Deployment of AWX-OPERATOR fails

moomin893 · December 13, 2024, 9:39am

AWX-OPERATOR version: 0.20

AWX web service will not start.

NAME                                                   READY   STATUS    RESTARTS   AGE
pod/awx-demo-postgres-0                                1/1     Running   0          53m
pod/awx-operator-controller-manager-579fd74d78-k7z2r   2/2     Running   0          54m

Output of awx-operator :

TASK [installer : Apply Resources] *********************************************
task path: /opt/ansible/roles/installer/tasks/resources_configuration.yml:30
changed: [localhost] => (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [localhost] => (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [localhost] => (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
changed: [localhost] => (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
failed: [localhost] (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
ok: [localhost] => (item=None) => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": false}
fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}

PLAY RECAP *********************************************************************
localhost : ok=39 changed=3 unreachable=0 failed=1 skipped=27 rescued=0 ignored=0

awx-demo.yml

---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
  name: awx-demo
spec:
  service_type: nodeport
  postgres_storage_class: awx-postgres-volume

I want to install AWX-OPERATOR version: 0.20. Please tell me what I am doing wrong.

mcen1 · December 13, 2024, 1:18pm

Are you really trying to install version 0.20 Release 0.20.0 · ansible/awx-operator · GitHub, which was released in March of 2022? Is there any particular reason you aren’t trying a more recent version?

Regardless, it’s impossible to recommend anything based off what you’ve shown here obviously since everything has “the output has been hidden due to no_log” thing. Per the output has been hidden due to the fact that 'no_log: true' was specified for this result · Issue #1574 · ansible/awx-operator · GitHub
you can add no_log: False under “spec” on your awx CR yaml file and the logs should show up

moomin893 · December 13, 2024, 1:59pm

I want to deploy AWX 0.20 because many people want to use AWX that I have been using.

I added no_log to awx-cr.yml but got an error.

\"reason\":\"Failed\"
,\"status\":\"True\",\"type\":\"Failure\"}]}}": strict decoding error: unknown field "spec.no_log"

mcen1 · December 13, 2024, 4:09pm

Downloading Release 0.20.0 · ansible/awx-operator · GitHub and grepping for no_log yields every single instance of no_log hardcoded to True, so I guess this feature was added in a later version.

Someone with more knowledge can correct me if I’m mistaken.

~/awx-operator-0.20.0$ grep -ri no_log *
roles/backup/tasks/dump_generated_secret.yml:  no_log: true
roles/backup/tasks/dump_generated_secret.yml:  no_log: true
roles/backup/tasks/dump_generated_secret.yml:  no_log: true
roles/backup/tasks/secrets.yml:  no_log: true
roles/backup/tasks/secrets.yml:  no_log: true
roles/backup/tasks/postgres.yml:  no_log: true
roles/backup/tasks/postgres.yml:  no_log: true
roles/backup/tasks/postgres.yml:  no_log: true
roles/backup/tasks/postgres.yml:  no_log: true
roles/backup/tasks/postgres.yml:  no_log: true
roles/backup/tasks/dump_secret.yml:        no_log: true
roles/backup/tasks/dump_secret.yml:        no_log: true
roles/backup/tasks/dump_secret.yml:        no_log: true
roles/installer/tasks/load_route_tls_secret.yml:  no_log: true
roles/installer/tasks/load_route_tls_secret.yml:  no_log: true
roles/installer/tasks/load_route_tls_secret.yml:  no_log: true
roles/installer/tasks/load_ldap_cacert_secret.yml:  no_log: true
roles/installer/tasks/load_ldap_cacert_secret.yml:  no_log: true
roles/installer/tasks/cleanup.yml:      no_log: true
roles/installer/tasks/admin_password_configuration.yml:  no_log: true
roles/installer/tasks/admin_password_configuration.yml:  no_log: true
roles/installer/tasks/admin_password_configuration.yml:  no_log: true
roles/installer/tasks/admin_password_configuration.yml:      no_log: true
roles/installer/tasks/admin_password_configuration.yml:      no_log: true
roles/installer/tasks/admin_password_configuration.yml:  no_log: true
roles/installer/tasks/admin_password_configuration.yml:  no_log: true
roles/installer/tasks/migrate_data.yml:  no_log: true
roles/installer/tasks/migrate_data.yml:  no_log: true
roles/installer/tasks/migrate_data.yml:  no_log: true
roles/installer/tasks/migrate_data.yml:  no_log: true
<...>

As opposed to a more recent version:

~/awx-operator-2.19.1$ grep -ri no_log *
ansible/helm-release.yml:          no_log: true
config/crd/bases/awx.ansible.com_awxrestores.yaml:              no_log:
config/crd/bases/awx.ansible.com_awxrestores.yaml:                description: Configure no_log for no_log tasks
config/crd/bases/awx.ansible.com_awxbackups.yaml:              no_log:
config/crd/bases/awx.ansible.com_awxbackups.yaml:                description: Configure no_log for no_log tasks
config/crd/bases/awx.ansible.com_awxs.yaml:              no_log:
config/crd/bases/awx.ansible.com_awxs.yaml:                description: Configure no_log for no_log tasks
config/manifests/bases/awx-operator.clusterserviceversion.yaml:        path: no_log
config/manifests/bases/awx-operator.clusterserviceversion.yaml:        path: no_log
config/manifests/bases/awx-operator.clusterserviceversion.yaml:        path: no_log
docs/user-guide/advanced-configuration/no-log.md:Configure no_log for tasks with no_log
docs/user-guide/advanced-configuration/no-log.md:| no_log | No log configuration | 'true'  |
docs/user-guide/advanced-configuration/no-log.md:Example configuration of `no_log` parameter
docs/user-guide/advanced-configuration/no-log.md:    no_log: true
docs/troubleshooting/debugging.md:It is possible to show task output for debugging by setting no_log to false on the AWX CR spec.
docs/troubleshooting/debugging.md:This will show output in the awx-operator logs for any failed tasks where no_log was set to true.
docs/troubleshooting/debugging.md:  no_log: false                  # <------------
molecule/default/templates/awx_cr_molecule.yml.j2:  no_log: false
playbooks/awx.yml:    no_log: true
playbooks/awx.yml:      no_log: "{{ no_log }}"
roles/backup/tasks/dump_ingress_tls_secrets.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_ingress_tls_secrets.yml:      no_log: "{{ no_log }}"
roles/backup/tasks/dump_ingress_tls_secrets.yml:      no_log: "{{ no_log }}"
roles/backup/tasks/dump_generated_secret.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_generated_secret.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_generated_secret.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/secrets.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/secrets.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_receptor_secrets.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_receptor_secrets.yml:      no_log: "{{ no_log }}"
roles/backup/tasks/dump_receptor_secrets.yml:      no_log: "{{ no_log }}"
roles/backup/tasks/postgres.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/postgres.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/postgres.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/postgres.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/postgres.yml:  no_log: "{{ no_log }}"
roles/backup/tasks/dump_secret.yml:        no_log: "{{ no_log }}"
roles/backup/tasks/dump_secret.yml:        no_log: "{{ no_log }}"
roles/backup/tasks/dump_secret.yml:        no_log: "{{ no_log }}"
roles/backup/defaults/main.yml:# Set no_log settings on certain tasks
roles/backup/defaults/main.yml:no_log: true
roles/installer/tasks/load_route_tls_secret.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/load_route_tls_secret.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/load_route_tls_secret.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/load_ldap_cacert_secret.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/load_ldap_cacert_secret.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/cleanup.yml:      no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:      no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:      no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/admin_password_configuration.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/migrate_data.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/migrate_data.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/migrate_data.yml:  no_log: "{{ no_log }}"
roles/installer/tasks/migrate_data.yml:  no_log: "{{ no_log }}"
<...>

At any rate, this is probably why it would make sense to utilize a newer version of the operator instead of standing up additional instances of two-year-old software that has unaddressed bugs and missing features.

moomin893 · December 13, 2024, 11:51pm

Thank you for your research.

Error source.
Changing hardcoded no_log does not apply lo_nog:false

github.com

ansible/awx-operator/blob/0.21.0/roles/installer/tasks/resources_configuration.yml#L30


      
          - name: Set user provided control plane ee image
            set_fact:
              _custom_control_plane_ee_image: "{{ control_plane_ee_image }}"
            when:
              - control_plane_ee_image | default([]) | length
          
          - name: Set Control Plane EE image URL
            set_fact:
              _control_plane_ee_image: "{{ _custom_control_plane_ee_image | default(lookup('env', 'RELATED_IMAGE_CONTROL_PLANE_EE')) | default(_control_plane_ee_image, true) }}"
          
          - name: Apply Resources
            k8s:
              apply: yes
              definition: "{{ lookup('template', item + '.yaml.j2') }}"
              wait: yes
            register: tower_resources_result
            loop:
              - 'config'
              - 'app_credentials'
              - 'service_account'
              - 'persistent'

resources_configuration.yml:30

- name: Apply Resources
k8s:
apply: yes
definition: "{{ lookup('template', item + '.yaml.j2') }}"
wait: yes
register: tower_resources_result
loop:
- 'config'
- 'app_credentials'
- 'service_account'
- 'persistent'
- 'service'
- 'ingress'
no_log: true

I really want to use AWX version 21.0.0.
Is it possible to install AWX 21.0.0 using the latest AWXoperator?

Topic		Replies	Views
My deployment failed while tried to deploy awx AWX Project awx	3	1	September 8, 2022
AWX-OPERATOR no_log at false AWX Project awx	9	5	April 14, 2022
21.1.0 to 21.2.0 Upgrade Failure AWX Project awx	2	1	September 30, 2022
AWX restore fails (postgres part succeeds however) AWX Project awx	4	1	August 3, 2022
AWX-Operator Fails at [Check for presence of awx-task Deployment] Get Help awx , kubernetes , ee	0	166	April 4, 2024

Deployment of AWX-OPERATOR fails

Related topics