QA » openQA Project » openQA Tests

In case you want to add to TW, in O3 I still cannot see any single run passing of remote_ssh_target https://openqa.opensuse.org/tests/1095178#next_previous. I could not find the problem there a time ago, and I don't remember other MM job there working. Perhaps in local passes, I don't have the setup. No problem with MM in O3, just and ssh problem not related.

Did you find any trouble with isos post to trigger the runs? If so, we can merge the schedules first, but we need to edit the PR info and remove [WIP] first.

For now, I'm working on the workarounds for TW. there are two situations that probably need to be reported, but may be related to some other workarounds : unable to mount the nfs enties which looks related to the other workaround, but the message in the logs seem to indicate it's not:

2019-11-26 09:29:58 <3> susetest(2582) [bash] ShellCommand.cc(shellcommand):78 Failed to get unit file state for nfs.service: No such file or directory
2019-11-26 09:29:58 <0> susetest(2582) [bash] ShellCommand.cc(shellcommand):199 shellcommand end
2019-11-26 09:29:58 <3> susetest(2582) [Ruby] modules/Nfs.rb:394 Unable to mount the NFS entries from /etc/fstab.

So I need to do some manual testing to figure it out.
There is also some exportfs error that I want to check

Does it work smooth for SLE-15-SP2 in 64bit? To fix it in O3 or add more archs I would say is the extended part, which is fine to do in this ticket, but at least to ensure to have one done for the end of the sprint.

JERiveraMoya wrote:

Does it work smooth for SLE-15-SP2 in 64bit? To fix it in O3

It does, but I am almost done with the "extended part", so I think it's better to work a couple of hours more on this and have it working everywhere rather than create a follow-up ticket and start again from scratch in six months

bug reported : Unable to mount the NFS entries from /etc/fstab: no nfs.service file and another one found: http://waaa-amazing.suse.cz/tests/10336#step/yast2_nfs4_client/111

Reported this bug https://bugzilla.opensuse.org/show_bug.cgi?id=1157915 regarding this failure http://waaa-amazing.suse.cz/tests/10336#step/yast2_nfs4_client/111. Not sure this will require a workaround, it looks like a kernel bug

So, several bugs reported for TW. The workaround I implemented for one of them will also fix the test in yast2_ncurses test suite. Regarding MM testing on other arches, works for ppc64le, but not yet for aarch64 and s390x, I did not really investigate why. I'd propose to enable it first for ppc64le and x86_64, as we know it works here, then see if we can have it working everywhere.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8991 is merged, but there are some issues with aarch64 and s390x. I disabled for s390x, and submitted this new PR for aarch64: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9075. I might as well disable it for arm, as it seems to not work great either: last VR ended as incomplete in the middle of execution, there's no clue what happened.