Project

General

Profile

Actions

action #104292

closed

action #102176: Test the feature "Enable Installer to Configure VLAN on s390x"

action #104289: Implement a simple module to join vlan on s390

Validate joining vlan at startup on s390

Added by JRivrain almost 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2021-12-17
Due date:
% Done:

0%

Estimated time:

Description

This should be done after parent ticket is done and feature https://jira.suse.com/browse/SLE-19611 is implemented.

How to validate:

The easy option:

- check that the "new" menu appears
- specify a VLAN ID when prompted, other than 0 and 1
- verify that a new interface has been created (eg eth0.2 if main interface is eth0 and the vlan ID is 2)
- verify that the file /proc/net/vlan/config was populated with the new interface

The more complicated one:

    - All of the above, plus verify that we the NIC is effectively part of the right VLAN (manually)
    - implement a multi-machine VLAN test in openQA

We should discuss which approach makes more sense, probably the simpler one, as I was told that IBM is already doing the VLAN testing, and otherwise could be more in the scope of the Desktop QA team or maybe qe-core. I discussed with Marius from Wicked project, who nicely explained me how to test this manually. Implementing an automated test is maybe overkill, at least for us YaST testers. Though it could be a good thing to have.


Related issues 1 (0 open1 closed)

Copied from qe-yam - action #104154: Validate joining vlan at startup on s390Rejected2021-12-17

Actions
Actions #1

Updated by JRivrain almost 3 years ago

  • Copied from action #104154: Validate joining vlan at startup on s390 added
Actions #2

Updated by JRivrain almost 3 years ago

  • Status changed from New to Rejected

misuse of subtasks

Actions

Also available in: Atom PDF