ERROR! Invalid callback for stdout specified: awx_display on MacOS M3

[Pieter-Visscher]

ISSUE TYPE

• Bug Report

SUMMARY

When running ansible-navigator on Macbook M3 I get the error ERROR! Invalid callback for stdout specified: awx_display.
Exact configuration shows no issues on Linux machines.

This issue has persisted across different execution environments: custombuild, awx, ansible, rhel.

ANSIBLE-NAVIGATOR VERSION

ansible-builder           3.1.0
ansible-compat            24.10.0
ansible-core              2.18.1
ansible-lint              24.10.0
ansible-navigator         24.10.0
ansible-runner            2.4.0

CONFIGURATION

ansible-navigator:

  ansible:
    config:
      path: ansible.cfg
    inventory:
      help: true
      entries:
        - inventory
    playbook:
      path: ansibletest.yml

  ansible-runner:
    artifact-dir: ./runner

  app: run

  execution-environment:
    container-engine: docker
    environment-variables:
      set:
        SATELLITE_PASSWORD:       'sample'
        SATELLITE_SERVER_URL:     'sample'
        SATELLITE_USERNAME:       'sample'
        SATELLITE_VALIDATE_CERTS: 'no'
        enabled: true
    image: my-custom-ee:latest
    pull:
      policy: missing
    container-options:
      - "--user=root"

  mode: stdout

  playbook-artifact:
    enable: false

LOG FILE

ansible-navigator.log

STEPS TO REPRODUCE

This appears to be a macOS specific issue. As ansible-navigator executed in linux VMs has shown no problems.
install python via homebrew
configure venv.
use pip3 to install ansible-navigator
run a playbook via the above mentioned settings.
In this playbook there is no inventory specified as its executed on localhost to fetch info of the running execution environment.

EXPECTED RESULTS

execution of ansible playbook in execution environments

ACTUAL RESULTS

I get the following error:
ERROR! Invalid callback for stdout specified: awx_display

ADDITIONAL INFORMATION

Running the same playbook with the same execution environment with ansible-runner directly works. So the issue appears to be ansible-navigator specific.