Project

General

Profile

Actions
Copy link

coordination #34333

closed

[functional][y][epic] More test scenarios covering installation on existing partition layouts

Added by okurz about 6 years ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
QA - future
Start date:
2017-10-20
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Motivation

#26922 should be enough motivation :) - as well as bugs about custom partition layouts and also a fate issue that huha asked riafarov and okurz about for SLE12SP4 if we can update parted and would feel safe about it - and autoyast!

Acceptance criteria

  • AC1: At least one autoyast test on existing partition layout for SLE15+SLE12SP4+TW+Leap (suggestion: reuse image created by create_hdd_job)
  • AC2: Make sure that there is at least one scenario reinstalling on existing partition layout on s390x (could be the existing cryptlvm+…) because we want to cover s390x as well
  • AC3: At least one scenario reusing all existing partitions
  • AC4: Like AC3 but only reuse /home -> check for the subvolumes! (ask riafarov for the bug if in doubt)

Suggestions

  • Look into the existing cryptlvm+… scenarios because they already do that
  • Try to find important/critical bugs about this and get the "partition layout" from there

Subtasks 3 (0 open — 3 closed)

action #26922: [ceo][sle][functional][y][medium]installation of unregistered sled on existing partition tableResolvedriafarov2017-10-20

Actions
action #35959: [sle][functional][y][s390x][medium] Add tests for s390x to test on "existing sle on dasd" and explicitly test the DASD formatting during installationResolvedriafarov2018-05-07

Actions
action #37039: [sle][functional][y] Partition disk before installation to verify storage proposalRejected2018-06-11

Actions
Actions
Copy link
 #1

Updated by okurz about 6 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by okurz about 6 years ago

  • Due date changed from 2018-04-24 to 2018-05-22

due to changes in a related task

Actions
Copy link
 #4

Updated by oorlov almost 6 years ago

  • Status changed from New to Workable
Actions
Copy link
 #5

Updated by riafarov almost 6 years ago

  • Due date changed from 2018-06-05 to 2018-06-19

due to changes in a related task

Actions
Copy link
 #6

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 18 to Milestone 18
Actions
Copy link
 #7

Updated by okurz almost 6 years ago

  • Due date changed from 2018-06-19 to 2018-12-31

due to changes in a related task

Actions
Copy link
 #8

Updated by okurz almost 6 years ago

  • Target version changed from Milestone 18 to Milestone 21+
Actions
Copy link
 #9

Updated by riafarov over 5 years ago

  • Due date changed from 2018-12-31 to 2019-01-29

due to changes in a related task

Actions
Copy link
 #10

Updated by okurz over 5 years ago

  • Target version changed from Milestone 21+ to future

-> #37039

Actions
Copy link
 #11

Updated by riafarov over 5 years ago

  • Due date changed from 2019-01-29 to 2018-06-19

due to changes in a related task

Actions
Copy link
 #12

Updated by szarate over 3 years ago

  • Tracker changed from action to coordination
  • Status changed from Workable to New
Actions
Copy link
 #14

Updated by riafarov over 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (New test)
Actions
Copy link
 #15

Updated by okurz over 2 years ago

This ticket had a due set but exceeded it already by more than 14 days. We would like to take the due date seriously so please update the ticket accordingly (resolve the ticket or update the due-date or remove the due-date). See https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives for details. This update was done as agreed within the SUSE QE Sync call 2021-09-01

Actions
Copy link
 #16

Updated by JERiveraMoya 2 months ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF