Bug 1235508

Summary:	Package update does not take puppet managed packages into account
Product:	[Community] RDO	Reporter:	Steve Baker <sbaker>
Component:	openstack-tripleo-heat-templates	Assignee:	Tomas Sedovic <tsedovic>
Status:	CLOSED EOL	QA Contact:	Shai Revivo <srevivo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	trunk	CC:	mburns
Target Milestone:	---
Target Release:	Kilo
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-19 15:39:17 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:
Bug Depends On:
Bug Blocks:	1235705

Description Steve Baker 2015-06-25 02:48:59 UTC

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/

Comment 1 Steve Baker 2015-06-25 02:51:24 UTC

Setting NEEDINFO on mburns to get a call on whether this should be flagged as a BLOCKER for RHEL-OSP director 7.0

Comment 2 Mike Burns 2015-06-25 22:32:19 UTC

This is an RDO bug, for the related RHEL-OSP bug, please see bug 1235705

Comment 3 Steve Baker 2015-06-25 23:28:12 UTC

Here is the etherpad tracking the changes required https://etherpad.openstack.org/p/tripleo-package-upgrades

Comment 4 Mike McCune 2016-03-28 23:42:22 UTC

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 6 Chandan Kumar 2016-05-19 15:39:17 UTC

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.