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.
This bug was initially created as a copy of Bug #2004929
I am copying this bug because:
we need to be in par with 8.6 and 9.0
Description of problem:
Currently the sos report lacks information that is needed to recreate ovs-vswitchd and ovs-db offline for debugging / analysis.
This includes tlv map dumps for each bridge and group dumps which are being collected inconsistently.
Additionally the database is not currently collected in a format that can be used to restore the ovsdb-server.
With this information, offline proto/traces and various other tools could be run on offline replicas.
How reproducible:
Always
Steps to Reproduce:
1. Run sos report on an ovs-node
Actual results:
- db is not in a format that can be restored.
- tlv maps are missing
- group and -O flow dumps will only be available for bridges that specify protocols in ovs-vsctl get bridge <br> protocols
Expected results:
The sos report should contain all necessary information to recreate ovs-vswitchd and ovsdb-server offline without needing to request any additional information from the user.
Additional info:
Some of this information is already included in the sos report (i.e. flow and group dumps by bridge), however this is only collected if ovs-vsctl list bridge specifies protocols, which may not always be the case even when default protocols are in place.
The conf.db file is also needed, and is currently being gathered using ovsdb-client list dump. This is not a format that can be used to restore the db, and also requires interacting with the ovsdb-server which could potentially take it "down" for some time.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (new packages: sos), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:3932