Bug 1299022
Summary: | net-snmp-libs multilib errors during compute node update | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | James Slagle <jslagle> |
Component: | openstack-tripleo-heat-templates | Assignee: | James Slagle <jslagle> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
Severity: | unspecified | Docs Contact: | |
Priority: | urgent | ||
Version: | 7.0 (Kilo) | CC: | dmacpher, emacchi, jmelvin, mburns, rhel-osp-director-maint, sasha |
Target Milestone: | y3 | ||
Target Release: | 7.0 (Kilo) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-0.8.6-99.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Non-Controller nodes reported package dependency issues due to delegating Puppet as the mechanism to update certain packages and excluding them from YUM updates. This fix sets all Non-Controller nodes to use Puppet as the update mechanism. Now packages on non-Controller nodes update without package dependency issues.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-02-18 16:50:01 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: | |
Embargoed: |
Description
James Slagle
2016-01-15 17:34:14 UTC
one potential fix here is when we build the yum command line, we specify the --exclude parameters with a * on the end of the package name. This will mean that all subpackages will also be excluded. So instead of specifying: --exclude=net-snmp it would be: --exclude=net-snmp* In my testing, this makes the yum update succeed. And we already have an addtional step after the puppet package update to run a plain old yum update again to ensure that all subpackages are updated as well. another option would be to backport this patch to puppet-tripleo: https://review.openstack.org/#/c/26104 In addition to that patch, we'd want to remove the initial yum update (with the excludes) on all the non-controller nodes, and the yum update at the end. This would mean puppet was handling all the package updates, and is probably the better long term solution. for manual testing, this is the command that can be run and will fail on compute nodes: yum update --exclude=ceph --exclude=libvirt-daemon-config-nwfilter --exclude=libvirt-daemon-kvm --exclude=net-snmp --exclude=ntp --exclude=openstack-ceilometer-common --exclude=openstack-ceilometer-compute --exclude=openstack-neutron --exclude=openstack-neutron-ml2 --exclude=openstack-neutron-openvswitch --exclude=openstack-nova-common --exclude=openstack-nova-compute --exclude=openvswitch --exclude=pm-utils --exclude=python-greenlet --exclude=python-nova --skip-broken (In reply to James Slagle from comment #3) > another option would be to backport this patch to puppet-tripleo: > > https://review.openstack.org/#/c/26104 this should be: https://review.openstack.org/#/c/261041 > > In addition to that patch, we'd want to remove the initial yum update (with > the excludes) on all the non-controller nodes, and the yum update at the end. > > This would mean puppet was handling all the package updates, and is probably > the better long term solution. concensus is around backporting the puppet patch and no longer running the yum update script on non-controllers. i've proposed the backport to stable/liberty upstream, https://review.openstack.org/#/c/268257/ We need to backport into OPM: https://review.openstack.org/#/c/261041/ And then: https://review.openstack.org/#/c/268388/ See https://bugzilla.redhat.com/show_bug.cgi?id=1299144 for OPM build. Verified: openstack-tripleo-heat-templates-0.8.6-106.el7ost.noarch The issue doesn't reproduce, no dependecy errors are shown. *** Bug 1295849 has been marked as a duplicate of this bug. *** 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-2016-0264.html |