ansible-navigator : Error with awx_display

[JS G.]

Hello, 

I'm a newbi on ansible-navigator.
I try to use it, for playbooks developement on VMs before put my playbooks on AWX.
I configured ansible-navigator to use awx-ee image with podman.
When I launch my playbook bye ansible-navigatror, i have this error :

ERROR! Invalid callback for stdout specified: awx_display

I try to set another stdout (minimal) callback in my ansible.cfg (/etc/ansible is in volume_mounts of execution_environment configuration), but I have always the same message ... 

Ansible-navigator dump say always : DEFAULT_STDOUT_CALLBACK(env: ANSIBLE_STDOUT_CALLBACK) = awx_display

Can you help me ?

Regards,  

[Michael Nelson]

Hi,

Looks like you are using an image built for use with awx.

Try with this config:

---
ansible-navigator:
  execution-environment:
    container-engine: podman
    enabled: true
    environment-variables:
      set:
        ANSIBLE_CONFIG: ansible.cfg
    image: antuelle78/awx-ee:latest
    pull:
      #arguments:
        #- "--tls-verify=true"
      policy: always
#     volume-mounts:
#       - src: "/tmp"
#         dest: "/test1"
#         options: "Z"
    container-options:
      - "--net=host"
  logging:
    level: critical
  #mode: stdout
#     append: False
#     file: /tmp/log.txt
  playbook-artifact:
    enable: false
#     replay: /tmp/test_artifact.json
#     save-as: /tmp/test_artifact.json
#
  time-zone: YourTimeZone

If it works, then you need to pay attention to the image used.

You can build your own with ansible-builder.

Regards,

Antuelle78

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/eb9fae71-4361-4912-bff5-a23ef81889d9n%40googlegroups.com.

[JS G.]

Hello, 

With quay.io/ansible/awx-ee:latest ==> KO, i have a same problem

With quay.io/ansible/awx-ee:0.6.0 ==> It's OK, but image has one year ...

On my custom  EE i have same error ..., maybe I missed something in my EE build : 

---
version: 1

build_arg_defaults:
  EE_BASE_IMAGE: 'quay.io/ansible/ansible-runner:stable-2.9-latest'
  #EE_BASE_IMAGE: 'quay.io/ansible/ansible-runner:stable-2.12-latest'

dependencies:
  galaxy: requirements.yml
  python: requirements.txt
  system: bindep.txt

additional_build_steps:
  prepend: |
    RUN whoami
    RUN cat /etc/os-release
    RUN yum update -y
    RUN pip3 install --upgrade pip setuptools
    #RUN pip3 install --upgrade ansible  # /!\ A commenter si ansible 2.9
  append:
    - RUN echo This is a post-install command!
    - RUN alternatives --set python /usr/bin/python3
    - COPY --from=quay.io/project-receptor/receptor:1.0.0 /usr/bin/receptor /usr/bin/receptor
    - RUN mkdir -p /var/run/receptor
    - ADD run.sh /run.sh
    - USER 1000
    - RUN git lfs install

Regards;  

[JS G.]

Hello, 

More example contains  build_arg_defaults / EE_BASE_IMAGE

But other don't have this variable ... 

I'm going to try buil a nex EE without EE_BASE_IMAGE ..., but in this case, what is base images ?

Regards; 

[Michael Nelson]

The base images are here:

https://quay.io/repository/ansible/ansible-runner?tab=tags

You can take a look at this for guidance:

https://github.com/antuelle78/ansible-builder-awxee

Hope that helps.

Regards,

Antuelle78

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bc90d822-34df-427b-91a4-dec6803f45adn%40googlegroups.com.

[JS G.]

Hello,

I will make some test, but actually only awx-ee:0.6.0 is good ...
All other EE custom or not (awx-ee:latest for example) are not good ...

Regards,