Bug 1677385 - Stack update breaks cinder-volume container if image name changes
Summary: Stack update breaks cinder-volume container if image name changes
Keywords:
Status: CLOSED DUPLICATE of bug 1643535
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-heat-templates
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Steve Baker
QA Contact: Tzach Shefi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-14 17:05 UTC by Andrew Mercer
Modified: 2022-03-13 17:28 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-06 20:16:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-13902 0 None None None 2022-03-13 17:28:52 UTC

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
Note You need to log in before you can comment on or make changes to this bug.