8000 fix two github action workflow issues by Luap99 · Pull Request #2823 · containers/image · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix two github action workflow issues #2823

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 11, 2025
Merged

fix two github action workflow issues #2823

merged 2 commits into from
Apr 11, 2025

Conversation

Luap99
Copy link
Member
@Luap99 Luap99 commented Apr 10, 2025

see both commits, the first one is obvious, the second one I like to see if that works on this repo before making PRs against all the other that use this cirrus rerun action with the same change

.github: check_cirrus_cron work around github bug

So I wondered why our email workflow only reported things for podman...

It seems the secrets: inherit is broken and no longer working, I see all
jobs on all repos failing with:

Error when evaluating 'secrets'. .github/workflows/check_cirrus_cron.yml (Line: 19, Col: 11): Secret SECRET_CIRRUS_API_KEY is required, but not provided while calling.

This makes no sense to me I doubled checked the names, nothing change
don our side and it is consitent for all projects. Interestingly this
same thing passed on March 10 and 11 (on all repos) but failed before
and after this as well.

Per[1] we are not alone, anyway let's try to get this working again even
if it means more duplication.

[1] actions/runner#2709

The linked action has been removed in podman [1] and such it will always
fail.

[1] containers/podman@130bb21

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
@TomSweeneyRedHat
Copy link
Member

LGTM

Copy link
Collaborator
@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for looking into this! The check_cirrus_cron.yml failures have been accumulating.

I don’t think this works as is, but, also, it can’t make things worse, so if you think this should be merged, please do so.

So I wondered why our email workflow only reported things for podman...

It seems the secrets: inherit is broken and no longer working, I see all
jobs on all repos failing with:

Error when evaluating 'secrets'. .github/workflows/check_cirrus_cron.yml (Line: 19, Col: 11): Secret SECRET_CIRRUS_API_KEY is required, but not provided while calling.

This makes no sense to me I doubled checked the names, nothing change
don our side and it is consitent for all projects. Interestingly this
same thing passed on March 10 and 11 (on all repos) but failed before
and after this as well.

Per[1] we are not alone, anyway let's try to get this working again even
if it means more duplication.

[1] actions/runner#2709

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Copy link
Collaborator
@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@mtrmac mtrmac merged commit 9b83c49 into containers:main Apr 11, 2025
10 checks passed
@Luap99 Luap99 deleted the github branch April 11, 2025 16:42
@Luap99
Copy link
Member Author
Luap99 commented Apr 11, 2025

Triggered the action manually, it worked! Now you should have an email that shows errors on two branches

@mtrmac
Copy link
Collaborator
mtrmac commented Apr 11, 2025

Thanks, I did get that email. And I was thinking c/image is doing so well :)

@Luap99
Copy link
Member Author
Luap99 commented Apr 11, 2025

Well that is what made me look into these things, we only got podman mails but no other repo a single flake (considering we disabled the auto rerun flake action just recently) so that couldn't be right to me and sure enough here we are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0