prebuilt kolla/centos-source-bifrost-deploy:ussuri image has unreachable yum/dnf repositories

Bug #1902101 reported by Lukasz Zalewski
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Fix Released
Medium
Mark Goddard

Bug Description

Hi there

Prebuilt kolla/centos-source-bifrost-deploy:ussuri image from dockerhub uses http://mirror-int.ord.rax.opendev.org as baseurl in some of the yum CentOS-*.repo files, which is not reachable for me.
in contrast kolla/centos-source-bifrost-deploy:10.1.0 uses http://mirror.dfw.rax.opendev.org which does work.

Is mirror-int.ord.rax.opendev.org temporarily down, or is this an issue with the build (internal repository used)?

Regards

Lukasz

description: updated
Revision history for this message
Mark Goddard (mgoddard) wrote :

Hi. We build the images in Zuul CI with local package mirrors. The mirrors are not guaranteed to be stable. Normally the package repos inside images are not used after the image is built, but bifrost is not a standard application container.

To be honest, if you are just starting with Bifrost, I would suggest using Bifrost directly, rather than the Kolla image.

Revision history for this message
Lukasz Zalewski (lzal3wski) wrote :

Hi Mark

I'm currently looking at kayobe deployment and the error came up during the kayobe seed service deploy phase. I wanted to use the pre-built container, as there was no need for me to make any customisations and I wanted to avoid building them locally.

I have noticed there was an update on the docker hub to the bifrost container and the repositories are working again. Can I assume this will stay as is, or can this change again when the container is updated?

Revision history for this message
Mark Goddard (mgoddard) wrote :

The repo in the image can change from day to day, depending on where the image was built. It would be better if we switched back to the public mirrors.

You can build an image locally via 'kayobe seed container image build', if you have a local registry to push to.

Revision history for this message
Lukasz Zalewski (lzal3wski) wrote :

Thanks Mark

Using public mirrors would be great. I will look into the local build too.

Changed in kolla:
assignee: nobody → Mark Goddard (mgoddard)
status: New → In Progress
Revision history for this message
Mark Goddard (mgoddard) wrote :
Changed in kolla:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 9.3.1

This issue was fixed in the openstack/kolla 9.3.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 12.0.0.0rc1

This issue was fixed in the openstack/kolla 12.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 10.3.0

This issue was fixed in the openstack/kolla 10.3.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 11.1.0

This issue was fixed in the openstack/kolla 11.1.0 release.

Changed in kolla:
status: In Progress → 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.