Bug 1943352 - The CinderVolumeEdge service does not automatically pull in the containers it needs
Summary: The CinderVolumeEdge service does not automatically pull in the containers it...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-common
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Alpha
: 16.2 (Train on RHEL 8.4)
Assignee: John Fulton
QA Contact: Alfredo
URL:
Whiteboard:
Depends On:
Blocks: 1868673
TreeView+ depends on / blocked
 
Reported: 2021-03-25 20:58 UTC by John Fulton
Modified: 2021-09-15 07:13 UTC (History)
4 users (show)

Fixed In Version: openstack-tripleo-common-11.6.1-2.20210419132322.dbdaa05.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-15 07:13:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1920704 0 None None None 2021-03-25 20:58:27 UTC
OpenStack gerrit 782009 0 None NEW container-images: fix Cinder when running at Edge 2021-03-25 21:02:11 UTC
OpenStack gerrit 784982 0 None NEW container-images: fix Cinder when running at Edge 2021-04-06 16:54:05 UTC
Red Hat Product Errata RHEA-2021:3483 0 None None None 2021-09-15 07:13:32 UTC

Description John Fulton 2021-03-25 20:58:28 UTC 
In TripleO DCN environment, we can't run Cinder Volume at the Edge (using the new CinderVolumeEdge composable service):

CREATE_FAILED Resource CREATE failed: StackValidationFailed: resources.ServiceChain: Property error: ServiceChain.resources[30].properties: Property ContainerCinderVolumeIm
age not assigned

CREATE_FAILED StackValidationFailed: resources.ServiceChain: Property error: resources[30].properties: Property ContainerCinderConfigImage not assigned
Comment 1 John Fulton 2021-03-30 11:01:05 UTC 
This bug may present itself if you run the command below and don't see entries for ContainerCinderConfigImage or ContainerCinderVolumeImage in the images.yaml.

openstack tripleo container image prepare \
...
-e /usr/share/openstack-tripleo-heat-templates/environments/dcn-storage.yaml \
...
--output-env-file images.yaml

I experienced the above but after ensuring my containers on the undercloud had /usr/share/openstack-tripleo-common-containers/container-images/tripleo_containers.yaml.j2 from the fixing patch [1] the output file contained the necessary entries.

[1] https://review.opendev.org/c/openstack/tripleo-common/+/782009/6/container-images/tripleo_containers.yaml.j2
Comment 7 errata-xmlrpc 2021-09-15 07:13:08 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 (Red Hat OpenStack Platform (RHOSP) 16.2 enhancement 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/RHEA-2021:3483
Note You need to log in before you can comment on or make changes to this bug.