action #9900

[sle][functional][hard][opensuse][y] nis+autofs

Added by lnussel about 4 years ago. Updated 6 days ago.

Status:WorkableStart date:14/12/2015
Priority:NormalDue date:25/02/2020
Assignee:JRivrain% Done:

80%

Category:New testEstimated time:8.00 hours
Target version:QA - future
Difficulty:
Duration: 1097

Description

Motivation

our biggest "customer" uses nis+autofs, so we should have a test for that :)

Acceptance criteria

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:


Checklist

  • SLE
  • Leap
  • TW

Related issues

Related to openQA Tests - action #13252: enable yast2_nis test Resolved 19/08/2016
Blocked by openQA Tests - action #30892: [opensuse][tools]multi-machine worker setup Resolved 29/01/2018

History

#1 Updated by lnussel about 4 years ago

  • Category set to New test

#2 Updated by RBrownSUSE about 4 years ago

  • Checklist set to [ ] SLE, [ ] Leap, [ ] TW

#3 Updated by zluo almost 4 years ago

  • Assignee set to zluo

#4 Updated by zluo almost 4 years ago

  • % Done changed from 0 to 100

pull request sent out now

#5 Updated by RBrownSUSE almost 4 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

#6 Updated by lnussel over 3 years ago

any update on this one?

#7 Updated by zluo over 3 years ago

No not yet. I need to learn about support server which provides nis server functionality.

#8 Updated by zluo over 3 years ago

  • Assignee changed from zluo to dzedro

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

#10 Updated by okurz about 3 years ago

#11 Updated by okurz about 3 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

#12 Updated by okurz about 3 years ago

bump

#13 Updated by dzedro about 3 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.

#14 Updated by okurz about 3 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.

#15 Updated by dzedro about 3 years ago

I can't make something not working just soft fail, but I will try.

#16 Updated by dzedro about 3 years ago

Low prio, no update in openQA and bugs

#17 Updated by okurz about 3 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?

#18 Updated by okurz almost 3 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?

#19 Updated by dzedro over 2 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

#20 Updated by okurz over 2 years ago

  • Subject changed from nis+autofs to [sle][functional][opensuse]nis+autofs

#21 Updated by lnussel over 2 years ago

  • Due date set to 30/11/2017

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

#22 Updated by okurz over 2 years ago

  • Status changed from Feedback to In Progress

"in progress" as in: can be worked on

#23 Updated by sebchlad over 2 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.

#24 Updated by okurz over 2 years ago

  • Target version changed from future to Milestone 12

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

#25 Updated by sebchlad over 2 years ago

  • Assignee set to sebchlad

#26 Updated by okurz about 2 years ago

  • Due date changed from 30/11/2017 to 19/12/2017

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

#27 Updated by okurz about 2 years ago

  • Due date changed from 19/12/2017 to 17/01/2018

#28 Updated by okurz about 2 years ago

  • Due date changed from 17/01/2018 to 30/01/2018
  • Target version changed from Milestone 12 to Milestone 13

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

#29 Updated by okurz about 2 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:

  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.

#30 Updated by okurz about 2 years ago

  • Description updated (diff)

#31 Updated by okurz about 2 years ago

  • Blocked by action #30892: [opensuse][tools]multi-machine worker setup added

#32 Updated by okurz about 2 years ago

  • Due date changed from 30/01/2018 to 27/02/2018
  • Status changed from In Progress to Blocked
  • Target version changed from Milestone 13 to Milestone 14

#33 Updated by okurz almost 2 years ago

  • Due date deleted (27/02/2018)
  • 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.

#34 Updated by okurz almost 2 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

#35 Updated by okurz over 1 year ago

  • Target version changed from Milestone 18 to Milestone 18

#36 Updated by okurz over 1 year ago

  • Target version changed from Milestone 18 to future

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

#37 Updated by okurz 9 months 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.

#38 Updated by okurz 9 months ago

  • Status changed from Blocked to Workable

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

#39 Updated by riafarov 9 months ago

  • Checklist changed from [ ] SLE, [ ] Leap, [ ] TW to [x] SLE, [ ] Leap, [ ] TW
  • Description updated (diff)
  • Due date set to 13/08/2019
  • Assignee deleted (riafarov)

#40 Updated by riafarov 7 months ago

We need to adapt network configuration part, as SLE images use wicked and openSUSE has network manager.

#41 Updated by riafarov 7 months ago

  • Due date changed from 13/08/2019 to 27/08/2019

Targeting remote ssh installation first.

#42 Updated by riafarov 7 months ago

  • Due date changed from 27/08/2019 to 10/09/2019

#43 Updated by riafarov 7 months ago

  • Estimated time set to 8.00

#44 Updated by lnussel 7 months ago

openSUSE Server installations also use wicked, use that one for the server part.

#45 Updated by riafarov 6 months ago

  • Due date changed from 10/09/2019 to 24/09/2019

#46 Updated by riafarov 6 months ago

  • Due date changed from 24/09/2019 to 22/10/2019
  • Status changed from Workable to Blocked
  • Assignee set to riafarov

#47 Updated by riafarov 4 months ago

  • Due date changed from 22/10/2019 to 03/12/2019

#48 Updated by riafarov 3 months ago

  • Due date changed from 03/12/2019 to 14/01/2020

#49 Updated by riafarov about 1 month ago

  • Due date changed from 14/01/2020 to 25/02/2020
  • Status changed from Blocked to New
  • Assignee deleted (riafarov)

Bug is fixed.

#50 Updated by riafarov 7 days ago

  • Status changed from New to Workable

#51 Updated by JRivrain 6 days ago

  • Assignee set to JRivrain

Also available in: Atom PDF