-
Notifications
You must be signed in to change notification settings - Fork 8
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
[Bug] mac address #451
Comments
Hello, unfortunately I can't reproduce this. Can you also include the log before, where interfaces are created (obviously without sensitive information)? |
Hello,
Thanks |
v1.9.0-v1.9.3 2025/01/31 15:30:03 add_items.go:1337 DEBUG (vmware): MAC address 24:6E:96:52:2E:C0 does not exist in Netbox. Creating it... with v1.8.14 I think the problem comes from 41ce5c5 |
Hello, |
I have added more verbose logs, could you rerun develop version again? |
Hello,
Thanks |
Which netbox version are you running? |
4.2.1 |
Could you maybe try 4.2.2. I actually have no idea why this happens, I also can't reproduce it on my 4.2.2 instance, but I have seen there were some mac address fixes in 4.2.2: netbox-community/netbox#18363. Fixes like this also make my microservice uncompatible between patch versions, since it completely relies on API functionalities 😞 ... |
Is this urgent?
No
How are you running netbox-ssot?
Docker
What is the version of netbox-ssot
latest: main or develop tag
Which module has the issue?
IOS-XE
Share your configuration
What is the problem?
2025/01/31 11:29:44 main.go:117 ERROR (MLS-DC): create mac address for object type: add mac address MACAddress{MAC: 00:D6:FE:25:D9:06}: unexpected status code: 400: {"assigned_object_id":["This field cannot be null."]}
2025/01/31 11:29:44 main.go:136 INFO (main): Skipping removing orphaned objects because run failed...
Steps to reproduce
docker run
What did you expect to happen?
n/n
What actually happened?
n/a
Share DEBUG-level logs (remove sensitive information)
Share your environment details
Ubuntu 24.04
The text was updated successfully, but these errors were encountered: