Skip to content

Conversation

flatcar-infra
Copy link

Updated GLSA metadata

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@chewi chewi merged commit beedbca into main Oct 2, 2025
4 of 5 checks passed
@chewi chewi deleted the buildbot/monthly-glsa-metadata-updates-2025-10-01 branch October 2, 2025 15:59
@krnowak
Copy link
Member

krnowak commented Oct 2, 2025

Oi, this should have been put on hold - this will likely make the nightly builds fail, because we are still having the old pam version and this will trigger the GLSA check. Let's see.

Copy link

github-actions bot commented Oct 2, 2025

@chewi
Copy link
Contributor

chewi commented Oct 3, 2025

Sorry, I thought it was harmless. 😢 I think PRs like this need a note about what we should check or watch out for when merging.

@tormath1
Copy link
Contributor

tormath1 commented Oct 3, 2025

So yeah the CI is failing because:

 This system is affected by the following GLSAs:
 202508-01
 202505-01

Let's revert this commit while PAM issue is being addressed.

EDIT: #3337

@dongsupark
Copy link
Member

dongsupark commented Oct 8, 2025

Just FYI, we have 2 options:

  1. Do not update GLSA metadata, a.k.a. keep such bot PRs open until pam could be updated. Basically what we already do.
  2. Add the 2 GLSAs to GLSA_ALLOWLIST, to avoid such CI failures. I am fine with this approach as well, as long as the pam update seems not so trivial.

@krnowak
Copy link
Member

krnowak commented Oct 8, 2025

Let's go with 1. I'm working on the PAM update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants