container image prepare task should be disabled when explicit container names are defined in deploment templates

Bug #1896757 reported by Takashi Kajinami
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
In Progress
Undecided
Alex Schultz

Bug Description

Since Rocky, container image prepare task is always executed during undercloud/overcloud deployment, which inspects container images in source registry and generates a list of container images used.
However this step is unnecessary when all container images are described in a static deployment templates and makes unnecessary requirement that we should prepare required tags in local container registry, to be compatible with container image prepare task.

It would be useful to allow disabling container image prepare tasks, so that operators can depend on only static list of container images, based on the content in their local registry.

This also helps operators avoid unexpected update of container images. Currently container images prepare tasks is executed all deployment actions, and this might generate updated list of container images during deployment, even though operators didn't intend to update any containers.

description: updated
Changed in tripleo:
assignee: nobody → Takashi Kajinami (kajinamit)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-ansible (master)

Reviewed: https://review.opendev.org/737522
Committed: https://git.openstack.org/cgit/openstack/tripleo-ansible/commit/?id=a2632456c1269e86de2da834811f2250a46094c5
Submitter: Zuul
Branch: master

commit a2632456c1269e86de2da834811f2250a46094c5
Author: Takashi Kajinami <email address hidden>
Date: Tue Jun 23 21:34:22 2020 +0900

    Allow disabling image_params_prepare task

    This patch introduces a new parameter, disable_image_params_prepare, to
    plan management tasks, so that operators can disable the task to
    prepare image parameters during overcloud deployment.
    This is useful when operators use an environment file to list all
    container images with explicit tags used in deployment.

    Related-Bug: #1896757
    Change-Id: I278299f8f20c6b70eb3f26780f7454319059a12f

Changed in tripleo:
assignee: Takashi Kajinami (kajinamit) → Emilien Macchi (emilienm)
Changed in tripleo:
assignee: Emilien Macchi (emilienm) → Alex Schultz (alex-schultz)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 15.0.0

This issue was fixed in the openstack/python-tripleoclient 15.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 14.2.0

This issue was fixed in the openstack/python-tripleoclient 14.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/python-tripleoclient 13.4.3

This issue was fixed in the openstack/python-tripleoclient 13.4.3 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.