tripleo train in ci.centos failing: package openstack-tripleo-common-11.6.1-0.20210413072434.dbdaa05.el8.noarch requires skopeo, but none of the providers can be installed conflicting requests

Bug #1925253 reported by wes hayutin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

3:02:33 + dnf install -y python3-tripleoclient
13:02:33 Last metadata expiration check: 0:00:06 ago on Tue Apr 20 19:02:25 2021.
13:02:33 Error:
13:02:33 Problem: package python3-tripleoclient-12.5.1-0.20210419114945.f61eccc.el8.noarch requires openstack-tripleo-common >= 11.4.0, but none of the providers can be installed
13:02:33 - package openstack-tripleo-common-11.6.1-0.20210413072434.dbdaa05.el8.noarch requires skopeo, but none of the providers can be installed
13:02:33 - conflicting requests
13:02:33 - package skopeo-1:0.1.32-6.git1715c90.module_el8.3.0+569+1bada2e4.x86_64 is filtered out by modular filtering
13:02:33 - package skopeo-1:0.1.41-4.module_el8.3.0+615+3b4f65ad.x86_64 is filtered out by modular filtering
13:02:33 - package skopeo-1:1.2.0-9.module_el8.3.0+699+d61d9c41.x86_64 is filtered out by modular filtering
13:02:33 (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
13:02:33 virt-customize: error: convert_image.sh: command exited with an error
13:02:33
13:02:33 If reporting bugs, run virt-customize with debugging enabled and include

https://ci.centos.org/job/tripleo-quickstart-promote-train-current-tripleo-delorean-minimal/320/console

Revision history for this message
wes hayutin (weshayutin) wrote :
Revision history for this message
Javier Peña (jpena-c) wrote :

Looking at the failed job, the error happens when running "virt-customize -v --smp 2 -m 2048 -a /home/stack/undercloud.qcow2 --run convert_image.sh". I've downloaded the image and checked the status of the container-tools module:

><rescue> yum list installed|grep container
container-selinux.noarch 2:2.158.0-1.module_el8.5.0+736+58cc1a5a @appstream
containernetworking-plugins.x86_64 0.9.1-1.module_el8.5.0+736+58cc1a5a @appstream
containers-common.x86_64 1:1.2.2-6.module_el8.5.0+736+58cc1a5a @appstream

><rescue> yum module list container-tools
Last metadata expiration check: 0:12:03 ago on Mon Apr 26 13:39:21 2021.
@modulefailsafe
Name Stream Profiles Summary
container-tools 3.0 [e] common Stable versions of podman 3.0, buildah 1.19,
                                   skopeo 1.2, runc, conmon, etc as well as depe
                                   ndencies such as container-selinux built and
                                   tested together, and supported as documented
                                   on the Application Stream lifecycle page.

quickstart-centos-appstreams
Name Stream Profiles Summary
container-tools rhel8 [d] common [ Most recent (rolling) versions of podman, bui
                          d] ldah, skopeo, runc, conmon, runc, conmon, CRI
                                   U, Udica, etc as well as dependencies such as
                                    container-selinux built and tested together,
                                    and updated as frequently as every 12 weeks.
container-tools 1.0 common [ Stable versions of podman 1.0, buildah 1.5, s
                          d] kopeo 0.1, runc, conmon, CRIU, Udica, etc as
                                   well as dependencies such as container-selinu
                                   x built and tested together, and supported fo
                                   r 24 months.
container-tools 2.0 common [ Stable versions of podman 1.6, buildah 1.11,
                          d] skopeo 0.1, runc, conmon, etc as well as depe
                                   ndencies such as container-selinux built and
                                   tested together, and supported as documented
                                   on the Application Stream lifecycle page.

Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled

So it looks like the issue is:

1- The undercloud image has the container-tools:3.0 module enabled, and some related packages already installed (probably being CentOS Stream 8-based)
2- The tripleo-quickstart scripts created a set of .repo files based on CentOS 8, which does not contain the container-tools:3.0 module, and removes the OS-provided repositories.
3- Due to that, when yum tries to find the skopeo package from the container-tools:3.0 module, it fails to find it and exits with error.

I guess tripleo-quickstart should generate .repo files based on CentOS Stream 8 for this job?

Revision history for this message
wes hayutin (weshayutin) wrote :

ya..

all these release files need to be updated.
https://opendev.org/openstack/tripleo-quickstart/src/branch/master/config/release/centosci for stream and container-tools 3.0

Revision history for this message
yatin (yatinkarel) wrote :
Revision history for this message
yatin (yatinkarel) wrote :

With https://review.opendev.org/c/openstack/tripleo-quickstart/+/787921 this issue got cleared

Although job failed due to different bug https://bugs.launchpad.net/tripleo/+bug/1910107, for which promotion is needed for tripleo-image-elements fix to current-tripleo.

wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Fix Released
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.