If you have passwords that break the yaml format. i.e. beginning with ! or | etc, they need to be special handled. They can be entered into the credentials.yml deployment file surrounded by quotes. However, due to the way encrypted passwords are processed by MetroAE, this is not sufficient by
Have you seen this error? unable to open shell. Please see: https://docs.ansible.com/ansible /network_debug_troubleshooting.html#unable-to-open-shell We’ve written previously about a few ways to handle the situation when MetroÆ hits a problem connecting to the VSC using the Ansible sros_command and sros_config modules. The other topic focuses on making sure that you have the correct versions of
We recently saw a problem where a user was having trouble doing an install via ./metroae install_everything. The problem: metroae was completing without doing anything. In the output, every component type displayed a message like this: [WARNING]: Could not match supplied host pattern, ignoring: vstats PLAY [vstats] ****************************************************************** skipping: no hosts
We sometimes see an issue when running an install with MetroAE that results in the following error: 2018-10-27 15:42:48,890 p=17607 u=root | fatal: [vsc2.mgmt.vnspoc.net -> localhost]: FAILED! => { “changed”: false, “failed”: true, “msg”: “unable to open shell. Please see:https://docs.ansible.com/ansible/network_debug_troubleshooting.html#unable-to-open-shell” } If you follow the URL provided in the
