Skip to content
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

AWX jobs are timing out #3887

Open
Haroon-Khel opened this issue Feb 24, 2025 · 1 comment
Open

AWX jobs are timing out #3887

Haroon-Khel opened this issue Feb 24, 2025 · 1 comment

Comments

@Haroon-Khel
Copy link
Contributor

I have tried to run the Deploy Static Docker Container job and my debug fork job, both times the job appears to be running, but with no output.

https://awx.adoptium.net/#/jobs/playbook/1977/output this job timed out after 2 hours with the following error log

Receptor detail:
Error creating pod: timed out waiting for the condition
@sxa
Copy link
Member

sxa commented Mar 5, 2025

Cannot currently access AWX via kubectl:

awx@adoptium-awx:~$ kubectl get services
E0305 10:37:16.069850 2818858 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0305 10:37:16.071856 2818858 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0305 10:37:16.073767 2818858 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0305 10:37:16.075940 2818858 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0305 10:37:16.077709 2818858 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the client to provide credentials)
awx@adoptium-awx:~$

May be that a certificate has expired one year after the instance was created. Similar issue described at https://blog.differentpla.net/blog/2023/10/29/k3s-unauthorized/ although https://docs.k3s.io/cli/certificate indicates that a restart might cure it as the certificates will be regenerated.

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

No branches or pull requests

2 participants