action #58909

action #42854: [functional][y][epic] Introduce relevant installation validation test modules

[functional][y] Validate ext4 installation

Added by riafarov 8 months ago. Updated 7 months ago.

New test
Target version:
SUSE QA tests - Milestone 30+
Start date:
Due date:
% Done:


Estimated time:
5.00 h
Duration: 34


See motivation in the parent ticket.

Scope is SLE 15 SP2 only + staging.

Acceptance criteria

  1. Only test modules which are relevant for the scenario are scheduled
  2. Partitioning is validated (ext4 for root)
  3. Test plan document is updated accordingly:


  1. Smoke test that we can read/write from/to fs
  2. Validate partitioning
  3. Validate proposal (existence of swap and separate home)


#1 Updated by riafarov 8 months ago

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

#2 Updated by okurz 8 months 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_ext4

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

#3 Updated by riafarov 8 months ago

  • Due date changed from 2019-11-19 to 2019-12-03

#4 Updated by syrianidou_sofia 8 months ago

  • Assignee set to syrianidou_sofia

#5 Updated by JERiveraMoya 8 months ago

Once you will start to work on this ticket, do not forget to change status to "In Progress".
I guess you will be focus on the validation, but if you don't mind, try to start to send Pull Request (PR) with yaml schedule first, so from that moment you will be able to gather more feedback in GitHub.

#6 Updated by syrianidou_sofia 8 months ago

  • Status changed from Workable to In Progress

#7 Updated by riafarov 7 months ago

  • Due date changed from 2019-12-03 to 2019-12-17

#8 Updated by syrianidou_sofia 7 months ago

  • Status changed from In Progress to Feedback

#9 Updated by JRivrain 7 months ago

We should see with tools team what is going on here:

#10 Updated by okurz 7 months ago

simple, there is no network. compare the string after "eth?:" in for the failed job and the corresponding reference ext4_yast@uefi in showing a valid network adress for eth0. I wonder why the aarch64 test has an eth1 instead of eth0. Previous build was still having eth0 in . I suggest to check , haven't looked there.

#11 Updated by riafarov 7 months ago

  • Status changed from Feedback to Resolved

We will investigate the failure (as seems as a product bug) in separate ticket.

#12 Updated by syrianidou_sofia 7 months ago

Looks like it's related to Bug#1158025

Also available in: Atom PDF