Bug 1174486 - Exclude facter from oo-admin-yum-validator repos.ini
Summary: Exclude facter from oo-admin-yum-validator repos.ini
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 22:28 UTC by Scott Dodson
Modified: 2015-01-08 15:34 UTC (History)
8 users (show)

Fixed In Version: openshift-enterprise-yum-validator-2.2.2-1.git.11.b13ec56.el6op
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-08 15:34:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0019 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 2.2.3 bug fix and enhancement update 2015-01-08 20:33:24 UTC

Description Scott Dodson 2014-12-15 22:28:59 UTC
The latest versions of puppet require facter 1.7.0 or later and puppet versions 3.0-3.4 required 1.6.11. With yum priorities in place users cannot upgrade puppet to version 3.x as we ship 1.6.6 in our node repo, though it appears unused.

If we add facter to excludes from repos.ini for oo-admin-yum-validator users will be able to upgrade to the version of facter of their choosing. However, this means that we're effectively removing the package for anyone that runs oo-admin-yum-validator. OSE depends on 'ruby193-facter' not 'facter', attempting to remove 'facter' from an all-in-one install does not show any dependencies. So this should be safe to do.

Alternatively, perhaps we could just un-ship the 'facter' package from our channels?

Comment 1 Scott Dodson 2014-12-15 22:29:49 UTC
Brenton,

Can you think of any problems here?

Comment 3 Brenton Leanhardt 2014-12-16 01:15:33 UTC
(In reply to Scott Dodson from comment #1)
> Brenton,
> 
> Can you think of any problems here?

This should be fine.  I think only ruby193-facter is used now.  Low ago I think some cartridges were relying on it and we probably failed to properly remove the package in newer versions of OSE in RHN.

Comment 4 Scott Dodson 2014-12-16 15:32:35 UTC
Test case, on a node :

oo-admin-yum-validator -a --role node 
rpm -Uvh http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
yum install puppet-3.7.3

should fail with dependency issues

Then upgrade oo-admin-yum-validator and repeat.

Comment 7 Ma xiaoqiang 2014-12-17 03:08:14 UTC
Check on openshift-enterprise-yum-validator-2.2.2-1.git.11.b13ec56.el6op.noarch

scenario 1:
1. register rhsm
2. fix all problem with node role
#oo-admin-yum-validator -a --role node 
<--snip-->
Repositories have been found which are missing one or more required package exclusions.
To prevent problems due to package conflicts, package exclusions are being set for the following repositories:
    rhel-6-server-rpms: tomcat6*
    jb-ews-2-for-rhel-6-server-rpms: httpd httpd-tools mod_ssl
    rhel-6-server-ose-2.2-node-rpms: facter
3. install  puppet-3.7.3
#rpm -Uvh http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
#yum install puppet-3.7.3

Can install puppet successfully.

scenario 2:
1. register rhn
2.  fix all problem with node role
#oo-admin-yum-validator -a --role node
<--snip--> 
To prevent problems due to package conflicts, package exclusions are being set for the following repositories:
    rhel-x86_64-server-6: tomcat6*
    rhel-x86_64-server-6-ose-2.2-node: facter
3. install  puppet-3.7.3
#rpm -Uvh http://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm
#yum install puppet-3.7.3

Can install puppet successfully.


I think the fixed package should be openshift-enterprise-yum-validator-2.2.2-1.git.11.b13ec56.el6op.noarch, Do you think so ?

Comment 8 Scott Dodson 2014-12-17 14:22:39 UTC
Ma,

You're correct. I've changed the Fixed By field to reflect the actual package, previously it reflected the build/SRPM for the fix.

--
Scott

Comment 10 errata-xmlrpc 2015-01-08 15:34:57 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/RHBA-2015-0019.html


Note You need to log in before you can comment on or make changes to this bug.