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.

Description of problem:

Currently sos doesn't capture the logs which are fundamental to start troubleshooting an issue.  There is also a second patch that captures a dump of the database so we have a clear view of all the configuration details.

This bug requests to backport such upstream changes listed below:


commit 4a57c54216242acb009fdb107d52712decfdfc1e
Author: Bryn M. Reeves <bmr>
Date:   Mon Jul 6 17:31:44 2015 +0100

    [openvswitch] consolidate self.add_cmd_output() calls
    
    Signed-off-by: Bryn M. Reeves <bmr>

commit f92205495113a8403066e911baeb4f5ee59c2101
Author: Flavio Leitner <fbl>
Date:   Fri Jun 19 22:05:52 2015 -0300

    [openvswitch] dump and capture the database
    
    The database contains all the vswitch configuration and
    is essential to understand and replicate the environment.
    
    Signed-off-by: Flavio Leitner <fbl>

commit 21aff64a58a3e0f3fc5065b2e18ca3d489e16a51
Author: Flavio Leitner <fbl>
Date:   Fri Jun 19 21:55:56 2015 -0300

    [openvswitch] capture the logs
    
    Both ovs-vswitchd.log and ovsdb-server.log are useful
    for troubleshooting.
    
    Signed-off-by: Flavio Leitner <fbl>

RHEL7.2 devel deadline was last week, bouncing to 7.3. 

Backporting the three commits sounds trivial, devel_acking it.

After discussion with Lee, requesting to add it to 7.2.

For QE:

The fix should additionally collect:

- output of command "ovsdb-client dump"
- files /var/log/openvswitch/ovs-vswitchd.log and /var/log/openvswitch/ovsdb-server.log

on an OpenVSwitch system.

Lee detected also 775b2bbfb28701ec2e687f0ece68a4558cef8740 commit needs to be backported. That adds three ovs-* commands output for each OVS bridge on the host.

To QE:
this BZ should additionally collect (complete list follows):

1) output of command "ovsdb-client dump"

2) logfiles:
/var/log/openvswitch/ovs-vswitchd.log
/var/log/openvswitch/ovsdb-server.log

3) for each OVS bridge (from output of "ovs-vsctl list-br" command), three commands output to be collected:
ovs-ofctl show <br>
ovs-ofctl dump-flows <br>
ovs-appctl fdb/show <br>

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, 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://rhn.redhat.com/errata/RHBA-2015-2118.html