Bug 1791869 - [rfe] ability to change segmentation_id in existing networks
Summary: [rfe] ability to change segmentation_id in existing networks
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 13.0 (Queens)
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: z11
: 13.0 (Queens)
Assignee: Rodolfo Alonso
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-16 16:12 UTC by Rafael Urena
Modified: 2023-07-10 17:19 UTC (History)
7 users (show)

Fixed In Version: openstack-neutron-12.1.0-12.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-10 17:19:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4281 0 None None None 2021-11-18 15:23:47 UTC

Description Rafael Urena 2020-01-16 16:12:30 UTC
This bug was initially created as a copy of Bug #1643769

I am copying this bug because: 

Affirm network would like to have the fix backported or a hotfix provided for rhosp 13

Description of problem:
In the context of a live datacenter, sometimes the network teams re-organize their VLANs by changing VLAN IDs .  This is pretty straightforward in the context of network configuration and physical servers but when using ML2 VLAN provider networks, those IDs cannot be updated .  The only possible solution here would be to delete those networks and recreate them with a different VLAN ID which might be a problem when you have 1000 VMs and 2000 ports.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a VLAN ML2 provider network
2. Try updating the segmentation_id
3.

Actual results:
Fails

Expected results:
Succeeds

Additional info:

Comment 15 Lon Hohberger 2020-03-11 10:36:11 UTC
According to our records, this should be resolved by openstack-neutron-12.1.1-6.el7ost.  This build is available now.

Comment 18 Lon Hohberger 2023-07-10 17:19:22 UTC
OSP13 support officially ended on 27 June 2023


Note You need to log in before you can comment on or make changes to this bug.