Bug 1677385

Summary:	Stack update breaks cinder-volume container if image name changes
Product:	Red Hat OpenStack	Reporter:	Andrew Mercer <amercer>
Component:	openstack-heat-templates	Assignee:	Steve Baker <sbaker>
Status:	CLOSED DUPLICATE	QA Contact:	Tzach Shefi <tshefi>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	abishop, apevec, aschultz, dvd, lhh, michele, tenobreg, tshefi
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-06 20:16:59 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 Andrew Mercer 2019-02-14 17:05:26 UTC

Description of problem:
Trying to change DockerCinderVolumeImage to customized image with vendor drivers. The image is downloaded successfully to the controllers, however, while stack updates work, they leave cinder-volume in a broken state and requires
it to be manually changed in pacemaker.



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

openstack-tripleo-heat-templates-8.0.7-4.el7ost.noarch


How reproducible:


Steps to Reproduce:
1. Update the cinder-volume container image name
2. Run update

Actual results:
cinder-volume container doesn't start

Expected results:
cinder-volume container starts using new image


Additional info:
Recommend moving the "Update <insert-pcs-service-here> pcs resource bundle for new container image" code from upgrade_task to update_task