-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues after migrating from old vcenter-netbox-sync: 'dict' object has no attribute 'get_display_name' #45
Comments
Oh, thisnis not meant to happen. I will check tomorrow what the issue is here. |
It looks like some relations could net be resolved. I added another check which hopefully fixes the issue. can you try it again? |
Hello, Seems like it is still an issue.
Updated:
|
Sorry, you need to switch to the development branch. |
Yeah, the dev branch fixed this issue. The script does now add new objects to Netbox, but creates quite a few duplicates and has a livid fanstasy creating objects that does not exist in vCenter and connects IP-adresses to servers to the completely wrong servers. Also, when running the script a second time (after it worked once), I got this error:
|
Hi, yes this is the same issue in a different spot. I'm wondering if this the only ERROR you get. When you start the sync, do you get any other WARNING or ERROR messages? Maybe check the log if activated. |
Hi again, I can see that if I scroll a bit up there are a few other errors:
This one repeats a lot:
This one is repeated 10-30 times in a row:
The first error when running the script seems to be:
I have modified the error messages somewhat to remove server-names and IP-addresses. |
I believe that your NetBox upgrade went wrong and some relations are not present anymore. Nevertheless, the code should be able to handle this. I will fix this issue. |
closing due to no response |
@bb-Ricardo Sorry, I have been unable to look at this for a while. I can however confirm that your fix has been successful. After some testing today, everything looks great. Thank you! |
Thank you for the feedback. Great to hear. Sometimes people don't get back at all, that's why I close tickets I consider fixed after a while. |
Hello,
Attempting to migrate from synackray/vcenter-netbox-sync to this version, while also upgrading from the last working version with synackray's version (2.8.9) to 2.10.4, I have encountered some issues and would like some guidance. I have followed the upgrade procedure as documented in the netbox repository, and netbox works perfectly on the new version.
The database is already populated with a few hundred virtual machines, ip-adresses, VLANs etc. and I was hoping that since this project is based on synackray's version they would somehow (almost) work.
The error I am getting when running the sync with this new sync tool is (VM names and IP-adresses has been changed):
I am guessing that there are something in the old database that the new tool does not like, but this crashes and is not handled (the script stops completely).
Any suggestions would be appriciated, thank you.
The text was updated successfully, but these errors were encountered: