Hide Forgot
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.
From the upstream discussion in https://github.com/sosreport/sos/issues/871 : openstack_* plugins shall implement --verify option to call "rpm -V (relevant_OSP_packages)" - that's acceptable.
(In reply to Pavel Moravec from comment #2) > From the upstream discussion in https://github.com/sosreport/sos/issues/871 : > > openstack_* plugins shall implement --verify option to call "rpm -V > (relevant_OSP_packages)" - that's acceptable. Hi Pablo, could you pls. comment if the proposal at: https://github.com/sosreport/sos/issues/871#issuecomment-285977997 is sufficient/acceptable?
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
This bug shall be fixed in package: sos-3.4-6.el7.noarch.rpm available via errata: https://access.redhat.com/errata/RHBA-2017:2331 Thus I am closing this bug report.