Feature test issue: 97-Migrate-VM-On-Reboot failed because of command "openstack server show 97centos" rc=0

[Alexandru Dimofte]

Brief Description
-----------------
Executing feature tests, I discovered this test: 97-Migrate-VM-On-Reboot.robot which is failing.
20200717 14:42:38.791 - INFO - Executing command 'export OS_CLOUD=openstack_helm && openstack server show 97centos|grep -w status|awk '{print$4}''.
20200717 14:42:41.197 - INFO - Command exited with return code 0.
20200717 14:42:41.197 - INFO - ${stdout} = ERROR
20200717 14:42:41.197 - INFO - ${stderr} =
20200717 14:42:41.197 - INFO - ${rc} = 0

Severity
--------
<Minor: System/Feature is usable with minor issue>

Steps to Reproduce
------------------
Run the above mentioned test or execute the command: export OS_CLOUD=openstack_helm && openstack server show 97centos|grep -w status|awk '{print$4}'
or
export OS_CLOUD=openstack_helm && openstack server list | grep 97centos

Expected Behavior
------------------
Server 97centos should be available.

Actual Behavior
----------------
Command "export OS_CLOUD=openstack_helm && openstack server show 97centos|grep -w status|awk '{print$4}'" returns nothing.

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Tested on Standard configuration (config 3)

Branch/Pull Time/Commit
-----------------------
I observed this on 3 builds from master branch, layered. ex:
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/flock/20200718T013422Z/

Last Pass
---------
Not known.

Timestamp/Logs
--------------
Will be attached.

Test Activity
-------------
Feature Testing: 97-Migrate-VM-On-Reboot.robot

Workaround
----------
NA

[yong hu (yhu6)]

VM migration is important, so @Zhipeng please help address this LP.

[zhipeng liu (zhipengs)]

Hi Alex,

From below time in your debug log, I did not see VM created successfully.
So not yet reach the test step of reboot.

20200717 14:41:05.131 - INFO - Executing command 'export OS_CLOUD=openstack_helm && openstack server create --image 97centos-image --flavor 97centos-flavor --nic net-id=fd5f296e-9a2c-4995-b437-1a178a32f336 97centos'.
20200717 14:41:10.510 - INFO - Command exited with return code 0.

Please provide complete logs under /var/log like other ticket next time.
Thanks!

Zhipeng

Zhipeng

[Alexandru Dimofte (adimofte)]

Hi Zhipeng,

I have all logs from /var/log . Just let me know which of them you need. I attached the sysinv.log file now.

Best regards,
Alex

[zhipeng liu (zhipengs)]

The key point is the VM has not been created.
This case is testing VM evacuation during reboot right?
Is there any special for VM creation in this case?

[Alexandru Dimofte (adimofte)]

Well I am not an expert on this but I can tell that manually I succeeded to run the command:
"export OS_CLOUD=openstack_helm && openstack server create --image 97centos-image --flavor 97centos-flavor --nic net-id=fd5f296e-9a2c-4995-b437-1a178a32f336 97centos"
but only after sudo authentication.
The result is:
controller-0:/home/sysadmin# export OS_CLOUD=openstack_helm && openstack server list
+--------------------------------------+----------+--------+----------+----------------+-----------------+
| ID | Name | Status | Networks | Image | Flavor |
+--------------------------------------+----------+--------+----------+----------------+-----------------+
| c5a1614e-5590-46b3-9988-11884aa93487 | 97centos | ERROR | | 97centos-image | 97centos-flavor |
+--------------------------------------+----------+--------+----------+----------------+-----------------+
controller-0:/home/sysadmin#

I suspect some authentication issues or some authentication token issues... This is all I have...

[Ghada Khalil (gkhalil)]

Marking as stx.4.0 for now until further investigation/discussion between the distro.openstack team and the reporter. This was seen in regression.

[zhipeng liu (zhipengs)]

Hi Alex,

Please provide all logs with nova prefix
under /var/log/containers/
You can also double check why VM creation failure took place in your side.

Thanks!
Zhipeng

[Alexandru Dimofte (adimofte)]

I executed this test manually and it passed. So the issue is from the test.
cmd used:
export OS_CLOUD=openstack_helm && openstack image create --file /home/sysadmin//CentOS-7-x86_64-GenericCloud.qcow2 --disk-format qcow2 --public 97centos-image
export OS_CLOUD=openstack_helm && openstack flavor create --ram 2048 --disk 20 --vcpus 1 --public --id auto 97centos-flavor
export OS_CLOUD=openstack_helm && openstack server create --image 97centos-image --flavor 97centos-flavor --nic net-id=53c63ac7-ed89-42ce-b3a1-0536bd1195e8 97centos
openstack server show 97centos
Then I reboot the compute-1
openstack server show 97centos and it migrated to compute-0 after a period of time.

Conclusion: This defect can be closed.