Kirk Byers

@mbeckergit Not that I am aware of. As far as I know there is no one working on it...so if you want to dive into it...that would be good :-)

Okay, let me know if you find a better way to clear it or something more proactive we can do on the NAPALM side (for this locking/unlocking issue).

This looks like a Cisco bug / issue with ``` show archive config differences flash:/candidate_config.txt system:running-config ```

@neelimapp

Should be fixed here: https://github.com/napalm-automation/napalm/pull/1700 This PR still needs to be merged.

@M0NsTeRRR Thanks for letting us know.

Okay, there is a probably bug in inline_transfer. As a workaround, you would need to put your configuration changes in an external file. In other words, call: ```python load_merge_candidate(filename="my_changes.txt") ```

I am going to re-open() to track the original issue.

Yes, you need to use {{ ansible_host }} and not {{ inventory_hostname }} ``` [cisco] spine1 ansible_host=10.0.100.101 spine2 ansible_host=10.0.100.102 leaf1 ansible_host=10.0.100.103 leaf2 ansible_host=10.0.100.104 leaf3 ansible_host=10.0.100.105 leaf4 ansible_host=10.0.100.106 ``` inventory_hostname is...

So `PlatformInventory` doesn't exist on 7.3.3? Is there an alternate place we should be querying for this information on 7.3.3?