ansible-navigator run playbook.yml fails with error ansible-playbook: error: unrecognized arguments: podman about ansible-navigator HOT 6 CLOSED

Hello
following your comments, i've tested changing the cmdline to --forks 15 and now it works with no additional arguments
emptying the cmdline breaks the run with the following error
In ansible-navigator.ansible.cmdline: none is not of type string
commenting the cmdline also enables it to works with no additional arguments
Thanks a lot for your help

from ansible-navigator.

cmdargs option is intended to contain not navigator own argument but the underlying called process arguments (ansible-playbook in this case.

We will keep this bug open in order to update the documentation to be more specific.

from ansible-navigator.

From what i've tested, if i don't put another flag after the ansible-navigator run playbook.yml, it will fail to run with the error listed
if i add either -v or -check, the playbook executes correctly
so there seems to be a bug when the run doesn't have any arguments added that it tries to send the -ce podman as an argument to ansible-playbook which is not recognized

from ansible-navigator.

Hey @nuclear12 , In your given configuration file cmdline argument is declared as cmdline: -ce podman which might be causing this error.

The cmdline option is used for passing extra parameter to the corresponding command.
For example:

---
ansible-navigator:
  ansible:
    cmdline: "--forks 15"

To specify container engine as podman, simply this should work:

ansible-navigator:
  execution-environment:
    container-engine: podman

from ansible-navigator.

Try using --ce podman, which is the parameter for navigator at the command line. When navigator doesn't recognize a flag it will pass it to the underlying command.

(that said, we should figure out why we aren't passing it to playbook when -v is used)

from ansible-navigator.

Oh.....

Here's the explanation.

If you have cmdline used in your setting file and don't provide any unrecognized parameters at the command line, the settings file entry will be used and passed to ansible-playbook

If you have cmdline used in your setting file and do provide some unrecognized paramater at the command line (e.g.-v) that will get passed to ansible-playbook instead of what is in the settings file.

This is a result of how navigator handles setting precedence: https://ansible.readthedocs.io/projects/navigator/faq/#what-is-the-order-in-which-configuration-settings-are-applied

from ansible-navigator.