Bug 1242507
Summary: | RHEL7: backport ovs patches to capture logs and db | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Flavio Leitner <fleitner> | |
Component: | sos | Assignee: | Pavel Moravec <pmoravec> | |
Status: | CLOSED ERRATA | QA Contact: | David Kutálek <dkutalek> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 7.1 | CC: | agk, bmr, dkutalek, gavin, isenfeld, lyarwood, plambri, sbradley | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | sos-3.2-29.el7 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1247630 (view as bug list) | Environment: | ||
Last Closed: | 2015-11-19 12:18:59 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Flavio Leitner
2015-07-13 13:00:38 UTC
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 |