Nathaniel Fernandez

Just an update. I updated nautobot to 2.0.5 and device onboarding version from 2.0.2 to 3.0.1 in order to address the XSS vulnerability. I still got the same error in...

Upon checking /var/log/messages on that job run, I was able to get more context in that error message. Looks like there are two device types being returned. 

The majority of the device types that was failing to onboard on our prod instance was a Cisco ASR1001-X Router. Actually I don't see an onboarded device having that type....

@susanhooks thanks for your suggestion. I tried to look at the code but I don't know if how it works fully. But since it mentioned ensure_device_type as one of the...

I think we're good to close this one. Just fyi, I would probably need to raise a separate issue in nautobot/nautobot. I get a different error for some devices that...

just fyi, I was able to work around the onboarding error about prefix on my previous post. There seems to be a discrepancy in what we're seeing in the UI....

Looks like a potential root cause has been found. Thanks guys. :) Do you still need any output from my end? If not, I'll apply the workaround on the prefixes...

I may have some clue on why the "**N**etwork" bug is showing up that I want to share. We have some devices that uses the wrong subnet for management. For...

Please disregard my previous message, we had a lot of those prefixes that uses "Network". Updated them in nbshell to use "network" type.  Looks like this issue did not...

I've encountered this issue today too on my new Xpresso setup where previous tests are not showing. I haven't encountered it on the previous setup. It started to show after...