Bug 1746440 - OSP15 container image upload before overcloud update is broken.
Summary: OSP15 container image upload before overcloud update is broken.
Keywords:
Status: CLOSED DUPLICATE of bug 1741247
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Sofer Athlan-Guyot
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-28 13:22 UTC by Sofer Athlan-Guyot
Modified: 2019-08-28 13:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-28 13:32:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sofer Athlan-Guyot 2019-08-28 13:22:59 UTC
Description of problem:  Before updating the overcloud we need to update all the image in the local registry in the undercloud.

The command used in OSP14 for doing so is:

  openstack overcloud external-update run --tags container_image_prepare

That command doesn't work anymore in osp15.  First issue is that the external tasks are just ignored, second issue is that the containers are downloaded inside the mistral-executor container and not on the undercloud.

This result in a failure during overcloud update where we can't find the new images in the undercloud registry.

Version-Release number of selected component (if applicable): Beta-1.0/trunk to passed_phase2 

The workaround is to use another command directly from the undercloud:

sudo openstack tripleo container image prepare \
    -e ~/containers-prepare-parameter.yaml \
    --output-env-file containers-prepare-parameter.yaml

But we'd rather have the same interface than in osp14.

Comment 1 Sofer Athlan-Guyot 2019-08-28 13:32:42 UTC

*** This bug has been marked as a duplicate of bug 1741247 ***


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