Project

General

Profile

action #39026

coordination #17208: [sle][functional][yast][y][mandatory][medium][epic] LVM Thin Provisioning

[sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on SLE

Added by riafarov almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
New test
Target version:
SUSE QA - Milestone 19
Start date:
2017-02-20
Due date:
2018-09-25
% Done:

0%

Estimated time:
8.00 h
Difficulty:

Description

Motivation

See motivation in parent epic

Acceptance criteria

  • AC1: An openQA test scenario conducting installation on thin-LVM exists and is scheduled on SLE15
  • AC2: Also on SLE12SP4 unless there is a clear message that thin-LVM is not supported on SLE12, see bsc#1027586
  • AC3: Add support for other boot methods for the rest of supported architectures

Tasks

History

#1 Updated by riafarov almost 4 years ago

  • Copied from action #39023: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on openSUSE added

#2 Updated by riafarov almost 4 years ago

  • Copied from deleted (action #39023: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on openSUSE)

#3 Updated by riafarov almost 4 years ago

  • Parent task set to #17208

#4 Updated by mloviska almost 4 years ago

  • Description updated (diff)

#5 Updated by okurz almost 4 years ago

  • Due date set to 2018-09-25
  • Target version changed from Milestone 18 to Milestone 19

As discussed with riafarov, give some grace period after we have openSUSE tests now before we enable the same on SLE

#6 Updated by mloviska over 3 years ago

  • Assignee set to mloviska

#7 Updated by mloviska over 3 years ago

  • Status changed from Workable to In Progress

#8 Updated by mloviska over 3 years ago

test works fine on sle15sp1, however sle12sp4 is still blocked by Can't create thinpool: LVM_LV_CREATE_FAILED: System error code was: -4014

#10 Updated by mloviska over 3 years ago

  • Status changed from In Progress to Feedback

PR is merged by now. I will enable the test for sle15sp1 since there has not been any issue observed yet. Regarding sle12sp4, I would rather enable it on dev group so we can label the failure with bug properly at least. Thus it should be easier to track it.

#12 Updated by okurz over 3 years ago

I think this is nearly good enough. As stated in the parent ticket, a general acceptance criterion is always "test passes or fails in valid product bug" and I think we have that. https://trello.com/c/XghjsYUv/183-sle12-sp2-p2-1027586-cant-create-thinpool-lvmlvcreatefailed-system-error-code-was-4014 mentions that the priority of the issue might increase. I recommend to move the SLE12 scenario to the validation job group as well. Then we can close this progress ticket as "Resolved".

#13 Updated by mloviska over 3 years ago

  • Status changed from Blocked to Resolved

sle12sp4 dev group contains the job for all archs.
sle15sp1 dev group has the rest.

Also available in: Atom PDF