fix: remove RBAC-restricted fields from port creation for neutron 2026.1#2068
Draft
nidzrai wants to merge 1 commit into
Draft
fix: remove RBAC-restricted fields from port creation for neutron 2026.1#2068nidzrai wants to merge 1 commit into
nidzrai wants to merge 1 commit into
Conversation
…6.1 compatibility
24c53a6 to
d96b27e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
neutron 2026.1 tightened RBAC policies for create_port:device_owner, create_port:mac_address and create_port:fixed_ips , PROJECT_MANAGER role no longer allowed. Passing empty values for these fields still triggers the policy check. Removed device_owner, mac_address, fixed_ips and device_id from the port dict to avoid 403 errors for non-network-owner users on shared/RBAC networks.
Reference: https://docs.openstack.org/releasenotes/neutron/2026.1.html. Security Issues section