Triggering an overcloud package update should do a combination of yum update and puppet ensure=>latest depending on whether the package is managed by a puppet module. Doing only a yum update will bypass the puppet module's service dependency/restart logic Doing only a puppet ensure=>latest will ignore packages not managed by puppet This bz is to track the progress of the fix for this which is in progress: https://review.openstack.org/#/c/190918/ https://review.openstack.org/#/c/194348/ https://review.openstack.org/#/c/193394/ https://review.openstack.org/#/c/193393/
Setting NEEDINFO on mburns to get a call on whether this should be flagged as a BLOCKER for RHEL-OSP director 7.0
This is an RDO bug, for the related RHEL-OSP bug, please see bug 1235705
Here is the etherpad tracking the changes required https://etherpad.openstack.org/p/tripleo-package-upgrades
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
This bug is against a Version which has reached End of Life. If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.