You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug report is not security related, security issues should be disclosed privately via netbox operator maintainers.
Existing open issues have been checked and this is not a duplicate.
What happened?
When creating an IpAddressClaim with a tenant which does not exist, an ipAddress resource is generated containing the next available IPAddress from the prefix.
What did you expect to happen?
There should be no IPAddress generated at all since the Tenant does not exist.
How can we reproduce it (as minimally and precisely as possible)?
Apply following cr and an ipaddress resource will be generated containing an ip:
Bug report criteria
What happened?
When creating an IpAddressClaim with a tenant which does not exist, an ipAddress resource is generated containing the next available IPAddress from the prefix.
What did you expect to happen?
There should be no IPAddress generated at all since the Tenant does not exist.
How can we reproduce it (as minimally and precisely as possible)?
Apply following cr and an ipaddress resource will be generated containing an ip:
Netbox operator version
Latest from main branch
Netbox operator configuration (command line flags or environment variables)
Followed the instructions from the readme
Relevant log output
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: