action #18974
closed
[functional][sles] Console login on ppc64le does not work with VIRTIO_CONSOLE=1
Added by nicksinger almost 7 years ago.
Updated almost 7 years ago.
Category:
Bugs in existing tests
Description
Observation¶
All acceptance tests on ppc64le break, if the test uses the virtio_console.
Take a look at these failures for reference:
https://openqa.suse.de/tests/918610#step/acceptance_fs_stress/5
https://openqa.suse.de/tests/918611#step/acceptance_process_stress/5
https://openqa.suse.de/tests/918615#step/acceptance_sched_stress/5
Some more information on this issue was provided on #qa-review:
13:29:54 rpalethorpe | nsinger: they are probably trying to use virtio_console which isn't working, probably because agetty is not being started on the serial device on ppc64le. It should work, but it is not for some reason. I could set VIRTIO_CONSOLE back to zero if necessary
13:35:24 nsinger | rpalethorpe: i'm not really sure what happens there. It uses the login function from lib/serial_terminal.pm . So if you changed VIRTIO_CONSOLE it seems to not work then :D
13:36:52 rpalethorpe | nsinger: I will disable it, I don't think that I will be able to fix any time soon
13:37:39 rpalethorpe | I have removed it so if the tests are rescheduled it should be OK now, unless there are other problems still
13:38:14 nsinger | rpalethorpe: okay then. I'll open a bug in poo and restart the tests to see if it works again
Reproducible¶
Take a look at the links above. The issue is easy to reproduce as soon as you change VIRTIO_CONSOLE from 0 to 1.
Expected result¶
Tests are able to login over the console
Thank you @nicksinger for debugging this issue. I'm adding VIRTIO_CONSOLE=0 to those three acceptance test to workaround it.
Since those acceptance tests are important and they're for testing product, not for testing openQA stability.
I suggest until virtio console feature more stable, then we can remove this setting "VIRTIO_CONSOLE=0".
Hi @yosun, because you changed settings and are now working on that ticket can you please assign the ticket to yourself and set the status to "In Progress" accordingly?
- Status changed from New to In Progress
- Assignee set to nicksinger
@yosun - you're welcome. Unfortunately just rerunning the job over the webui does not work because openQA then copies over the values from the previous test (hence VIRTIO_CONSOLE stays 1 because it gets copied from the old testsuite).
With this command, one can easily rerun certain testsuites:
openqa-client --host https://openqa.suse.de isos post BUILD=0367 BUILD_SLE=0367 ISO=SLE-12-SP3-Server-DVD-ppc64le-Build0367-Media1.iso _NOOBSOLETEBUILD=1 TEST=sles12_qa_acceptance_fs_stress,sles12_qa_acceptance_process_stress,sles12_qa_acceptance_sched_stress ARCH=ppc64le BUILD_SDK=0187 DISTRI=sle FLAVOR=Server-DVD VERSION=12-SP3 SCC_REGCODE=72d93c8cb967614a SCC_URL=http://Server-0367.proxy.scc.suse.de
(adjust variables as needed and thanks @okurz for showing me this)
I already did this so lets wait what
https://openqa.suse.de/tests/922916,
https://openqa.suse.de/tests/922917 and
https://openqa.suse.de/tests/922918
result in. But in the live view I can already see how openQA is able to login again. So changing back to VIRTIO_CONSOLE=0 fixes this issue as expected.
I still wait until all runs finish successful and close the ticket then.
- Status changed from In Progress to Resolved
- Related to action #18970: [sle][functional]test fails in acceptance_fs_stress added
Also available in: Atom
PDF