11:26 a.m.
Detected one or more Cirrus-CI cron-triggered jobs have failed recently:
Cron build 'release-1.4' Failed: https://cirrus-ci.com/build/5962551954505728
# Source: check_cirrus_cron workflow on containers/skopeo.
This message was generated by an automated system. Replies to the sender will bounce, be
ignored and discarded.
9:56 a.m.
New subject: Cirrus-CI cron build failures on containers/skopeo
On 1/26/22 11:26, Do Not Reply wrote:
Detected one or more Cirrus-CI cron-triggered jobs have failed
recently:
Cron build 'release-1.4' Failed: https://cirrus-ci.com/build/5962551954505728
Miloslav,
I know we have registry startup problems now and again, but this error
is new to me. Or I just don't remember seeing it recently:
Error fetching blob: invalid status code from registry 503 (Service
Unavailable)
https://cirrus-ci.com/task/4787361090371584?logs=system#L50
Anything we need to worry about?
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
10:58 a.m.
čt 27. 1. 2022 v 15:56 odesílatel Chris Evich <cevich(a)redhat.com> napsal:
On 1/26/22 11:26, Do Not Reply wrote:
> Cron build 'release-1.4' Failed:
https://cirrus-ci.com/build/5962551954505728
Miloslav,
I know we have registry startup problems now and again, but this error
is new to me. Or I just don't remember seeing it recently:
Error fetching blob: invalid status code from registry 503 (Service
Unavailable)
“Trying to pull quay.io/libpod/registry:2”
I guess it could be caused by a bug in the client, but my first guess is
that this is really a server-side unavailability correctly reported.
Mirek
11:50 a.m.
New subject: Cirrus-CI cron build failures on containers/skopeo
On 1/27/22 10:58, Miloslav Trmac wrote:
“Trying to pull quay.io/libpod/registry:2
<http://quay.io/libpod/registry:2>”
I guess it could be caused by a bug in the client, but my first guess is
that this is really a server-side unavailability correctly reported.
Oh, my mistake missing that detail. Yes, quay does break from time to
time. Okay, I'll ignore this then.
--
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
My personal robot overlord told me to include this signature line.
606
days inactive
607
days old
podman-monitor@lists.podman.io
3 comments
3 participants
participants (3)
-
Chris Evich -
Do Not Reply -
Miloslav Trmac