yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59787
[Bug 1649531] Re: When adding subports to trunk segmentation details shouldn't be mandatory
The only drivers that are supported today by the trunk extension do
require these details be provided by the user. If/when a new driver is
added (like Ironic) that can work without, we'll revise the conditional
statement that return this error to the user. Until then, this is
invalid.
** Changed in: neutron
Status: New => Invalid
** Changed in: neutron
Assignee: Vasyl Saienko (vsaienko) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1649531
Title:
When adding subports to trunk segmentation details shouldn't be
mandatory
Status in neutron:
Invalid
Bug description:
According to Neutron trunk specification [0] segmentation_id and
segmentation_type are optional fields. But when we adding subport to
trunk requests without segmentation_id/segmentation_type are failing.
Example:
$ openstack network trunk set --subport port=port2 trunk10
Failed to add subports to trunk 'trunk10': Invalid input for operation: Invalid subport details '{u'port_id': u'f9922f99-f0e4-4420-be73-dbb9ea7904c6'}': missing segmentation information. Must specify both segmentation_id and segmentation_type.
Neutron server returns request_ids: ['req-7601d1a4-afdf-40e6-9273-1fdab1fc8040']
[0] https://specs.openstack.org/openstack/neutron-specs/specs/mitaka/vlan-aware-vms.html#proposed-change
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1649531/+subscriptions
References