vcenter null pointer due to irresponsive node about netbox-ssot

[TaLoN1x]

sample.log
this should make more sence now. Sorry for creating a confusion.

[TaLoN1x]

this fix resolved null pointer.

[bl4ko]

Thanks for reporting the issue. Could you provide the full log with DEBUG level?

[TaLoN1x]

Please find batch of last logs below. I did obfuscate some values. someserver.local is p
hysical node of cluster that is unavailable (disconnected).

sample.log

[bl4ko]

This log seems odd to me. How is it possible that IP addresses and interfaces for eevcenter source are synced before device data. Did you rename more than one source to eevcenter?

[TaLoN1x]

I had some nodes defined manually in netbox. It wasnät the first run for bath either, I had some null pointers I mentioned earlier, that I worked around with if smth == nil {return} ugly hack :)

[bl4ko]

Oh, I see so you are altering source code. The error says the panic occurs on

/Users/jurikononov/src/netbox-ssot/internal/source/vmware/vmware_sync.go:443 +0x4d

Which is empty line in main branch.

Could you first report issues in the main source code so I can test them and fix them?

[TaLoN1x]

yeah, my bad. let me revert it and provide new log.

[bl4ko]

Could you test again on 131-vcenter-null-pointer-due-to-irresponsive-node branch.