action #53855
closed
[functional][y][timeboxed:4h] Create multi-machine Test Suite for NFS
Added by oorlov almost 5 years ago.
Updated over 4 years ago.
Target version:
SUSE QA - Milestone 30+
Description
****## Motivation
Currently, there are several test modules for NFS testing:
- yast2_nfs_server
- yast2_nfs_client
- yast2_nfs4_server
- yast2_nfs4_client
Though, only yast2_nfs_client is used in test suites on osd and o3 (in yast2_ncurses, example: https://openqa.suse.de/tests/3029961). And only steps for single-machine setup are used, i.e. server is created on the same machine where the client is.
At the same time, the PR introduced code for multi-machine test, but it is not executed anywhere.
Acceptance criteria¶
- nfs client and nfs server yast modules are tested for SLE 15 or follow up ticket is created with problem described
Task¶
- Create multi-machine test suite where yast2_nfs_server and yast2_nfs_client will be used; (optional)
- Create multi-machine test suite where yast2_nfs4_server and yast2_nfs4_client will be used;
- Ensure that both scenarios are working with the existing code, otherwise fix the issues;
- Add the scenarios to both o3 and osd.
NOTE: Please, pay attention while estimating the task, that the code already exist. The task is mainly to make it run on openQA (slight fixes might be required, though).
- Due date set to 2019-09-10
- Target version set to Milestone 30+
- Subject changed from [functional][y] Create multi-machine Test Suite for NFS to [functional][y][timeboxed:4h] Create multi-machine Test Suite for NFS
- Description updated (diff)
- Status changed from New to Workable
- Due date changed from 2019-09-10 to 2019-09-24
- Due date changed from 2019-09-24 to 2019-10-22
- Status changed from Workable to Blocked
- Assignee set to riafarov
- Due date changed from 2019-10-22 to 2019-11-19
- Status changed from Blocked to Workable
- Assignee deleted (
riafarov)
MM on o3 works, so can start working on this.
- Status changed from Workable to In Progress
Tested locally, it works, but I want to see things:
- there is a workaround, not sure it applies to sp2
- may be good to use YAML
- Due date changed from 2019-11-19 to 2019-12-03
Need to discuss how to proceed.
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
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.
- Due date changed from 2019-12-03 to 2019-12-17
Need to enable test suite and update test plan.
- Status changed from In Progress to Feedback
All is merged. We may want to keep it in feedback for 2 more days, until we made sure it's working everywhere
- Status changed from Feedback to Resolved
Tests working everywhere.
Also available in: Atom
PDF