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.
Description of problem:
sos report is not reporting the dump of ovn dbs (ovn-nbdb and ovn-sbdb) by default.
Version-Release number of selected component (if applicable):
sos-4.0-12.el8_4.noarch
How reproducible:
RHOSP 16.2 environment, request a sosreport of one controller node and check that ovn db dumps are not reported in tar.xz file.
Steps to Reproduce:
1. Connect to controller node
2. Request sos report
3. Check tar.xz file looking for ovnnb_db.db and ovnsb_db.db
Actual results:
No files found
Expected results:
ovnnb_db.db and ovnsb_db.db files present on report tar.xz file
Additional info:
A pull request has been done already to fix the issue https://github.com/sosreport/sos/pull/2827 with the following commit message
Previous ovn packages were 'ovn2xxx' and now they have been renamed to 'ovn-2xxx'. This causes sos tool to not recognize that the packages are installed and it won't collect the relevant data.
This patch is changing the match expression to be compatible
with the previous and newer naming conventions.
So after merge it, we need to include in a new packet sos-4*
The business impact is important due to the fact that in the usual dealings with the customer for the tracking and analysis of problems, ovn databases data is not currently being attached to the general sos report that the customer sends us.
Simple workaround:
Call sos report -e ovn_central,ovn_host
That will explicitly enable those to plugins. Optionally, add to /etc/sos/sos.conf:
[report]
# Options that ..
# ..
enable-plugins = ovn_central,ovn_host
Where the backport is required to land?
- 8.7 can be trivially granted.
- 8.6 is a border case (quite late in devel/testing phase, a mandatory requirement to get qa_ack is to promise to verify the change / providing OtherQE; we can add to a respin in 1-2 weeks easily, then)
- 8.[4-5].z : most likely not happen as that would require an extra errata we dont have capacity for, now
Thanks Pawel for the workaround, currently we request and additional sos report in case we needed.
Related to backport:
- 8.7 good!
- 8.6 would be of great help to us and I myself offer to test the patch once the backport is done. (I will myself as OtherQE)
- 8.4 would be even more necessary than 8.6 and I justify the reasons as, RHOSP 16.2 is being deployed on top of RHEL 8.4, the migration effort is going strong to bring customers from previous versions to at least RHOSP 16.2, and we should keep in mind that RHOSP 16.2, according to its life cycle as ELS is going to be supported until April 30, 2025. [1]
[1] https://access.redhat.com/support/policy/updates/openstack/platform
After a chat with QE, we can add it to the 8.6 re-spin in the next 1-2 weeks, assuming the OtherQE (thanks for the commitment). That will ensure no regression from either 8.*.z to 8.6+ .
8.4.z : no capacity until April; also this would require backporting to 8.5.z (could be some RHOSP / ovn customer on 8.5? if not, we shall skip that backport excercise) - we can deliver the z-stream(s) there but no formal commitment can be provided ATM.
I will change this BZ to 8.6 and make it cloned to 8.4 and 8.5.
Granting zstream+ that the fix can be backported to 8.4.z and 8.5.z - with no comitment of really preparing the errata, in case of capacity constraints.
Hi,
Yes, the packet works but we have discovered an additional issue.
Basically the plugin is not enabled by default due to a typo on container name, a pull request has been done already to fix this issue [1] , so after merge it, we need to include in a new packet.
Thanks
[1] https://github.com/sosreport/sos/pull/2856
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 (sos bug fix and enhancement update), 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/RHEA-2022:1998