Bug 1594910

Summary: BlockStorageCinderVolume specifies non-containerized version of cinder-volume service
Product: Red Hat OpenStack Reporter: Alan Bishop <abishop>
Component: openstack-tripleo-heat-templatesAssignee: Alan Bishop <abishop>
Status: CLOSED ERRATA QA Contact: Tzach Shefi <tshefi>
Severity: medium Docs Contact: Kim Nylander <knylande>
Priority: medium    
Version: 13.0 (Queens)CC: joflynn, jschluet, mburns, scohen
Target Milestone: z2Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-8.0.4-15.el7ost Doc Type: Bug Fix
Doc Text:
TripleO's BlockStorage role was not updated when Cinder services migrated from running on the host to running in containers. The cinder-volume service deployed on the BlockStorage host. The BlockStorage role has been updated to deploy the cinder-volume service in a container. The cinder-volume service runs correctly in a container.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 16:37:54 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: 1591251    

Description Alan Bishop 2018-06-25 16:46:12 UTC
Description of problem:

The TripleO composable roles resource registry defines the BlockStorageCinderVolume service, but the heat template it points to is one that deploys the non-containerized version of the cinder-volume service.

The file needs to be updated to specify the docker (containerized) version of the THT file.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

A patch has already been proposed upstream for stable/queens.

Comment 4 errata-xmlrpc 2018-08-29 16:37:54 UTC
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://access.redhat.com/errata/RHBA-2018:2574