Otherwise they'll be skipped. The undercloud will deploy non updated images (and not fail) and the minion node will try to deploy the updated images and fail, since they didn't build.
So there are 3 identified issues:
1) Ansible didn't report a failure when minion failed to deploy (even if tripleoclient reported RC 1).
2) New container images need a specific label and this label needs to be allowed in "modify_only_with_labels" (in tripleo-quickstart-extras)
3) Figure out why the undercloud didn't fail to deploy since it's supposed to use the -updated images, but it seems it fell back on the non updated ones.
The issue is the following:
Yesterday was pushed new container images that don't use Kolla. /opendev. org/openstack/ kolla/src/ branch/ master/ docker/ base/Dockerfile .j2#L21)
The problem is that these new images don't have the LABEL "kolla_version" (see https:/
For the images to be updated in the CI jobs, they need to have this tag: /opendev. org/openstack/ tripleo- common/ src/branch/ master/ tripleo_ common/ image/kolla_ builder. py#L342- L344 /opendev. org/openstack/ tripleo- quickstart- extras/ src/branch/ master/ roles/underclou d-deploy/ templates/ containers- prepare- parameter. yaml.j2# L12-L13
https:/
https:/
Otherwise they'll be skipped. The undercloud will deploy non updated images (and not fail) and the minion node will try to deploy the updated images and fail, since they didn't build.
So there are 3 identified issues:
1) Ansible didn't report a failure when minion failed to deploy (even if tripleoclient reported RC 1).
2) New container images need a specific label and this label needs to be allowed in "modify_ only_with_ labels" (in tripleo- quickstart- extras)
3) Figure out why the undercloud didn't fail to deploy since it's supposed to use the -updated images, but it seems it fell back on the non updated ones.