action #9900
closed[sle][functional][hard][opensuse][y] nis+autofs
0%
Description
Motivation¶
our biggest "customer" uses nis+autofs, so we should have a test for that :)
Acceptance criteria¶
- AC1: We have a NIS server+client test in openSUSE TW
- AC2: Same as AC1 but for openSUSE Leap 15.2
- AC3: Test suites are enabled in development job group first and then moved to the main job group
- AC4: Same as AC1 but for SLE 15 DONE: https://openqa.suse.de/tests/1404255
- AC5: Same as AC1 but for SLE 12 SP4 DONE: https://openqa.suse.de/tests/1408217#step/nis_client/43
Tasks¶
- Crosscheck existing NIS tests against manual expectations
- If necessary add new tests / extend existing tests
- Ensure the supported testsuites are called in all products+versions mentioned above
SLE 15 tests can be used as a base:
https://openqa.suse.de/tests/latest?arch=x86_64&version=15-SP1&machine=64bit&test=nis_server&flavor=Installer-DVD&distri=sle
https://openqa.suse.de/tests/latest?flavor=Installer-DVD&distri=sle&test=nis_client&machine=64bit&version=15-SP1&arch=x86_64
Related:
Updated by RBrownSUSE almost 9 years ago
- Checklist item changed from to [ ] SLE, [ ] Leap, [ ] TW
Updated by RBrownSUSE almost 9 years ago
- % Done changed from 100 to 80
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
Updated by zluo over 8 years ago
No not yet. I need to learn about support server which provides nis server functionality.
Updated by zluo over 8 years ago
- Assignee changed from zluo to dzedro
HI Josef, please take over and help on this test case, thanks!
Updated by dzedro about 8 years ago
- Status changed from New to In Progress
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
Updated by okurz about 8 years ago
- Related to action #13252: enable yast2_nis test added
Updated by okurz about 8 years ago
- Status changed from In Progress to Feedback
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
Updated by dzedro about 8 years ago
I don't mind, I will update my existing (green) test with at least one bug to make it fail, maybe somebody will start to push this.
Updated by okurz about 8 years ago
huh? why do you want to make the tests fail? If the bugs are not being worked on you should not make tests fail, rather pass nevertheless e.g. with a softfail. What I see as necessary though is adding a corresponding openSUSE version for tests.
Updated by dzedro about 8 years ago
I can't make something not working just soft fail, but I will try.
Updated by okurz almost 8 years ago
I also checked the bugs
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
Not any useful progress at all.
But: @dzedro: I could not find a recent job example. Possibly because we are restructuring the "extra tests" to be more aligned with the structure on o3. When you say the test is "blocked": Is NIS unusable? If this is the case I think we would need to escalate. If NIS works but the test has different assumptions then it would need to be adjusted to reflect reality. How feasible would this be?
Updated by okurz almost 8 years ago
two scenarios now included in Functional: Server on osd: nis_client, nis_server
The four mentioned bugs are still open.
Can we cross SLE of the list?
what about openSUSE?
Updated by dzedro over 7 years ago
- Assignee deleted (
dzedro)
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
Updated by okurz over 7 years ago
- Subject changed from nis+autofs to [sle][functional][opensuse]nis+autofs
Updated by lnussel about 7 years ago
- Due date set to 2017-11-30
Changes in TW broke NIS. So there is a real need for this test!
Updated by okurz about 7 years ago
- Status changed from Feedback to In Progress
"in progress" as in: can be worked on
Updated by sebchlad about 7 years ago
- Target version set to future
Adding the target version: "future" as I would like to schedule this better with the QA SLE Functional team.
Updated by okurz about 7 years ago
- Target version changed from future to Milestone 12
PO+SM want to have it :) Let's try to make it workable then
Updated by okurz about 7 years ago
- Due date changed from 2017-11-30 to 2017-12-19
SR: Please give us another chance for the next sprint :)
Updated by okurz about 7 years ago
- Due date changed from 2017-12-19 to 2018-01-17
Updated by okurz almost 7 years ago
- Due date changed from 2018-01-17 to 2018-01-30
- Target version changed from Milestone 12 to Milestone 13
mass-shift of tickets to next sprint due to training on sprint review day
Updated by okurz almost 7 years ago
- Subject changed from [sle][functional][opensuse]nis+autofs to [sle][functional][hard][opensuse]nis+autofs
- Description updated (diff)
- Assignee changed from sebchlad to okurz
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:
- openvswitch+multi-machine o3 workers
- rewrite tests be one-host only
I asked in #opensuse-factory what we can do about opt. 1.
Updated by okurz almost 7 years ago
- Blocked by action #30892: [opensuse][tools]multi-machine worker setup added
Updated by okurz almost 7 years ago
- Due date changed from 2018-01-30 to 2018-02-27
- Status changed from In Progress to Blocked
- Target version changed from Milestone 13 to Milestone 14
Updated by okurz almost 7 years ago
- Due date deleted (
2018-02-27) - Target version changed from Milestone 14 to Milestone 15
@asmorodskyi is working on the subticket to have multi-machine workers in o3 infrastructure. Let's give him some time and review later.
Updated by okurz over 6 years ago
- Subject changed from [sle][functional][hard][opensuse]nis+autofs to [sle][functional][hard][opensuse][y] nis+autofs
- Target version changed from Milestone 15 to Milestone 18
Commented in the blocking ticket but I don't see this happening now so -> M18
Updated by okurz over 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by okurz over 6 years ago
- Target version changed from Milestone 18 to future
if we continue like this in #30892 this will never happen
Updated by okurz over 5 years ago
- Assignee changed from okurz to riafarov
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.
Updated by okurz over 5 years ago
- Status changed from Blocked to Workable
#30892 fixed, multi-machine tests are possible on o3
Updated by riafarov over 5 years ago
- Checklist item changed from [ ] SLE, [ ] Leap, [ ] TW to [x] SLE, [ ] Leap, [ ] TW
- Description updated (diff)
- Due date set to 2019-08-13
- Assignee deleted (
riafarov)
Updated by riafarov over 5 years ago
We need to adapt network configuration part, as SLE images use wicked and openSUSE has network manager.
Updated by riafarov over 5 years ago
- Due date changed from 2019-08-13 to 2019-08-27
Targeting remote ssh installation first.
Updated by riafarov over 5 years ago
- Due date changed from 2019-08-27 to 2019-09-10
Updated by lnussel over 5 years ago
openSUSE Server installations also use wicked, use that one for the server part.
Updated by riafarov over 5 years ago
- Due date changed from 2019-09-10 to 2019-09-24
Updated by riafarov over 5 years ago
- Due date changed from 2019-09-24 to 2019-10-22
- Status changed from Workable to Blocked
- Assignee set to riafarov
Updated by riafarov about 5 years ago
- Due date changed from 2019-10-22 to 2019-12-03
Updated by riafarov about 5 years ago
- Due date changed from 2019-12-03 to 2020-01-14
Updated by riafarov almost 5 years ago
- Due date changed from 2020-01-14 to 2020-02-25
- Status changed from Blocked to New
- Assignee deleted (
riafarov)
Bug is fixed.
Updated by JERiveraMoya almost 5 years ago
- Due date changed from 2020-02-25 to 2020-03-10
- Status changed from Workable to In Progress
Updated by JRivrain almost 5 years ago
I haven't really been working on this, as I worked on some bug reports. What I see so far is I have to rewrite parts of the test to work in opensuse, as opensuse desktop is using NetworkManager. So there are 2 options:
1 - rewrite the network part to work also with NM
2 - use a textmode image as it uses wicked also on opensuse, when not desktop. but then, it also needs a bit of rewrite, as the test is made for desktop
Updated by JERiveraMoya almost 5 years ago
- Due date changed from 2020-03-10 to 2020-03-24
Updated by JRivrain almost 5 years ago
- Status changed from In Progress to Blocked
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
Updated by JRivrain almost 5 years ago
- Status changed from Blocked to In Progress
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%.
Updated by JRivrain almost 5 years ago
Apparently, the difference between files is due to https://github.com/yast/yast-nis-server/blob/ed65ef561f14a16705e2ce2e5fd4cee5c8c9dc37/src/include/nis_server/maps.rb#L88, so it's normal. But then how to expect how many of them we should select ?
Updated by riafarov almost 5 years ago
- Due date changed from 2020-03-24 to 2020-04-07
Investigating the issue.
Updated by JRivrain almost 5 years ago
I reported that bug: https://bugzilla.suse.com/show_bug.cgi?id=1167589. basically the test does not work in TW. We could work around this, but I also found another problem: the already existing workarounds are outdated, we have one soft-failure about firewalld that refers a closed bug, see closure comment here: https://bugzilla.suse.com/show_bug.cgi?id=1083487#c36.
Updated by JRivrain almost 5 years ago
PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/9646
Added a workaround for the reported bug, removed outdated workarounds that were for closed bugs, or slee<15-sp2 ( as it seems like we (qa-sle-y) are the only ones now to use this test suite)
Updated by JRivrain almost 5 years ago
- Checklist item changed from [x] SLE, [ ] Leap, [ ] TW to [x] SLE, [x] TW
- Status changed from In Progress to Feedback
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.
Updated by JRivrain almost 5 years ago
- Status changed from Feedback to Resolved
Test passed in TW and SLE.
Updated by riafarov over 4 years ago
- Related to action #65349: [functional][y][timeboxed:16h] Add validation module for nis mm tests added