QA » openQA Project » openQA Tests

pull request sent out now

While I really like the test and it mostly works (75% of the problems we've seen are due to changes in SLE12 SP2 that are NOTHING to do with the test) we've still had to remove the yast2_nis test from main.pm for the following reasons

• it only works on the suse.de network - no one can test anything in Prague or Bejing with it present
• it's reliant on nis.suse.de - this prevents the test being used by openSUSE, which is always a goal if it can be done
• while it is important, it gets in the way of staging. It probably warrants either it's own scenario, or we're going to have to start implementing something like the extra_tests_ scenarios which openSUSE uses for stuff like this

Zaoliang, please make the following changes

• Please make it so this test does not rely on nis.suse.de.
• This might mean making two tests, one to setup a NIS/NFS server, and then connecting the NIS client to it using an improved version of yast2_nis.pm
• I'd accept localhost testing, but this might be an excuse to experiment with openQA's multi-machine testing - Denis is our expect.

This will make the test more flexible in where we put it and how we put it..once we get there I'll hopefully have made a decision about how we put it back in the sle main.pm :)

Thanks

HI Josef, please take over and help on this test case, thanks!

YaST nis code is pretty old, bugs below are blocking progress in openQA test
Existing openQA test https://openqa.suse.de/tests/627400

https://bugzilla.suse.com/show_bug.cgi?id=998965
https://bugzilla.suse.com/show_bug.cgi?id=999873
https://bugzilla.suse.com/show_bug.cgi?id=1005248
https://bugzilla.suse.com/show_bug.cgi?id=1007033

Hi @dzedro, zluo now put the yast2_nis module in use, see #13252 for details. It is only used in SLE so it would be great if in this ticket we can focus on openSUSE.

I just checked all bugs you mentioned. There are all in state NEW and I don't see that any immediate action is necessary by you so I guess we are blocked here by others. Setting to feedback to resemble the blocked state, I hope you don't mind

Green NIS test in openQA is misleading, there are few bugs, the part is not present in existing test
No idea in what state is NIS in openSUSE

Changes in TW broke NIS. So there is a real need for this test!

"in progress" as in: can be worked on

Adding the target version: "future" as I would like to schedule this better with the QA SLE Functional team.

PO+SM want to have it :) Let's try to make it workable then

SR: Please give us another chance for the next sprint :)

mass-shift of tickets to next sprint due to training on sprint review day

SLE15 currently blocked by https://bugzilla.suse.com/show_bug.cgi?id=1073281 and then #23822

https://openqa.suse.de/tests/1408217#step/nis_client/43 shows the client for SLE 12 SP4 and it actually checks nicely the expectations, e.g. exported home directory over NFS from test user on NIS.

I will try to harmonize the test plan regarding the test modules "nis_server" and "nis_client". "yast2_nis" relies on nis.suse.de, not much we can do here. The challenge though is that currently there are no multi-machine capable workers in the o3 infrastructure. I see the following options:

1. openvswitch+multi-machine o3 workers
2. rewrite tests be one-host only

I asked in #opensuse-factory what we can do about opt. 1.

@asmorodskyi is working on the subticket to have multi-machine workers in o3 infrastructure. Let's give him some time and review later.

Commented in the blocking ticket but I don't see this happening now so -> M18

if we continue like this in #30892 this will never happen

Move to new QSF-y PO after I moved to the "tools"-team. I mainly checked the subject line so in individual instances you might not agree to take it over completely into QSF-y. Feel free to reassign to me or someone else in this case. Thanks.

#30892 fixed, multi-machine tests are possible on o3

Targeting remote ssh installation first.

Blocked by https://bugzilla.suse.com/show_bug.cgi?id=1149011

Bug is fixed.

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9646. This works, but, ticket is blocked because of https://progress.opensuse.org/issues/64195

The other issue is hopefully fixed for good.

Now, I found this problem, posted on yast's IRC:
Hello, I am testing yast nis_server module on TW, and I see that there are different files mapped in TW and in sle, see TW: http://waaa-amazing.suse.cz/tests/11777#step/nis_server/48 vs SLE http://waaa-amazing.suse.cz/tests/11773#step/nis_server/51. Does somebody here know why is that so ?

And another: we have a problem in our test, if we compare the screenshot vs the needle here we see that the needle matches, but not all mapped files are selected. So that's a false positive that stays un-detected. Maybe we can address this in a different ticket.

EDIT: for the latter, actually if we check the video, it's working as expected. So that's just that the needle matches too early at 98%.

Investigating the issue.

PR merged, test enabled in TW development group. Discussed with Leap PO, we agreed that in today's context it did not make much sense to test it on Leap. Putting it on feedback until we see if it all works fine.

Test passed in TW and SLE.