August 2022 - Podman-monitor - Podman List Archives

Cirrus-CI cron build failures on containers/podman

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build 'v3.3.1-rhel' Failed: https://cirrus-ci.com/build/5376839685242880 Cron build 'v3.2.3-rhel' Failed: https://cirrus-ci.com/build/6560728864784384 Cron build 'v3.4.2-rhel' Failed: https://cirrus-ci.com/build/6328108872630272 Cron build 'main' Failed: https://cirrus-ci.com/build/6204408043143168 Cron build 'v3.4' Failed: https://cirrus-ci.com/build/5295825260642304 # Source: check_cirrus_cron workflow on containers/podman. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

6 months, 3 weeks

1
0
0 / 0

HEADS UP: imgobsolete run on 8-30 might fail

by Chris Evich

While investigating something else, I noticed a problem in the 'latest' image-build. I fixed that, but I also noticed a problem in it's script that's going to make it fail. This will fix it: https://github.com/containers/automation_images/pull/188 For reference, the error this should address looks like: ...cut... Obsoleting EC2 image fedora-netavark-aws-arm64-c6298910627987456: ...something... An error occurred (UnauthorizedOperation) when calling the EnableImageDeprecation operation: You are not authorized to perform this operation. ...blah...blah...blah... ...cut... That _SHOULD_ read: Obsoleting EC2 image AMI-0987654321 -- Chris Evich (he/him), RHCA III Senior Quality Assurance Engineer My personal robot overlord told me to include this signature line.

6 months, 3 weeks

1
1
0 / 0

Cirrus-CI cron build failures on containers/buildah

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build '1.21' Failed: https://cirrus-ci.com/build/6092926831820800 # Source: check_cirrus_cron workflow on containers/buildah. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

6 months, 4 weeks

1
0
0 / 0

Cirrus-CI cron build failures on containers/podman

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build 'v3.3.1-rhel' Failed: https://cirrus-ci.com/build/5034696550645760 Cron build 'v3.0.1-rhel' Failed: https://cirrus-ci.com/build/5841697551679488 Cron build 'v3.2.3-rhel' Failed: https://cirrus-ci.com/build/4728914743394304 Cron build 'v3.4.2-rhel' Failed: https://cirrus-ci.com/build/6045346513027072 Cron build 'main' Failed: https://cirrus-ci.com/build/6013093019910144 Cron build 'v3.4' Failed: https://cirrus-ci.com/build/5981418005200896 # Source: check_cirrus_cron workflow on containers/podman. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

6 months, 4 weeks

1
0
0 / 0

Cirrus-CI cron build failures on containers/podman

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build 'v3.3.1-rhel' Failed: https://cirrus-ci.com/build/5871559922417664 Cron build 'v3.0.1-rhel' Failed: https://cirrus-ci.com/build/5611588068573184 Cron build 'v3.2.3-rhel' Failed: https://cirrus-ci.com/build/4812929504641024 Cron build 'main' Failed: https://cirrus-ci.com/build/5786823204012032 # Source: check_cirrus_cron workflow on containers/podman. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

6 months, 4 weeks

2
1
0 / 0

[AWS Trusted Advisor] Your weekly update on AWS usage, 8/30/22

by trustedadvisornotification＠amazon.com

6 months, 4 weeks

1
0
0 / 0

Cirrus-CI cron build failures on containers/buildah

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build '1.24' Failed: https://cirrus-ci.com/build/6393172124237824 Cron build '1.22' Failed: https://cirrus-ci.com/build/6572517644042240 # Source: check_cirrus_cron workflow on containers/buildah. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

6 months, 4 weeks

1
0
0 / 0

Cirrus-CI cron build failures on containers/automation_images

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build 'VM' Failed: https://cirrus-ci.com/build/Image Maintenance 5700512883408896 # Source: .github/workflows/check_cirrus_cron.yml workflow on containers/automation_images. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

7 months

1
0
0 / 0

Cirrus-CI cron build failures on containers/buildah

by Do Not Reply

Detected one or more Cirrus-CI cron-triggered jobs have failed recently: Cron build '1.24' Failed: https://cirrus-ci.com/build/6246310952042496 # Source: check_cirrus_cron workflow on containers/buildah. This message was generated by an automated system. Replies to the sender will bounce, be ignored and discarded.

7 months

1
0
0 / 0

Constant re-running

by Chris Evich

Lokesh & Ed, Just wondering out-loud: Release-branch flakes seem really annoying, and with a very high fix-it barrier (if even possible). I'm thinking running them daily is probably excessive. What if we dialed back the schedule on non-main branches to...maybe once-per-week or month each? WDYT? -- Chris Evich (he/him), RHCA III Senior Quality Assurance Engineer My personal robot overlord told me to include this signature line.

7 months

2
1
0 / 0

2023

2022

2021

Podman-monitor August 2022