Bug 1294513

Summary: oo-diagnostics test_enterprise_rpms fails for nodejs010-nodejs-debug
Product: OpenShift Container Platform Reporter: Josep 'Pep' Turro Mauri <pep>
Component: ContainersAssignee: Timothy Williams <tiwillia>
Status: CLOSED ERRATA QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.2.0CC: aos-bugs, erjones, gpei, jokerman, mmccomas, rthrashe, tiwillia
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-openshift-origin-common-1.29.5.1-1.el6op Doc Type: Bug Fix
Doc Text:
Cause: Checks for proper rpm packages, with el6op in the name, incorrectly expected the nodejs-debug package to contain this tag. Consequence: A false error was reported from oo-diagnostics on up-to-date systems Fix: oo-diagnostics no longer expects nodejs-debug to contain the el6op tag Result: oo-diagnostics no longer reports a false error on up-to-date systems.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-22 16:53:53 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:
Bug Depends On:    
Bug Blocks: 1273542    

Description Josep 'Pep' Turro Mauri 2015-12-28 16:37:55 UTC 
Description of problem:

oo-diagnostics on a current OSE 2.2 node reports a FAILure in the installed RPMs because there's a package installed from a RHEL [SCL] channel unexpectedly: nodejs010-nodejs-debug

Version-Release number of selected component (if applicable):

rubygem-openshift-origin-common-1.29.1.1-1.el6op.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install an OpenShift Enterprise 2.2.8 node
2. Configure repositories as documented, i.e. including RHSCL:
   https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Configuring_Yum_on_Node_Hosts
3. Update the system (yum update). This will update nodejs010-nodejs-debug to version 2.2.0-2.el6 coming from RHSCL
4. Run 'oo-diagnostics' on the node

Actual results:

# oo-diagnostics -v
INFO: loading list of installed packages
INFO: OpenShift node installed.
INFO: running: prereq_dns_server_available
INFO: checking that the first server in /etc/resolv.conf responds
INFO: running: prereq_domain_resolves
INFO: checking that we can resolve our application domain
INFO: running: test_enterprise_rpms
INFO: Checking that all OpenShift RPMs are actually from OpenShift Enterprise
FAIL: test_enterprise_rpms
      The following problems were found with your RPMs:

        nodejs010-nodejs-debug should be an OpenShift Enterprise RPM but installed version 2.2.0-2.el6 does not have 'el6op' in it

      Please ensure that you have not enabled EPEL or other third-party repositories, and
      do not have any of these RPMs pre-installed in your install image. These RPMs must come
      from your OpenShift Enterprise subscription in order to be supported.


Expected results:
No failure if the installed packages are actually supported.

Additional info:

nodejs010-nodejs-debug-2.2.0-2.el6 was introduced to RHSCL in https://rhn.redhat.com/errata/RHBA-2015-2653.html on 16/Dec/2015. AFAICT this package was not part of SCL before, but it seems to be supported from there now.
Comment 6 Rory Thrasher 2016-02-22 22:31:06 UTC 
QE,

Can we verify based on the original report's instructions that this has been fixed?

Puddle: http://etherpad.corp.redhat.com/puddle-2-2-2016-02-19

Thank you
Comment 7 Gaoyun Pei 2016-02-26 05:25:46 UTC 
Verify this bug with rubygem-openshift-origin-common-1.29.5.1-1.el6op.noarch

With the following nodejs010-nodejs-debug packages from rhscl installed on host:
nodejs010-nodejs-debug-2.2.0-2.el6.noarch
nodejs010-nodejs-debuglog-1.0.1-4.el6.noarch

Run 'oo-diagnostics', it wouldn't complain nodejs010-nodejs-debug during test_enterprise_rpms.
Comment 9 errata-xmlrpc 2016-03-22 16:53:53 UTC 
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/RHSA-2016-0489.html