AWX-OPERATOR no_log at false

Archives AWX Project
1

Hello,

I have a failed task on AWX deployment by awx-operator 0.18.0.
I dont have this error on awx-operator in 0.16.1.
The failed task is in no_log …
Is there a way to pass the no_log to false ?

I try replace no_log to false in code, and redeploy awx-operator, but log are always in no_log = True …

Can you help me ?

Regards,

2

Output of awx-operator :


TASK [installer : Apply Resources] *********************************************
task path: /opt/ansible/roles/installer/tasks/resources_configuration.yml:20
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
3

Hello,

{“level”:“error”,“ts”:1647008680.0272427,“logger”:“controller-runtime.manager.controller.awx-controller”,“msg”:“Reconciler error”,“name”:“awx”,“namespace”:“awx-test”,“error”:“event runner on failed”,“stacktrace”:“sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.2/pkg/internal/controller/controller.go:253\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.9.2/pkg/internal/controller/controller.go:214”}
{“level”:“info”,“ts”:1647008681.6396737,“logger”:“logging_event_handler”,“msg”:“[playbook task start]”,“name”:“awx”,“namespace”:“awx-test”,“gvk”:“awx.ansible.com/v1beta1, Kind=AWX”,“event_type”:“playbook_on_task_start”,“job”:“3634993104103387969”,“EventData.Name”:“installer : Patching labels to AWX kind”}

Any idea ?

Regards

4

Hi!

Can you please provide more information about your deployment (gce, minikube?), and share your awx-demo.yml (or whatever you are using)? Thanks

Seth

5

Hi,
same problem here:
Operator verison 0.14.0
AWX version 19.4.0
Seems like deployment process succeeded, but this error does appear in manager.

6

https://github.com/ansible/awx-operator/issues/640

7

Hey folks, i was able to track down the step when issue appear in my depoyment:

after NodePort service is up, i change port number, like so:

kubectl get svc awx-service -oyaml | sed '/ nodePort: /c\ nodePort: 30080' | kubectl apply -f -

As i can see, it’s about aplying resources from roles/installer/tasks/resources_configuration.yml:20

{"level":"error","ts":1649424483.421153,"logger":"logging_event_handler","msg":"","name":"awx","namespace":"awx-namespace","gvk":"awx.ansible.com/v1beta1, Kind=AWX","event_type":"runner_on_failed","job":"1871149835079166338","EventData.Task":"Apply Resources","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/roles/installer/tasks/resources_configuration.yml:20","error":"[playbook task failed]"}

Any ideas on how to dig deeper?
…
lines 20+

- 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
8

And issue didn’t appear with operator v 0.20.0
Not actual,
Thank you.

9

Forgot to mention my setup, may be it could help somehow though:
Self-hosted Kubernetes v1.21.10 provided by RKE
No ingress

---
apiVersion: awx.ansible.com/v1beta1
kind: AWX
metadata:
name: awx
namespace: awx-namespace
spec:
service_type: nodeport
nodeport_port: 30080
---
apiVersion: v1
kind: Secret
metadata:
name: awx-secret-key
namespace: awx-namespace
stringData:
secret_key: awxsecret
type: Opaque
---
apiVersion: v1
kind: Secret
metadata:
name: postgres-postgres-configuration
namespace: awx-namespace
stringData:
password: pgpasswd
type: managed
type: Opaque
10

Actually it did appear because of db secret problem. Opening a new
tread for it now.
To summarize - this error appear every time something goes wrong on
deployment step.