You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that AWX is open source software provided for free and that I might not receive a timely response.
I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.)
Bug Summary
Job fails with the following output
{
"status": "error",
"job_explanation": "Failed to extract private data directory on worker.",
"result_traceback": "Traceback (most recent call last):File \"/usr/local/lib/python3.11/site-packages/ansible_runner/streaming.py\", line 183, in rununstream_dir(self._input, data['zipfile'], self.private_data_dir)File \"/usr/local/lib/python3.11/site-packages/ansible_runner/utils/streaming.py\", line 71, in unstream_dirdata = source.read(chunk_size)^^^^^^^^^^^^^^^^^^^^^^^File \"/usr/local/lib/python3.11/site-packages/ansible_runner/utils/base64io.py\", line 282, in readresults.write(base64.b64decode(data))^^^^^^^^^^^^^^^^^^^^^^File \"/usr/lib64/python3.11/base64.py\", line 88, in b64decodereturn binascii.a2b_base64(s, strict_mode=validate)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^binascii.Error: Incorrect padding"
}
AWX version
24.2.0
Select the relevant components
UI
UI (tech preview)
API
Docs
Collection
CLI
Other
Installation method
kubernetes
Modifications
no
Ansible version
2.15.10
Operating system
Linux 652c6ec34339 4.18.0-553.8.1.el8_10.x86_64 #1 SMP Fri Jun 14 03:19:37 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Web browser
Chrome
Steps to reproduce
We are running a basic job template, running on a container group on AKS.
Every 10-20 runs a job fails with the padding error described in the summary, we can see this error in the pod logs running the custom EE
Expected results
The job should work the same as the others
Actual results
The job fails and the UI shows "Failed to JSON parse a line from worker stream. Error: Expecting value: line 1 column 1 (char 0) Line with invalid JSON data: b''"
the job output shows "Receptor detail: Error with pod's stdout: write /tmp/receptor/awx-task-5f558b7586-sz78m/ze2sUz4x/stdout: file already closed"
Additional information
AWX version: 24.2.0
AWX Operator: 2.15.0
Ansible Runner: 2.3.6
EE image: 24.2.0
Kubernetes version: v1.29.4 and v1.30.2
Ansible version: 2.15.10
We have gathered the files from the receptor in the awx-ee container for a failed job (stdout file is empty)
We have successfully decoded and uncompressed the zip data included in the stdin file
raw logs from pod running job
2024-08-12T12:14:11.409468343Z stdout F {"status": "error", "job_explanation": "Failed to extract private data directory on worker.", "result_traceback": "Traceback (most recent call last):\n File \"/usr/local/lib/python3.11/site-packages/ansible_runner/streaming.py\", line 183, in run\n unstream_dir(self._input, data['zipfile'], self.private_data_dir)\n File \"/usr/local/lib/python3.11/site-packages/ansible_runner/utils/streaming.py\", line 71, in unstream_dir\n data = source.read(chunk_size)\n ^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/local/lib/python3.11/site-packages/ansible_runner/utils/base64io.py\", line 282, in read\n results.write(base64.b64decode(data))\n ^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/lib64/python3.11/base64.py\", line 88, in b64decode\n return binascii.a2b_base64(s, strict_mode=validate)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nbinascii.Error: Incorrect padding\n"}
awx-task pod logs around the time the job fails
awx-rsyslog awx-task-6b95d77bbb-sbv76awx-task2024-08-12 12:11:33,252 INFO supervisord started with pid 7
awx-task-6b95d77bbb-sbv76awx-ee(changed: True)
awx-task-6b95d77bbb-sbv76awx-rsyslogERROR 2024/08/12 12:14:11 Error reading stdin: %!!(MISSING)s(<nil>)
awx-task-6b95d77bbb-sbv76awx-task2024-08-12 12:11:34,255 INFO spawned: 'superwatcher' with pid 28
awx-task-6b95d77bbb-sbv76awx-ee2024-08-12 12:11:39,579 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
awx-task-6b95d77bbb-sbv76awx-rsyslogE0812 12:14:11.400577 14 v2.go:104] write tcp 100.65.6.186:42510->100.64.0.1:443: write: connection reset by peer
awx-task-6b95d77bbb-sbv76awx-task2024-08-12 12:11:34,255 INFO spawned: 'superwatcher' with pid 28
awx-task-6b95d77bbb-sbv76awx-ee2024-08-12 12:11:39,579 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
awx-task-6b95d77bbb-sbv76awx-rsyslog ERROR 2024/08/12 12:14:11 Error streaming pod logs to stdout for pod awx/automation-job-96995-r78qq. Error: write /tmp/receptor/awx-task-6b95d77bbb-sbv76/izVSBFQ4/stdout: file already closed
awx-task2024-08-12 12:11:34,258 INFO spawned: 'rsyslog-4xx-recovery' with pid 29
We tried a bunch of AAP versions and EE version, but the problem persists.
We have also tried this setting with no changes
Please confirm the following
[email protected]
instead.)Bug Summary
Job fails with the following output
AWX version
24.2.0
Select the relevant components
Installation method
kubernetes
Modifications
no
Ansible version
2.15.10
Operating system
Linux 652c6ec34339 4.18.0-553.8.1.el8_10.x86_64 #1 SMP Fri Jun 14 03:19:37 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
Web browser
Chrome
Steps to reproduce
We are running a basic job template, running on a container group on AKS.
Every 10-20 runs a job fails with the padding error described in the summary, we can see this error in the pod logs running the custom EE
Expected results
The job should work the same as the others
Actual results
The job fails and the UI shows "Failed to JSON parse a line from worker stream. Error: Expecting value: line 1 column 1 (char 0) Line with invalid JSON data: b''"
the job output shows "Receptor detail: Error with pod's stdout: write /tmp/receptor/awx-task-5f558b7586-sz78m/ze2sUz4x/stdout: file already closed"
Additional information
AWX version: 24.2.0
AWX Operator: 2.15.0
Ansible Runner: 2.3.6
EE image: 24.2.0
Kubernetes version: v1.29.4 and v1.30.2
Ansible version: 2.15.10
We have gathered the files from the receptor in the awx-ee container for a failed job (stdout file is empty)
status file:
stdin file: (zip data excluded)
We have successfully decoded and uncompressed the zip data included in the stdin file
raw logs from pod running job
awx-task pod logs around the time the job fails
We tried a bunch of AAP versions and EE version, but the problem persists.
We have also tried this setting with no changes
ee_extra_env: |
value: disabled
The text was updated successfully, but these errors were encountered: