netbox-sync: Errors after script update

netbox 3.3.1 netbox-sync 1.3.0-beta3

  1. log file is not created (I created the folder manually) but the folder is empty. I set the DEBUG2 parameter but the log was not created.
  2. virtual machines are not created, only IP addresses to them
  3. Such error for each server. 2022-08-29 11:42:11,236 - DEBUG: Parsing vCenter host: 192.168.50.150 2022-08-29 11:42:11,620 - ERROR: Requesting cluster for host '192.168.50.150' failed. Skipping. 2022-08-29 11:42:11,696 - DEBUG: Parsing vCenter host: 192.168.50.110 2022-08-29 11:42:12,081 - ERROR: Requesting cluster for host '192.168.50.110' failed. Skipping. 2022-08-29 11:42:12,158 - DEBUG: Parsing vCenter host: 192.168.50.180 2022-08-29 11:42:12,537 - ERROR: Requesting cluster for host '192.168.50.180' failed. Skipping. 2022-08-29 11:42:12,613 - DEBUG: Parsing vCenter host: 192.168.50.145 2022-08-29 11:42:12,994 - ERROR: Requesting cluster for host '192.168.50.145' failed. Skipping. 2022-08-29 11:42:15,440 - ERROR: Requesting cluster for host '192.168.50.200' failed. Skipping. 2022-08-29 11:42:15,517 - DEBUG: Parsing vCenter host: 192.168.50.250 2022-08-29 11:42:15,898 - ERROR: Requesting cluster for host '192.168.50.250' failed. Skipping

2022-08-29 12:17:09,469 - DEBUG: Parsing vCenter host: 192.168.50.250 2022-08-29 12:17:09,851 - ERROR: Requesting cluster for host ‘192.168.50.250’ failed. Skipping. 2022-08-29 12:17:10,077 - ERROR: (vmodl.query.InvalidProperty) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = ‘’, faultCause = <unset>, faultMessage = (vmodl.LocalizableMessage) [], name = ‘answerFileValidationResult’ }

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 30 (15 by maintainers)

Commits related to this issue

Most upvoted comments

I will try to message you a zip file with the output from govc @bb-Ricardo

Version 1.3.0 has just been released

That’s what i noticed and installed 😃

Except for a few duplicate IPs i have on a group of VMs which is a non-issue fo me, everything works! Good job @bb-Ricardo

Thank you for all the feedback. I will close this issue for now so I can finally bush out the 1.3.0 release.

If you still encounter issue then please don’t hesitate to open a new issue.

Thank you

Seems it work fine with single Esxi hosts. Thanks a lot for your great script) Will use the last version of it from development branch and if it go wrong will text it.

I have a successful test run, visually all virtual machines have been created

I hope it works as planned. Thank you for a great script!

Hey, thank you again. The import worked flawlesly and also found a host with this issue in the logs. Will tey to fix it the next few days.

Great contribution

Thank you very much. I received the file and will test it over the weekend.