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
A common problem we hear from the field is an error when MetroAE attempts to execute a yum update on the VSDs. This takes place during the vsd-deploy phase and results in this error text: This problem is going to prevent you from moving forward
We recently saw a user experiencing an error running the MetroAE setup script: # ./metro-setup.sh Setting up Nuage Metro Automation Engine Checking user privileges… [ OK ] Checking OS type… [ OK ] Checking OS version… [ OK ] Installing epel-release… [ OK ] Installing
With the introduction of Croxley, MetroÆ supports a new, schema-validated method of user input. The implementatino is such that now each section of the old build_vars.yml file now has its own file: vsds.yml vscs.yml common.yml and so on As an aid to hep you convert
