Wallaby/Victoria/Train Tripleo Content-provider job failing, Unable to pull ceph related containers because quay.ceph.io is not accessible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
Description:
Wallaby/
https:/
~~~
2022-05-12 02:01:28.874676 | primary | TASK [container-build : Fail the job if missing containers exists] *************
2022-05-12 02:01:28.874764 | primary | Thursday 12 May 2022 02:01:28 +0000 (0:00:00.303) 0:41:51.978 **********
2022-05-12 02:01:28.944183 | primary | fatal: [undercloud]: FAILED! => {"changed": false, "msg": "Failed to pull following containers: ['quay.
~~~
https:/
~~~
2022-05-12 02:22:16.156916 | primary | TASK [container-build : Fail the job if missing containers exists] *************
2022-05-12 02:22:16.156967 | primary | Thursday 12 May 2022 02:22:16 +0000 (0:00:00.387) 0:52:46.512 **********
2022-05-12 02:22:16.236722 | primary | fatal: [undercloud]: FAILED! => {"changed": false, "msg": "Failed to pull following containers: ['quay.
~~~
Master branch use the different registry to pull ceph related containers:-
https:/
~~~
ceph_alertmanag
~~~
vs wallaby and before:-
~~~
ceph_prometheus
~~~
Douglas have proposed a patch [1] trying to switch the registry to pull ceph related containers and waiting for ceph team reviews on the patch[2].
[1] https:/ /review. opendev. org/c/openstack /tripleo- common/ +/841512
Victoria/train branch will need a similar fix/cherry-pick with correct container tag.