Closed phil-dileo closed 9 years ago
Same files as always. What's interesting is that after this initial bootstrap (which returns the wrong value) if you delete the nodes dirs and delete the startup-configs on the tors to revert them to ZTP, the next time they go through provisioning the right value is returned. So there's something unique about the initial assignment that's broken.
Ok, sorted - was using the same variable name in too many places and things got messed up. This is now fixed - good catch!
On Tue, Aug 11, 2015 at 12:15 PM, Philip DiLeo notifications@github.com wrote:
Same files as always. What's interesting is that after this initial bootstrap (which returns the wrong value) if you delete the nodes dirs and delete the startup-configs on the tors to revert them to ZTP, the next time they go through provisioning the right value is returned. So there's something unique about the initial assignment that's broken.
— Reply to this email directly or view it on GitHub https://github.com/arista-eosplus/ztpserver/issues/323#issuecomment-129839752 .
Thanks Andrei! Just tested it and things look good.
This is strange. When using the ztpserver-demo files, the allocate plugin correctly updates the resource pool file, but it doesn't return the right key to the do_resources().
EG
Resource Pool (before provisioning)
Resource Pool (after provisioning)
Both tora and torb are identified via neighbordb, but when they run GET definition the ZTPServer returns the same key from the resources pools, but for ipaddress and hostname.
tora
torb