Project

General

Profile

Actions

action #59193

closed

action #50669: [functional][y] Test autoyast installation with NFS share mount point

[functional][y] New test suite for NFS in autoyast

Added by JRivrain over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA - Milestone 30
Start date:
2019-11-07
Due date:
2020-02-11
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

Motivation

It is possible to enable some nfs share during installation, so autoyast supports it. We could automate the testing of this.

Scope is SLE 15 SP2 only.

Acceptance criteria

  • A test suite with nfs share created in autoyast exists
  • Mount of nfs share is validated in the end of installation
  • Generation of the profile is also validated in the SUT

Suggestions

  • In a VM that fits our tests, add a nfs share ( this will do: echo "openqa.suse.de:/var/lib/openqa/share /mnt nfs defaults 0 0" >> /etc/fstab ; mount /mnt )
  • generate an autoyast profile with yast2 clone_system
  • create a test suite that installs a system with that autoyast profile, then verifies that the nfs share is mounted after install.

We can reuse MIRROR_NFS variable to be mounted (nfs share on osd).
Autoyast documentation can be found here: https://documentation.suse.com/sles/15-SP1/single-html/SLES-autoyast/#book-autoyast

Don't forget to update test plan

Actions #1

Updated by JRivrain over 4 years ago

  • Subject changed from [functional]y] New test suite for NFS in autoyast to [functional][y] New test suite for NFS in autoyast
Actions #2

Updated by riafarov over 4 years ago

  • Due date set to 2019-12-03
  • Category set to New test
  • Target version set to Milestone 30+
Actions #3

Updated by riafarov over 4 years ago

  • Due date changed from 2019-12-03 to 2019-12-17
Actions #4

Updated by riafarov over 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h
Actions #5

Updated by riafarov over 4 years ago

  • Due date changed from 2019-12-17 to 2020-01-28
Actions #6

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 30+ to Milestone 30

bulk moved to M30 for revisiting

Actions #7

Updated by ybonatakis over 4 years ago

  • Assignee set to ybonatakis
Actions #8

Updated by riafarov over 4 years ago

  • Due date changed from 2020-01-28 to 2020-02-11
Actions #9

Updated by ybonatakis over 4 years ago

  • Assignee deleted (ybonatakis)
Actions #10

Updated by JERiveraMoya over 4 years ago

  • Assignee set to JERiveraMoya
Actions #11

Updated by JERiveraMoya over 4 years ago

  • Status changed from Workable to In Progress
Actions #12

Updated by JERiveraMoya over 4 years ago

  • Status changed from In Progress to Blocked
Actions #13

Updated by JERiveraMoya over 4 years ago

  • Status changed from Blocked to In Progress
Actions #14

Updated by JERiveraMoya over 4 years ago

For using /mnt probably there is a bug, but we can move on we automation if we use /test for example as a mount point.

Actions #15

Updated by JERiveraMoya about 4 years ago

  • Status changed from In Progress to Feedback
Actions #16

Updated by JERiveraMoya about 4 years ago

  • Status changed from Feedback to Resolved
Actions #17

Updated by okurz about 4 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: autoyast_nfs_share
https://openqa.suse.de/tests/3900031

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions

Also available in: Atom PDF