Skip links

Tag: shell

vsc_health: Get output of ‘show version’ failed: unable to open shell

We recently saw a user encounter this error when running vsc_health prior to upgrading an existing installation of VSP: unable to open shell. Please see: https://docs.ansible.com/ansible /network_debug_troubleshooting.html#unable-to-open-shell There are several other Forum topics on this error. For example: https://devops.nuagenetworks.net/forums/topic/unable-to-open-shell-error-take-2/. But this case was a bit different. This case was caused by

Unable to open shell error: take 2

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

Unable to open shell error

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

Bitnami