Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 916336[details]
debug info
Description of problem:
While creating vlan interface ( with/without NM) and attached it to openstack br-ex bridge
After network restart
The interface is seen in the ovs-show but not in ovs-ofctl , only openvswitch agent restart help
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.configure packstack to use interface vlan within BR-EX
2.check ovs-show and ovs-ofctl interface vlan is seen
3.service network restart
4. check ovs-ofctl doesn't show the interface vlan
See attached logs and debug
Actual results:
Expected results:
Additional info:
Hi,
The ovs-vsctl command shows what is in the database, not what is running on the system. Usually they are synchronized, but some events can break that link.
The ovs-ofctl command shows what is currently running in the system.
When you restart the 'network' service script, the VLAN device is destroyed (ip link delete <vlan> type vlan) from the system but it's not removed from the OVS bridge/database, then the vlan device is created again, but that device isn't attached to the OVS bridge. As a result, you have the OVS bridge with stale information about the old device, but ovs-ofctl confirms that it's not actually attached.
Ideally you should stop openvswitch first which would remove all ports and bridges, then restart the network service, then bring up openvswitch again. But I know that if you have the bridge configured using ifcfg- file, on a ifdown it will be destroyed taking all the OVS specific configuration with it (see bz#1115151).
So, this is a known issue without a solution yet. If you can remove the ports before restart the network service and then attach the new devices back to the bridge it should work just fine, but it might be better to have the ifcfg- configs and ifdown/ifup scripts working for OVS so you can use them manage all that.
Created attachment 916336 [details] debug info Description of problem: While creating vlan interface ( with/without NM) and attached it to openstack br-ex bridge After network restart The interface is seen in the ovs-show but not in ovs-ofctl , only openvswitch agent restart help Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.configure packstack to use interface vlan within BR-EX 2.check ovs-show and ovs-ofctl interface vlan is seen 3.service network restart 4. check ovs-ofctl doesn't show the interface vlan See attached logs and debug Actual results: Expected results: Additional info: