panic: runtime error: invalid memory address or nil pointer dereference in awx-task

[inetpcelo]

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 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 security@ansible.com instead.)

Bug Summary

We have notice after updating from AWX 24.2.0 to 24.6.0 that the awx-task pod fails with the following error:

INFO 2025/04/01 11:30:48 Detected Error: EOF for pod awx-cpd/automation-job-460084-x9kpn. Will retry 5 more times.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1622395]
 
goroutine 29243 [running]:
github.com/ansible/receptor/pkg/workceptor.(*KubeUnit).kubeLoggingWithReconnect(0xc000226a00, 0x44645d?, 0xc001068cf0, 0xc000ce0710, 0xc000ce0720)
        /source/pkg/workceptor/kubernetes.go:388 +0xb55
created by github.com/ansible/receptor/pkg/workceptor.(*KubeUnit).runWorkUsingLogger in goroutine 29261
        /source/pkg/workceptor/kubernetes.go:830 +0xba7

We have reserached this error and issue, and we found that there is apparently an error in the ansible receptor related with the timestamp: ansible/receptor#1186 and ansible/receptor#1187. In the AWX 24.6.0 and AWX 24.6.1 the ansible receptor version is v1.4.8, and we see in next versions of the receptor the fix of this issue with the timestamp.

Is there any fix or workaround for this problem until a new AWX version with the new receptor pulls is released?

AWX version

24.6.0

Select the relevant components

• UI
• UI (tech preview)
• API
• Docs
• Collection
• CLI
• Other

Installation method

kubernetes

Modifications

no

Ansible version

No response

Operating system

No response

Web browser

No response

Steps to reproduce

We are receiving this error after several executions of the same task.

Expected results

We expect no errors like in the previous executions.

Actual results

We obtain the error descripted in the bug report in the awx-task pod:

INFO 2025/04/01 11:30:48 Detected Error: EOF for pod awx-cpd/automation-job-460084-x9kpn. Will retry 5 more times.
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1622395]
 
goroutine 29243 [running]:
github.com/ansible/receptor/pkg/workceptor.(*KubeUnit).kubeLoggingWithReconnect(0xc000226a00, 0x44645d?, 0xc001068cf0, 0xc000ce0710, 0xc000ce0720)
        /source/pkg/workceptor/kubernetes.go:388 +0xb55
created by github.com/ansible/receptor/pkg/workceptor.(*KubeUnit).runWorkUsingLogger in goroutine 29261
        /source/pkg/workceptor/kubernetes.go:830 +0xba7

Additional information

No response

[tvo318]

@inetpcelo Have you tried to pull in the latest changes from devel to see if the fix made it in there?