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 Job completes but shows as error #1979

Closed
3 tasks done
mhegreberg opened this issue Oct 22, 2024 · 1 comment
Closed
3 tasks done

AWX Job completes but shows as error #1979

mhegreberg opened this issue Oct 22, 2024 · 1 comment

Comments

@mhegreberg
Copy link

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

I have a new instance of AWX deployed via helm chart on RKE2.

when running jobs I get the following error:

Failed to JSON parse a line from worker stream. Error: Expecting value: line 1 column 1 (char 0) Line with invalid JSON data: b''

however when looking at the logs in the job's pod I see the full playbook ran and succeeded. Is there some setting I've missed that causes the logs to not be able to be read?

I ran the job about 10 times, and in one case the logs did populate.

AWX Operator version

2.19.1

AWX version

AWX 24.6.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

v1.30.4+rke2r1

Modifications

no

Steps to reproduce

  • install on rke2 cluster with 3 server nodes and 2 worker nodes
  • turn on the troubleshooting settings to preserve pods
  • import playbooks from git repo
  • run playbook
  • see error in AWX
  • read logs in job pod to confirm playbook completed

Expected results

I'd expect AWX to read the logs from the job pod

Actual results

AWX fails to read the logs from the job pod

Additional information

No response

Operator Logs

No response

@mhegreberg
Copy link
Author

I deployed all the pods and it works now. not sure what the issue was.

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

No branches or pull requests

1 participant