On running the reboot SSVM smoke test, the health check script fails to detect the mounted NFS stores post reboot. Increasing the wait time between reboot and running of the ssvm-check.sh helps ensure there is sufficient time for the SSVM to get configured.
With a 30s wait/ sleep - there have been intermittent failures with the test:
nosetests --with-xunit --xunit-file=results.xml --with-marvin --marvin-config=/marvin/ref-trl-1543-v-M7-pearl-dsilva-advanced-cfg -s -a tags=xx --hypervisor=vmware /marvin/tests/smoke/test_ssvm.py
==== Marvin Init Started ====
=== Marvin Parse Config Successful ===
=== Marvin Setting TestData Successful===
==== Log Folder Path: /marvin/MarvinLogs/Sep_09_2020_06_07_53_TJ2GQX. All logs will be available here ====
=== Marvin Init Logging Successful===
==== Marvin Init Successful ====
====Trying SSH Connection: Port:22 RetryCnt:60===
===SSH to Host port : 22 SUCCESSFUL===
{Cmd: ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no -oUserKnownHostsFile=/dev/null -p 3922 <SSVM_PRIVATE_IP> /usr/local/cloud/systemvm/ssvm-check.sh |grep -e ERROR -e WARNING -e FAIL via Host: <HOST_IP>} {returns: [u'ERROR: NFS is not currently mounted', u'Tests Complete. Look for ERROR or WARNING above.']}
=== TestName: test_07_reboot_ssvm | Status : FAILED ===
On increasing it to 90s:
[root@ref-trl-1543-v-M7-pearl-dsilva-marvin ~]# nosetests --with-xunit --xunit-file=results.xml --with-marvin --marvin-config=/marvin/ref-trl-1543-v-M7-pearl-dsilva-advanced-cfg -s -a tags=xx --hypervisor=vmware /marvin/tests/smoke/test_ssvm.py
==== Marvin Init Started ====
=== Marvin Parse Config Successful ===
=== Marvin Setting TestData Successful===
==== Log Folder Path: /marvin/MarvinLogs/Sep_09_2020_06_09_45_N33PNR. All logs will be available here ====
=== Marvin Init Logging Successful===
==== Marvin Init Successful ====
====Trying SSH Connection: Port:22 RetryCnt:60===
===SSH to Host port : 22 SUCCESSFUL===
{Cmd: ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no -oUserKnownHostsFile=/dev/null -p 3922 <SSVM_PRIVATE_IP> /usr/local/cloud/systemvm/ssvm-check.sh |grep -e ERROR -e WARNING -e FAIL via Host: <HOST_IP>} {returns: [u'Tests Complete. Look for ERROR or WARNING above.']}
====Trying SSH Connection: Port:22 RetryCnt:60===
====Trying SSH Connection: Port:22 RetryCnt:60===
===SSH to Host port : 22 SUCCESSFUL===
===SSH to Host port : 22 SUCCESSFUL===
{Cmd: ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no -oUserKnownHostsFile=/dev/null -p 3922 SSVM_PRIVATE_IP systemctl is-active cloud via Host: HOST_IP} {returns: [u'active']}
{Cmd: ssh -i /var/cloudstack/management/.ssh/id_rsa -ostricthostkeychecking=no -oUserKnownHostsFile=/dev/null -p 3922 SSVM_PRIVATE_IP systemctl is-active cloud via Host: HOST_IP} {returns: [u'active']}
====Trying SSH Connection: Port:22 RetryCnt:60===
====Trying SSH Connection: Port:22 RetryCnt:60===
====Trying SSH Connection: Port:22 RetryCnt:60===
===SSH to Host port : 22 SUCCESSFUL===
===SSH to Host port : 22 SUCCESSFUL===
===SSH to Host port : 22 SUCCESSFUL===
....
=== TestName: test_07_reboot_ssvm | Status : SUCCESS ===
===final results are now copied to: /marvin//MarvinLogs/test_ssvm_MRZ93U===
On running the reboot SSVM smoke test, the health check script fails to detect the mounted NFS stores post reboot. Increasing the wait time between reboot and running of the ssvm-check.sh helps ensure there is sufficient time for the SSVM to get configured.
With a 30s wait/ sleep - there have been intermittent failures with the test:
On increasing it to 90s: