running Cord 2.0 after shutdown

[labwna]

Hi,

after shutdown I' ve got always problems re-running the framework cord 2.0

I re-run the installation bash script (with -t or -c parameters), but I got errors on deployn tests or for example I' ve got problems of time out with MAAS, for example see below

1. How to rerun the framework after shutdown? Is it right to use the bash installation script?

2. Why time out problems with MAAS

Thank you

Joe

TASK [maas-provision : Wait for node to become ready] **************************

FAILED - RETRYING: TASK: maas-provision : Wait for node to become ready (40 retries left).

FAILED - RETRYING: TASK: maas-provision : Wait for node to become ready (39 retries left).

......

.....

FAILED - RETRYING: TASK: maas-provision : Wait for node to become ready (2 retries left).

FAILED - RETRYING: TASK: maas-provision : Wait for node to become ready (1 retries left).

fatal: [127.0.0.1]: FAILED! => {"attempts": 40, "changed": true, "cmd": "maas cord nodes list|jq -r '.[] | select(.status == 0).system_id'", "delta": "0:00:00.577659", "end": "2017-06-06 15:59:26.246428", "failed": true, "rc": 0, "start": "2017-06-06 15:59:25.668769", "stderr": "", "stdout": "", "stdout_lines": [], "warnings": []}

to retry, use: --limit @/cord/build/ansible/maas-provision.retry

PLAY RECAP *********************************************************************

127.0.0.1                  : ok=3    changed=2    unreachable=0    failed=1   

[Rajesh Challa]

Hello Joe,

Re-running the installation bash script (with -t parameter) would lead to MAAS-provisioning problem coz the compute-node is already provisioned. So, obviously, it can't be re-provisioned.

With -c parameter, you should not get this problem as it clears the previous installations.

To re-run cord-2.0, just doing vagrant up should work for you. Additionally, check out the following wiki link: https://wiki.opencord.org/pages/viewpage.action?pageId=2556321

with regards

Raj