action #40715
closed[hyperv] Hyper-V 2012 R2 serial console unstable
0%
Description
We were bothered by this for a long time and it's still present: Hyper-V 2012 R2 serial console leaks data, usually it's the 16th character on a line.
In https://openqa.suse.de/tests/2030033#step/rsync/17 openQA expected SCRIPT_FINISHEDEcM1i but got SCRIPT_FINISHEDcM1i, note the missing E, a 16th character. This is a Hyper-V product issue and I don't know what we can do about it apart from trimming our magic strings to be shorter than 16 characters. I did this when Hyper-V 2012 R2 was our primary platform, but it is not anymore and Hyper-V 2016 has it fixed. This should not affect openQA groups outside of "Virtualisation".
This ticket mostly serves as a "wailing wall" for the purpose of openQA reviews and I expect it to be kept for the time we support Hyper-V 2012 R2.
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_offline_sle12sp3_minimalupdate_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2091972
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_offline_sle12sp3_minimalupdate_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2132852
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: migration_offline_sle12sp3_minimalupdate_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2217234
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: om_proxyscc_sles12sp3_full_update_by_zypper_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2246700
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: om_proxyscc_sles12sp3_full_update_by_zypper_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2246700
Updated by okurz about 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: media_upgrade_sles12sp4_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2320019
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: textmode@svirt-hyperv2012r2
https://openqa.suse.de/tests/2442046
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: media_upgrade_sles15_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2508301
Updated by okurz almost 6 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: proxyscc_upgrade_sles12sp4_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2549909
Updated by xlai almost 6 years ago
okurz wrote:
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: proxyscc_upgrade_sles12sp4_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2549909
@michalnowak, About this failure test, proxyscc_upgrade_sles12sp4_hyperv@svirt-hyperv2012r2, is this one the case that from automation we can do nothing to avoid the length limit on serial console?
Updated by xlai almost 6 years ago
okurz wrote:
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: media_upgrade_sles15_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2508301
What about this then?
Updated by michalnowak almost 6 years ago
@xlai: Both of them are the "unstable serial console on Hyper-V 2012 R2" problem.
It's easy to miss it but have a look the first one: "release-notes-sles" is expected, but "release-notes-ses" was received, l - the 16th character - is missing. For the latter one: "SCRIPT_FINISHED708tO-0-" is expected, but "SCRIPT_FINISHED08tO-0-" received, 7 - the 16th character - is missing.
What we can do is to trim magic codes to under 16 characters, but approach gets problematic for wait_serial() matched as they are expected to be longer than 16 characters. In such cases I plan to remove the test module from Hyper-V 2012 R2 runs.
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: proxyscc_upgrade_sles15_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2804721
Updated by okurz over 5 years ago
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: media_upgrade_sles15_hyperv@svirt-hyperv2012r2
https://openqa.suse.de/tests/2866160
Updated by michalnowak over 5 years ago
- Status changed from New to Blocked
- Assignee deleted (
michalnowak) - Difficulty set to hard
With current design of openQA which relies on serial console to be 100% stable, I - nor anyone else besides Microsoft - can do much in here. It's fixed from Hyper-V 2016 on, so just be patient and wait for 10/10/2023 (https://support.microsoft.com/en-us/lifecycle/search/1163).
Updated by okurz over 3 years ago
- Priority changed from Normal to Low
This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".
Updated by okurz almost 3 years ago
- Related to action #97745: [virtualization][hyperv] ensure_serialdev_permissions fails for hyperv added
Updated by rcai almost 2 years ago
Not find the same issue: the lack of character for wait_serial recently.