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.
DescriptionPablo Iranzo Gómez
2016-09-07 11:52:43 UTC
Description of problem:
User decided to modify some important libraries (AMQP) on the system (BZ 1373146), so until it was found that the libraries were manually modified, the issue and the configuration status was not reproducible and made no sense.
Having identified that the libraries were modified, could have sched light on this, allowing to solve it faster.
Upstream report for sos is at https://github.com/sosreport/sos/issues/871
Gigantic NACK from my side, sorry :-)
There are ways that we can make this work for specific use-cases but we will not re-introduce a default "rpm -Va" collection for any reason.
Plugins have for some time now been able to add their own "--verify" hooks and this is what plugin authors should be doing now.
There are ways we can refine that to make this even easier for developers but throwing in a command that could run for 20-30m, and that generates a huge volume of IO, is not acceptable as a default setting for the places that sos finds itself in use today.
Comment 4Pablo Iranzo Gómez
2017-03-13 06:46:50 UTC
Hi Pavel,
If we have the *verify* enabled always for OSP that would be great, the problem is that we don't want to have reask customers for rpm -Va (for OSP packages and python dependencies)
Thanks!,
Pablo