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..
python-openstackclient: We're forced to run 'openstack overcloud container im...
Status: ASSIGNED
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-openstackclient (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
low Severity low
: ga
: 12.0 (Pike)
Assigned To: Steve Baker
Alexander Chuzhoy
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-01 18:19 EDT by Alexander Chuzhoy
Modified: 2017-10-02 16:40 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1708303 None None None 2017-08-02 17:58 EDT

  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

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