Hello All, This issue is resolved. The issue affecting the quay.ceph.io is resolved, Also we have moved from quay.ceph.io to quay.io in [1] to pull ceph containers for stable branches(Master branch was already using quay.io). [1] https://review.opendev.org/q/topic:ceph_monitoring_containers On Thu, May 12, 2022 at 10:52 AM Sandeep Yadav <sandeepggn93 at gmail.com> wrote: > Hello All, > > Currently, we have a check/gate blocker on Tripleo Content-provider job > for wallaby and earlier branches. The content-provider job cannot pull Ceph > related containers because quay.ceph.io is not accessible. The > details have been added to the launchpad bug[1]. > > Please hold rechecks while we are investigating the issue. In the > meantime, We are trying to switch the registry to pull ceph related > containers and waiting for the triple ceph team squad reviews on the > patch[2]. > > [1] https://bugs.launchpad.net/tripleo/+bug/1973115 > [2] https://review.opendev.org/c/openstack/tripleo-common/+/841512 > > Sandeep (on behalf of TripleO CI team) > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220513/fb2bd85a/attachment.htm>