It is unable to set a single VLAN for L2 Neutron segmenatation in Fuel

Bug #1589584 reported by Dmytro Fomenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Alexey Stupnikov

Bug Description

It is unable to set a single VLAN for L2 Neutron segmentation in Fuel. If I'm trying to do this I got the following error:

[504, 504] has non-unique elements
Failed validating 'uniqueItems' in schema['properties']['networking_parameters']['properties']['vlan_range']:
{'items': {'exclusiveMaximum': False,
'exclusiveMinimum': False,
'maximum': 4094,
'minimum': 2,
'type': 'integer'},
'maxItems': 2,
'minItems': 2,
'type': 'array',
'uniqueItems': True}
On instance['networking_parameters']['vlan_range']:
[504, 504]

Steps to reproduce:
Set a single VLAN in Neutron L2 Configuration tab.

Expected results:
Settings applied correctly

Actual results:
I get error cited above.

Reproducibility:
100%

Description of environment:
Fuel-8.0, VLAN network segmentation.

Tags: area-mos
Revision history for this message
Dmytro Fomenko (daks12) wrote :
Changed in fuel:
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
Maciej Relewicz (rlu)
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
milestone: none → 8.0-updates
tags: added: area-mos
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Alexey Stupnikov (astupnikov)
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

We have the same situation described here for both WEB and CLI Fuel interfaces, so Fuel requirements to have at least two VLAN IDs are consistent. I think, that originally Fuel required to have at least two VLAN IDs configured for Neutron L2 because it always created example network and according to bug #1471244 this situation stays the same for MOS 8.0. So IMO we are talking about a feature, which has simple workaround: provide non-existing second VLAN ID. Closing this bug as invalid.

Changed in fuel:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.