Bug 1746440

Summary: OSP15 container image upload before overcloud update is broken.
Product: Red Hat OpenStack Reporter: Sofer Athlan-Guyot <sathlang>
Component: python-tripleoclientAssignee: Sofer Athlan-Guyot <sathlang>
Status: CLOSED DUPLICATE QA Contact: Raviv Bar-Tal <rbartal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15.0 (Stein)CC: hbrock, jslagle, mburns
Target Milestone: ---   
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: 2019-08-28 13:32:42 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 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 ***