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
In recent Neutron, setting trusted key directly in the port's binding:profile has been deprecated and will be forbidden in future releases.
Dedicated port's attribute trusted, added by the API extension port_trusted_vif should be used instead.
New ML2 plugin extension port_trusted is now available. This extension implements the port_trusted_vif API extension which adds to the port resource a new boolean field called trusted.
This field should be used by admin users to set the port as trusted what was previously possible only through the port's binding:profile dictionary.
With this extension enabled, it is now possible for admin users to set port as trusted without modifying directly 'binding:profile' field which is supposed to be just for machine to machine communication.
/kind bug
In recent Neutron, setting
trusted
key directly in the port'sbinding:profile
has been deprecated and will be forbidden in future releases.Dedicated port's attribute
trusted
, added by the API extensionport_trusted_vif
should be used instead.New ML2 plugin extension
port_trusted
is now available. This extension implements theport_trusted_vif
API extension which adds to the port resource a new boolean field calledtrusted
.This field should be used by admin users to set the port as trusted what was previously possible only through the port's
binding:profile
dictionary.With this extension enabled, it is now possible for admin users to set port as trusted without modifying directly 'binding:profile' field which is supposed to be just for machine to machine communication.
Source: https://review.opendev.org/c/openstack/neutron/+/926068
We need to adapt CAPO with this change bu checking if the extension is enabled.
The text was updated successfully, but these errors were encountered: