Kirk Byers
Kirk Byers
No, it is just me. Let me see if I can do this in the next week.
We should also remove the `secrets.PYPI_USERNAME` and `secrets.PYPI_PASSWORD` from the NAPALM repository after this is done (as we shouldn't need them any longer)...but you were probably going to do this...
@jesk78 If I am understanding you correctly,you are misunderstanding the behavior of NAPALM + IOS and a merge operation. NAPALM + IOS does the following 1. secure copy a configuration...
@jesk78 Meaning the issue is with the `diff` or you are seeing an actual issue on a `merge` behavior? If it is on the `merge` behavior, can you give me...
I am not seeing an issue: ``` Cisco IOS XE Software, Version 16.08.01 Cisco IOS Software [Fuji], ISR Software (ARMV8EB_LINUX_IOSD-UNIVERSALK9_IAS-M), Version 16.8.1, RELEASE SOFTWARE (fc3) ``` ``` device.load_merge_candidate(config="ntp server 192.0.2.1")...
Okay, I don't think that is Cisco IOS-XE being smart. I think it is probably just a Cisco bug. I also would not generalize it beyond this one example (unless...
Do we need a different process here? In this case applying the candidate config failed and the `on-box rollback` failed. I think we should automatically invoke a NAPALM rollback in...
@ncsurfus Yes, it would try to do a `configure replace` again, but back to original configuration (which has been saved to flash). I would expect this should work (otherwise, I...
Neither `show configuration lock` nor `show configuration sessions`, show any lock nor config session: ``` RP/0/RP0/CPU0:iosxr3#show configuration lock Fri Apr 9 20:52:16.003 UTC RP/0/RP0/CPU0:iosxr3#show configuration sessions Fri Apr 9 20:52:49.017...