awx-ee:latest throws argument error

[macskay]

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

When I tried to start AWX the awx-task deployment wants to run the initContainer with awx-ee:latest. However the latest seems to have a bug where command line arguments are not recognized.

Error: unknown flag: --cert-makereq
Usage:
  receptor [flags]

Flags:
      --config string   config file (default is $HOME/receptor.yaml)
  -h, --help            help for receptor
      --version         Show the Receptor version

Error: unknown flag: --cert-signreq
Usage:
  receptor [flags]

Flags:
      --config string   config file (default is $HOME/receptor.yaml)
  -h, --help            help for receptor
      --version         Show the Receptor version
2024-08-06T08:07:27.589748904Z

AWX Operator version

2.12.1

AWX version

23.8.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.27.7

Modifications

no

Steps to reproduce

Install version awx-operator 2.12.1 via Helm with

AWX:
  enabled: true

Expected results

awx-task starts with the initContainer successfully running through.

Actual results

awx-task does not spin up bexause initContainer fails with the message above leading to the actual containers never starting as the pre-condition of a successfully ended initContainer is never met.

Additional information

No response

Operator Logs

No response

[Aminechouchene98]

i have the same error with manifests not helm chart
Client Version: v1.28.11+rke2r1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.11+rke2r1

[sdigit]

Same error here. The operator wants to use awx-ee:latest and awx-ee:latest lacks the receptor version it needs, from the look of it.
I ended up having to edit the deployment and disable the operator for now, as downgrading the operator one version didn't fix it either.

[sdigit]

Another note: I tried devel branch of the operator, which does use 24.6.1 as version for awx-ee, however that didn't fix it either, as when I looked at the containers brought up in the awx-task deployment, some awx-ee containers had :24.6.1 and others had :latest still.

[Aminechouchene98]

after i added this the problem is fixed for me
security_context_settings:
runAsGroup: 0
runAsUser: 0
fsGroup: 0
fsGroupChangePolicy: OnRootMismatch

[aimee-889]

we had the same problem the last days, but today the latest image worked again, so it seems to be fixed for us :)

[jbrowning32]

I'm still stuck on this, even on a fresh install of the awx-demo I get Init:CrashLoopBackOff on the task pod.

[jbrowning32]

Following up on this, I was able to resolve my issue by upgrading to Operator 2.19.1 (AWX v24.6.1). I'm using an external postgres db which also had to be upgraded from 13 to 15.