Execution environment marked as latest is not actually latest after update

[amg-web]

Environment

OS: Ubuntu 22.04
Kubernetes/K3s: v1.30.4+k3s1
AWX Operator: 2.19.1

Description

Execution environment marked as latest is not actually latest after update of AWX from older versions.

I understood this when route53 module failed with error message

"msg": "Failed to import the required Python library (botocore and boto3) on automation-job-434-lfn5s's Python /usr/bin/python3. Please read the module documentation and install it in the appropriate location. If the required library is installed, but Ansible is using the wrong Python interpreter, please consult the documentation on ansible_python_interpreter"

Then I switched template to use specific version EE and all jobs were done.

with minikube I used this in kustomization.yaml, did not checked yet if it works.

images:
  - name: quay.io/ansible/awx-operator
    newTag: 2.12.1
  - name: quay.io/ansible/awx-ee
    newTag: latest

[jpmens]

I don’t think this can be considered an issue attributed to this repository.

[amg-web]

@jpmens
yes. sorry.
I can not change label

[jpmens]

True, but you can close the issue;)

[amg-web]

What do you think about improving then close?

[jpmens]

Let me clarify: I'm just an interested party and not the owner of this repository. What I intended saying is that what you describe sounds to me to be an AWX issue, and not one caused by the code graciously provided by @kurokobo to install AWX. That's all.

[amg-web]

@jpmens
kurokobo can change label, and may be add required lines.

[amg-web]

suppose it's settings by awx itself

[kurokobo]

@amg-web
Thanks for the report, this is a known issue with AWX Operator.
I expect latest will not be used in the future. See the discussions on this thread for more details:

• Bind EE images version with DEFAULT_AWX_VERSION ansible/awx-operator#1740 (comment)
• AWX Community Meeting Agenda - March 2024 ansible/awx#14969

[kurokobo]

@jpmens
Thanks as always for your comments 😃