Closed adparis99 closed 4 weeks ago
@adparis99 thanks for trying it out! I'm sorry you have issues. The issue seems to be that I'm trying to get the tenant from the site, but the site does not have a tenant assigned.
I'll push a fix today that does a few things different:
if you could please verify if that fixes the issue it would be lovely :)
FYI: It's on main now, I'll cut a release if it works as expected for you
@adparis99 thanks for trying it out! I'm sorry you have issues. The issue seems to be that I'm trying to get the tenant from the site, but the site does not have a tenant assigned.
My pleasure! Thanks for bringing a great idea to life.
if you could please verify if that fixes the issue it would be lovely :)
Good news and bad news! The issue of the app crashing is fixed, and some devices are syncing! Unfortunately, not all devices are syncing, and no VMs synced either. The status in the system tray shows as "failed to create session", and there's no output in the console. Let me know if there's anything I can do on my end to help troubleshoot/debug further.
Edit: I paid a bit more attention to the system tray and noticed that the status dynamically updates throughout the sync process. I was able to see it start at Getting Devices, then Getting Virtual Machines, then finally Writing session... or something similar (it changes too quickly for me to catch it exactly) before stating failed to create session.
One other thing to note with regards to the devices that aren't syncing is that there are whole sites that don't seem to get added, despite devices in those sites being assigned the correct tenant. In one of my tenants there are twelve sites, but only six of them are populating.
failed to create session
happens when the program is unable to write session files, or create the directory structure needed. I have a feeling there might be some special characters involved in the device name or site names?
Could you maybe provide a site name, and device name under that site and I'll try replicate it? (sanitized where it makes sense of course)
Thank you! That was enough of a push to help me find the issue (one device with '?' in the name, and another with '/'). Once I updated those, the sync went through perfectly.
As an aside, I think a cool feature to add would be the ability to set the connection type based on attributes of the device/VM. An example use case would be to look create sessions with RDP for VMs, or with telnet for devices with a given custom field. I'd be more than happy to make a separate feature request for that though.
Thanks again for all the hard work!
Awesome you got it working! I'll do some work on improving the handling of special characters in filenames. Please create a separate request for that and I'll look into it :)
First off, I think the idea for this is awesome, and was super excited to try it. Unfortunately, I got the error above/below after installing Go, getting the app running, and then hitting Sync Inventory Now. While I'm familiar with YAML and NetBox, I've got no experience with Go, so I definitely could be doing something wrong. The error:
My YAML config:
Edit: Should've added this before, but I'm running NetBox 3.7.8, Go 1.22.4 on Windows 11, and SecureCRT 9.3.2.