tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates job does not update containers on overcloud

Bug #2015993 reported by Mikolaj Ciecierski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Undecided
Unassigned

Bug Description

Description
===========
Job https://zuul.opendev.org/t/openstack/job/tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates is suppose to be running containers updates on overcloud.

In tripleo-upgrade container check change https://review.opendev.org/c/openstack/tripleo-upgrade/+/872592/12 , which compares container images before overcloud ovn update run(before overcloud update) and before reboot(after overcloud update), we have discovered that containers are updated from the same tag to the same tag.

The content of files used in check can be seen below:

container-ps-before_reboot.txt

clustercheck aa83fb96012e 192.168.24.1:8787/tripleomastercentos9/openstack-mariadb:67316b1caba6cecebf7f78764dcc361c
2galera-bundle-podman-0 88a5a63ea012 192.168.24.1:8787/tripleomastercentos9/openstack-mariadb:pcmklatest
3haproxy-bundle-podman-0 854576d5a98a 192.168.24.1:8787/tripleomastercentos9/openstack-haproxy:pcmklatest
4keystone_cron b136f2daef99 192.168.24.1:8787/tripleomastercentos9/openstack-keystone:67316b1caba6cecebf7f78764dcc361c
5keystone e0d237d553a0 192.168.24.1:8787/tripleomastercentos9/openstack-keystone:67316b1caba6cecebf7f78764dcc361c
6memcached 481d3d388bfe 192.168.24.1:8787/tripleomastercentos9/openstack-memcached:67316b1caba6cecebf7f78764dcc361c
7rabbitmq-bundle-podman-0 b171403303bb 192.168.24.1:8787/tripleomastercentos9/openstack-rabbitmq:pcmklatest

container-ps-before_ovn_controller_update.txt
clustercheck aa83fb96012e 192.168.24.1:8787/tripleomastercentos9/openstack-mariadb:67316b1caba6cecebf7f78764dcc361c
2galera-bundle-podman-0 ebeaef1a4a3f 192.168.24.1:8787/tripleomastercentos9/openstack-mariadb:pcmklatest
3haproxy-bundle-podman-0 503f451f8723 192.168.24.1:8787/tripleomastercentos9/openstack-haproxy:pcmklatest
4keystone_cron b136f2daef99 192.168.24.1:8787/tripleomastercentos9/openstack-keystone:67316b1caba6cecebf7f78764dcc361c
5keystone e0d237d553a0 192.168.24.1:8787/tripleomastercentos9/openstack-keystone:67316b1caba6cecebf7f78764dcc361c
6memcached 481d3d388bfe 192.168.24.1:8787/tripleomastercentos9/openstack-memcached:67316b1caba6cecebf7f78764dcc361c
7rabbitmq-bundle-podman-0 166936af2d93 192.168.24.1:8787/tripleomastercentos9/openstack-rabbitmq:pcmklatest

In both files the same tag for container images is used: 67316b1caba6cecebf7f78764dcc361c. This indicates that container images update is skipped for some reason.

Expected result
===============
Containers on overcloud are updated from one tag to another.

Tags: upgrade
tags: added: upgrade
Revision history for this message
Marios Andreou (marios-b) wrote :

Adding some more context on the CI side - agree this is no longer working as it was intended to.

This upstream update job was taking current-tripleo and updating to the latest current tag.

You can still see this mechanism from logs e.g.: from the emit_releases_file [1]

output releases: ... 'overcloud_deploy_hash': '514d9f3921ea135d3a304d382c08d7e6', 'overcloud_target_release': 'wallaby', 'overcloud_target_hash': '744609c1eade3e921c5a4ee08d33db37',
where https://trunk.rdoproject.org/centos9-wallaby/current-tripleo/51/4d/ current-tripleo and https://trunk.rdoproject.org/centos9-wallaby/current/74/46/ current

After your ping today about the content providers it has become clearer that this probably fell through the cracks when we moved to the content provider model.

So one of the things we need is to adjust the content providers to provider the current build too.

[1] https://9f8cf072dd722b3de279-df315ac4bc3fab6cd31bd9cee1db3c46.ssl.cf1.rackcdn.com/879179/4/gate/tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates/41177b0/logs/quickstart_files/emit_releases_file.log

Revision history for this message
Sofer Athlan-Guyot (sofer-athlan-guyot) wrote :
Revision history for this message
Mikolaj Ciecierski (mciecierski) wrote :
Revision history for this message
Mikolaj Ciecierski (mciecierski) wrote :
Revision history for this message
Mikolaj Ciecierski (mciecierski) wrote :

I made some progress in solving this issue.

In https://review.opendev.org/c/openstack/tripleo-ci/+/880162 change I added additional content-provider that uses current dlrn tag.

In https://review.opendev.org/c/openstack/tripleo-quickstart-extras/+/873125 change playbook multinode-overcloud-update.yml was modified to change tag in container-prepare file to use tag from current content-prodiver job. However, tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates is still not able to pull images from content-provider registry.

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.