action #97517
closed
[virtualization][3rd party hypervisor][vmware] Executing command returns 'undef' value with assert_script_run after vm reboot
Added by nanzhang over 2 years ago.
Updated over 2 years ago.
Category:
Regressions/Crashes
Files
- Project changed from openQA Infrastructure to openQA Project
- Due date set to 2021-09-09
- Category set to Regressions/Crashes
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
- Description updated (diff)
Thank you Oliver for looking into this issue. I've updated the description as per the ticket template for defects.
Another finding is that the issue only happened on shutdown VM completely then booting up. VM reboot operation will not cause this issue, and it was verified in my local openqa. After rebooting VM, the token "LHroM" can be normally received from ttyS0 - http://10.67.129.66/tests/240#step/esxi_open_vm_tools/53
- Status changed from Feedback to New
- Subject changed from [virtualization][3rd party hypervisor] Executing command returns 'undef' value with assert_script_run after vm reboot to [virtualization][3rd party hypervisor][vmware] Executing command returns 'undef' value with assert_script_run after vm reboot
- Due date deleted (
2021-09-09)
- Assignee deleted (
okurz)
- Priority changed from Normal to Low
- Target version changed from Ready to future
I see. So the impact seems to be limited to the vmware backend. Good that you could reproduce it on another vmware host. Within the QE Tools team I doubt we won't be able to help more. You are on your own, sorry.
Actually, we have two cases which needs to shutdown VM during test running, and currently this issue blocked automation tests.
- Status changed from New to Resolved
I've found a solution. After shutting down and booting up VM, it is required to re-setup the serial channel to the VM before switch to SUT console.
Just adding the following line in my test code.
console('svirt')->start_serial_grab;
Also available in: Atom
PDF