removed old localhost content (#51839)

pull/51521/head
Sandra McCann 6 years ago committed by Alicia Cozine
parent 0f0d33a954
commit d92797f594

@ -33,8 +33,6 @@ Errors generally fall into one of the following categories:
* May actually be masking a authentication issue * May actually be masking a authentication issue
:Playbook issues: :Playbook issues:
* Use of ``delegate_to``, instead of ``ProxyCommand``. See :ref:`network proxy guide <network_delegate_to_vs_ProxyCommand>` for more information. * Use of ``delegate_to``, instead of ``ProxyCommand``. See :ref:`network proxy guide <network_delegate_to_vs_ProxyCommand>` for more information.
* Not using ``connection: local``
.. warning:: ``unable to open shell`` .. warning:: ``unable to open shell``
@ -569,31 +567,6 @@ Playbook issues
This section details issues are caused by issues with the Playbook itself. This section details issues are caused by issues with the Playbook itself.
Error: "invalid connection specified, expected connection=local, got ssh"
-------------------------------------------------------------------------
**Platforms:** Any
Network modules require that the connection is set to ``local``. Any other
connection setting will cause the playbook to fail. Ansible will now detect
this condition and return an error message:
.. code-block:: console
fatal: [nxos01]: FAILED! => {
"changed": false,
"failed": true,
"msg": "invalid connection specified, expected connection=local, got ssh"
}
To fix this issue, set the connection value to ``local`` using one of the
following methods:
* Set the play to use ``connection: local``
* Set the task to use ``connection: local``
* Run ansible-playbook using the ``-c local`` setting
Error: "Unable to enter configuration mode" Error: "Unable to enter configuration mode"
------------------------------------------- -------------------------------------------

Loading…
Cancel
Save