Bug 1477369 – python-openstackclient: We're forced to run 'openstack overcloud container image prepare" twice with different namespace for generating --env-file and --images-file..

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1477369 - python-openstackclient: We're forced to run 'openstack overcloud container image prepare" twice with different namespace for generating --env-file and --images-file..

Summary:	python-openstackclient: We're forced to run 'openstack overcloud container im...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	openstack-tripleo-common (Show other bugs)
Sub Component:
Version:	13.0 (Queens)
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	beta
Target Release:	13.0 (Queens)
Assigned To:	Steve Baker
QA Contact:	Omri Hochman
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-08-01 18:19 EDT by Alexander Chuzhoy
Modified:	2018-06-27 09:34 EDT (History)
CC List:	15 users (show)

See Also:
Fixed In Version:	openstack-tripleo-common-8.5.1-0.20180326153322.91f52e9.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-06-27 09:33:47 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1708303	None	None	None	2017-08-02 17:58 EDT
Red Hat Product Errata	RHEA-2018:2086	None	None	None	2018-06-27 09:34 EDT

Groups: None (edit)

Description Alexander Chuzhoy 2017-08-01 18:19:16 EDT

python-openstackclient: We're forced to run 'openstack overcloud container image prepare" twice with different namespace for generating --env-file and --images-file.

Environment:
instack-undercloud-7.1.1-0.20170714211622.el7ost.noarch
openstack-puppet-modules-10.0.0-0.20170315222135.0333c73.el7.1.noarch
openstack-tripleo-heat-templates-7.0.0-0.20170721174554.el7ost.noarch
python-openstackclient-3.11.0-0.20170613232431.c69304e.el7ost.noarch



To create an env-file we run:
openstack overcloud container image prepare --namespace=<FQDN:PORT/namespace> --env-file <filename> ...<args>


To create --images-file we run:
openstack overcloud container image prepare --namespace <namespace>   --images-file <filename>  --pull-source <FQDN:PORT>



1) 
Providing a different namespace is confusing.

2)
Can we make it possible generating both files in a single run.

Comment 1 Steve Baker 2017-08-02 17:58:41 EDT

To be clear, I think that when deploying from a local registry I think it is correct to run prepare twice, because you're preparing for two different tasks against two different registries.

However I do want to fix the consistency issue of
--namespace=<FQDN:PORT/namespace>
vs
--namespace <namespace>

I've raised a bug upstream so that --pull-source is deprecated and --namespace=<FQDN:PORT/namespace> is used consistently.

Comment 2 Steve Baker 2017-10-02 16:39:03 EDT

In Queens the following commands will be replaced with a single command backed by a mistral workflow. This workflow will also be invoked from the UI:

  overcloud container image prepare
  overcloud container image tag discover
  overcloud container image upload

Comment 7 Steve Baker 2018-03-26 19:02:49 EDT

This is now ready for testing.

If the local undercloud is being used, only a single prepare call is needed. Only the first prepare call is required, which needs to:

- specify both output files --output-images-file and --output-env-file
- specify a --push-destination argument with the <undercloud ip>:8787

This will result in an --output-env-file with appropriate undercloud registry image references

Comment 14 Omri Hochman 2018-06-06 10:56:38 EDT

Verified OSP13 RC -  prepare command need to be executed only once.

Comment 16 errata-xmlrpc 2018-06-27 09:33:47 EDT

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/RHEA-2018:2086

Note You need to log in before you can comment on or make changes to this bug.