Cause: Changes in the subscription-manager and/or python-rhsm libraries shipped with RHEL 6.7 beta conflict with the way yum-validator uses the "logging" module shipped with Python.
Consequence: Output from the oo-admin-yum-validator tool was suppressed.
Fix: oo-admin-yum-validator has been updated to instantiate a unique, named logging.Logger object, which isolates its output from the common "root" Logger object and isn't affected by changes to the root Logger object.
Result: oo-admin-yum-validator generates output as expected under RHEL 6.7 beta.
Description of problem:
oo-admin-yum-validator can not show any message on RHEL67
Version-Release number of selected component (if applicable):
[2.2.6/2015-05-08.1/RHEL67]
How reproducible:
100%
Steps to Reproduce:
1. run o-a-y-v after installation on RHEL67
#oo-admin-yum-validator
Actual results:
Doesn't show any message
Expected results:
Should show message:
No roles have been specified. Attempting to guess the roles for this system...
If the roles listed below are incorrect or incomplete, please re-run this script with the appropriate --role arguments
broker
<--snip-->
Additional info:
This looks like it might be a bug in subscription-manager-1.14.5-1.el6. subscription_manager.repolib.RepoActionInvoker.is_manager() is failing because of a missing "matching_content" attribute. Will investigate further Monday.
Actually there are two problems here - the first is that the logging.RootLogger object used by oo-admin-yum-validator for output gets broken during the CheckSources initialization - but only under RHEL 6.7.
The second is the aforementioned problem with is_managed, which I've confirmed is an actual bug in subscription-manager.
I'm working on a workaround for the first problem, and will need to file a bug for the second.
We apologize, however, we do not plan to address this report at this time. The majority of our active development is for the v3 version of OpenShift. If you would like for Red Hat to reconsider this decision, please reach out to your support representative. We are very sorry for any inconvenience this may cause.
Description of problem: oo-admin-yum-validator can not show any message on RHEL67 Version-Release number of selected component (if applicable): [2.2.6/2015-05-08.1/RHEL67] How reproducible: 100% Steps to Reproduce: 1. run o-a-y-v after installation on RHEL67 #oo-admin-yum-validator Actual results: Doesn't show any message Expected results: Should show message: No roles have been specified. Attempting to guess the roles for this system... If the roles listed below are incorrect or incomplete, please re-run this script with the appropriate --role arguments broker <--snip--> Additional info: