This repository was archived by the owner on Jan 8, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 29
Cleanup tasks fail for IP defined vCenter hosts #51
Comments
Hello again, @jaimehrubiks! Let me take a quick look at this. The tags are derived from the vCenter hosts configuration in |
I did @synackray, it is an IP address :P |
:') No worries. This was a simple mistake on my part. After adjustments here is what I see.
|
synackray
added a commit
that referenced
this issue
Feb 4, 2020
synackray
added a commit
that referenced
this issue
Feb 4, 2020
synackray
added a commit
that referenced
this issue
Feb 4, 2020
…osts Fixed cleanup requests for IP defined vCenter hosts for #51
Merged into |
Works great, thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I found this error in my setup when trying to clean.
I did notice that all my elements (devices, vms, ips...) have these three tags: "Synced", "vCenter" and "10.102.138.31"
The last one looks weird, maybe it's the one causing errors. That is in fact the IP of the following VM: "nxt-vcenter-01"
jaimejoseba at CH-JJOSEBA-MBP in ~/working/vcenter-netbox-sync
$ python3 run.py -c -v
2020-02-04 14:15:44,630 [DEBUG] Log level has been overriden by the --verbose argument.
2020-02-04 14:15:44,631 [INFO] Preparing for removal of all NetBox synced vCenter objects.
2020-02-04 14:15:44,631 [INFO] Collecting all current NetBox ip_addresses objects to prepare for deletion.
2020-02-04 14:15:44,632 [DEBUG] Sending GET to 'http://10.102.140.212:80/api/ipam/ip-addresses/?tag=10.102.138.31' with data 'None'.
2020-02-04 14:15:44,657 [DEBUG] Received HTTP Status 400.
2020-02-04 14:15:44,657 [CRITICAL] Well this in unexpected. Please report this. GET request received 400 status with body 'None' and response '{'tag': ['Select a valid choice. 10.102.138.31 is not one of the available choices.']}'.
The text was updated successfully, but these errors were encountered: