whitespace breaks module name parsing in local_action

[rnowagk]

SUMMARY

Extra whitespace between a local_action module and the first argument is treated as part of the module name and leads to 'module not found' errors in 2.8.4. (It works in 2.7.0.)

ISSUE TYPE

• Bug Report

COMPONENT NAME

ansible-playbook

ANSIBLE VERSION

ansible 2.8.4
  config file = None
  configured module search path = [u'/home/centos/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Jun 20 2019, 20:27:34) [GCC 4.8.5 20150623 (Red Hat 4.8.5-36)]

CONFIGURATION

<nothing>

OS / ENVIRONMENT

CentOS Linux release 7.6.1810 (Core)

STEPS TO REPRODUCE

- hosts: localhost
  gather_facts: false

  tasks:
     - name: one space
       local_action: set_fact a="a"

     - name: more spaces
       local_action: set_fact     b="b"

EXPECTED RESULTS

all ok; as with 2.7.0:

...
PLAY RECAP *****************************************************************************************************************************************************
localhost                  : ok=3    changed=1    unreachable=0    failed=0

ACTUAL RESULTS

fails; note the whitespace after 'set_facts' in the error message

PLAY [localhost] ***********************************************************************************************************************************************

TASK [one space] ***********************************************************************************************************************************************
ok: [localhost -> localhost]

TASK [more spaces] *********************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "The module set_fact     was not found in configured module paths. Additionally, core modules are missing. If this is a checkout, run 'git pull --rebase' to correct this problem."}

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

[ansibot]

Files identified in the description:

• lib/ansible/playbook

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[sivel]

Likely caused by b72e989 although I haven't bisected.