action #160883
closed
salt-states-openqa CI complains about "Authentication failed for 'https://gitlab.suse.de/openqa/salt-pillars-openqa.git/'" size:S
Added by jbaier_cz 7 months ago.
Updated 6 months ago.
Description
Observation¶
CI jobs like https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/2650180 complain with
+ git fetch origin
remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://gitlab.suse.de/help/topics/git/troubleshooting_git#error-on-git-fetch-http-basic-access-denied
fatal: Authentication failed for 'https://gitlab.suse.de/openqa/salt-pillars-openqa.git/'
Acceptance criteria¶
- AC1: We are receiving reminders about expired GitLab tokens
Suggestions¶
- DONE: Renew token
- Check whether we got a reminder e-mail from GitLab and if not how to enable it
Files
- Copied from action #116845: salt-states-openqa CI complains about "fatal: Authentication failed for 'https://gitlab.suse.de/openqa/salt-pillars-openqa/'" but no useful hint size:M added
- Priority changed from High to Normal
So what we're seeing here is the impact of https://about.gitlab.com/blog/2023/10/25/access-token-lifetime-limits/ .
I mitigated the urgency by generating two new tokens (could be reduced to one if we create a group scoped token), updating the pipeline variables (are they actually used?) and setting the remotes on OSD. This gives us 1y of time to come up with a proper automated solution.
- Tags changed from alert, reactive work to alert, reactive work, infra
- Subject changed from salt-states-openqa CI complains about "Authentication failed for 'https://gitlab.suse.de/openqa/salt-pillars-openqa.git/'" to salt-states-openqa CI complains about "Authentication failed for 'https://gitlab.suse.de/openqa/salt-pillars-openqa.git/'" size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to In Progress
- Assignee set to dheidler
Let's see if and what notifications I get in the coming night:
- Due date set to 2024-06-13
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Blocked
- Status changed from Blocked to In Progress
- Status changed from In Progress to Resolved
Replaced the token.
We will get a notification to the osd-admins mailing list,
when the token expires the next time.
Also available in: Atom
PDF
