action #36085
closed[sle][functional][u][hyperv] test fails in logs_from_installation_system - missed character in serial console
0%
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-x86_64-textmode@svirt-hyperv fails in
logs_from_installation_system
There is a mismatch in verification regexp received by serial console.
Expected regexp='SCRIPT_FINISHEDjDiaD-\d+-'
Received regexp='SCRIPT_FINISHEDDiaD-0-'
---> [2018-05-03T19:51:33.0399 CEST] [debug] <<< testapi::wait_serial(record_output=1, timeout=90, regexp='SCRIPT_FINISHEDjDiaD-\\d+-') <---
2018-05-03 15:47:34 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 umount: /mnt/dev: not mounted
--
2018-05-03 15:4:34 <2> dhcp89(3317) [Ruby] clients/umount_finish.rb:244 Umount failed, trying to remount read only...
2018-05-03 15:47:34 <0> dhcp89(3317) [agent-system] SystemAgent.cc(Execute):918 Execute (.bash_output)
2018-05-03 15:47:34 <0> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):31 shellcommand start
2018-05-03 15:47:34 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 mont: /mnt/dev not mounted or bad option
2018-05-03 15:47:34 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78
2018-05-03 15:47:34 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 In some cases useful info is found in syslog - try
2018-05-03 15:47:34 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 dmesg | tail or so.
2018-05-03 15:47:35 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 umount: /mnt/dev: not mounted
--
2018-05-03 15:47:39 <1> dhcp89(3317) [Ruby] clients/umount_finish.rb:284 loopdev: /sbin/losetup -d /dev/loop4
2018-05-03 15:47:39 <0> dhcp89(3317) [agent-system] SystemAgent.cc(Execute):918 Execute (.bash)
2018-05-03 15:47:39 <0> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):31 shellcommand start
2018-05-03 15:47:39 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 losetup: /dev/loop4: detach failed: No such device or address
--
2018-05-03 15:47:40 <1> dhcp89(3317) [Ruby] clients/umount_finish.rb:284 loopdev: /sbin/losetup -d /dev/loop0
2018-05-03 15:47:40 <0> dhcp89(3317) [agent-system] SystemAgent.cc(Execute):918 Execute (.bash)
2018-05-03 15:47:40 <0> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):31 shellcommand start
2018-05-03 15:47:40 <3> dhcp89(3317) [bash] ShellCommand.cc(shellcommand):78 losetup: /dev/loop0: detach failed: No such device or address
---> SCRIPT_FINISHEDDiaD-0- <---
---> [2018-05-03T19:56:04.0552 CEST] [debug] >>> testapi::wait_serial: SCRIPT_FINISHEDjDiaD-\d+-: fail <---
Reproducible¶
Fails since (at least) Build 0239 (current job)
Expected result¶
Last good: 0236 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by oorlov almost 6 years ago
- Related to action #28669: [sle][functional][u][svirt-hyperv-uefi] one character from serial output in wait_serial lost (was: /lib/libc.so.* did not match) added
Updated by oorlov almost 6 years ago
Same issue occurred again in logs_from_installation_system.
Expected regexp='SCRIPT_FINISHEDz8Xpn-\d+-'
Received regexp='SCRIPT_FINISHED8Xpn-0-'
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional][u] test fails in logs_from_installation_system - missed character in serial console to [sle][functional][u][hyperv] test fails in logs_from_installation_system - missed character in serial console
- Target version set to Milestone 18
First #28669 then this one
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-hyperv
https://openqa.suse.de/tests/1706867
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by okurz almost 6 years ago
- Due date set to 2018-07-03
- Status changed from New to Rejected
- Assignee set to okurz
- Target version changed from Milestone 18 to Milestone 17
After we have a new, more powerful and much more stable hyperv testing host I assume this ticket does not apply anymore, any new observations should be reported explicitly either by reopening or opening a new issue.