Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1842976

Summary:	openstack tripleo container image prepare should retrieve neutron ovs containers
Product:	Red Hat OpenStack	Reporter:	Takashi Kajinami <tkajinam>
Component:	openstack-tripleo-common	Assignee:	Adriano Petrich <apetrich>
Status:	CLOSED NOTABUG	QA Contact:	David Rosenfeld <drosenfe>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.0 (Train)	CC:	mburns, slinaber
Target Milestone:	---	Keywords:	Triaged
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:	2020-06-03 04:35:03 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 Takashi Kajinami 2020-06-02 13:40:48 UTC

Description of problem:

"openstack tripleo container image prepare" command is expected to pull
all containers required for undercloud/overcloud deployment.

However currently "openstack tripleo container image prepare" only pulls
neutron containers for ovn, and doesn't pull neutron containers for ovs.

This is incomplete because neutron ovs containers for undercloud are still
required for undercloud.

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

How reproducible:
Always

Steps to Reproduce:
1. run "openstack tripleo container image prepare --" according to the guide[1]
2. Check the list of container images shown in "openstack tripleo cntainer image list"

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html-single/director_installation_and_usage/index

Actual results:
Neutron ovs containers are not stored in undercloud image server, but only neutron ovn containers are.

Expected results:
Both neutron ovs containers and neutron ovn containers are stored in undercloud image server

Additional info:

Comment 1 Takashi Kajinami 2020-06-03 04:34:01 UTC

I now noticed that the execution of "openstack tripleo container image prepare" is not 
expected in deployment steps currently described in our installation documentation.

If we follow the current deployment procedures, we only generate basic template files by
 openstack tripleo container image prepare default
and then actually pull/push containers during deploying undercloud/overcloud .

The way to realize 2 step image management (store all containers first into undercloud,
and then use retrieved containers in deployment) are not described in the doc.

I'll close this bug because now I feel like we should file an RFE to cover such kind of use case
if any customer expects such kind of usecase.