Project

General

Profile

coordination #17208

[sle][functional][yast][y][mandatory][medium][epic] LVM Thin Provisioning

Added by maritawerner over 4 years ago. Updated 12 months ago.

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

100%

Estimated time:
(Total: 16.00 h)
Difficulty:

Description

Motivation

Thin Provisioning is an imporant feature and
as such it makes sense to have at least a basic test - meaning
deployment of the system, which will implicitly test the subsystem itself.
Yast team has fixed a bug in Yast in February about Thin Provisioned LVM
installation. It showed up that there is no test coverage for this in
OpenQA.

Acceptance criteria

  • AC1: An openQA test scenario conducting installation on thin-LVM exists and is scheduled on SLE15, openSUSE Tumbleweed and openSUSE Leap 15.0
  • AC2: Also on SLE12SP4 unless there is a clear message that thin-LVM is not supported on SLE12, see bsc#1027586

Tasks


Subtasks

action #39023: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on openSUSEResolvedmloviska

action #39026: [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning on SLEResolvedmloviska

History

#1 Updated by coolo over 4 years ago

  • Project changed from openQA Project to openQA Tests

#2 Updated by maritawerner over 4 years ago

  • Assignee set to okurz

Oli, could you please add a Milestone to that.

#3 Updated by okurz over 4 years ago

  • Assignee deleted (okurz)
  • Target version set to Milestone 7

earliest milestone I see feasible is M7 considering the current backlog.

#4 Updated by michalnowak over 4 years ago

  • Category set to New test
  • Assignee set to michalnowak

#5 Updated by michalnowak over 4 years ago

  • Status changed from New to In Progress

#6 Updated by maritawerner over 4 years ago

Any progress?

#7 Updated by michalnowak over 4 years ago

  • Status changed from In Progress to Feedback

#8 Updated by okurz over 4 years ago

  • Target version changed from Milestone 7 to Milestone 8

#9 Updated by okurz about 4 years ago

  • Target version changed from Milestone 8 to Milestone 9

#10 Updated by michalnowak about 4 years ago

Is there any use of keeping this ticket in milestone as it most likely won't be fixed in 12SP2 GM time?

#11 Updated by michalnowak about 4 years ago

  • Target version changed from Milestone 9 to Milestone 12

Moving to future milestone so we review it somewhere in 2018 once it's closer to actual implementation.

#12 Updated by sebchlad almost 4 years ago

  • Assignee changed from michalnowak to maritawerner
  • Target version deleted (Milestone 12)

@Michal: thanks for good and clear status.

As I take the role of the Product Owner for the SLE functional, I prefer we clarify if this is a workable item or not. I do not want to have items which are about something what might be done or might not be done and if is done it will be in Sep. 2023 :)

maritawerner: could you kindly verify if there is anything what SLE functional team should we working on here?
If not I would prefer we do not have this in our product backlog.
an idea: still it might be useful for you to have such items in the progress. Perhaps you could then have your own tag for keeping track of such future issues? I would suggest we talk about it f2f

#13 Updated by michalnowak almost 4 years ago

There's a slight chance it will be fixed in SLE15: https://bugzilla.suse.com/show_bug.cgi?id=1027586#c20 but otherwise no, there's no general fix and it hasn't been anyone's priority at all. I suggest we close this and re-open if/when we have an actual fix around.

#14 Updated by okurz almost 4 years ago

I am ok with this assuming it is represented accordingly on FATE for the recently released products and the one currently in development. I want to avoid that it is assumed "everything is working fine". A quick search on fate.suse.com did not reveal anything for me.

#15 Updated by okurz almost 4 years ago

also the recent yast team highlights mention the feature: https://lizards.opensuse.org/2017/10/11/yast-sprint-44/
so it looks like there is something going on and we should not close the ticket but rather revisit it in some time.

#16 Updated by maritawerner almost 4 years ago

I have no additional information here. Let me check with RMs how important that is.

#17 Updated by okurz almost 4 years ago

  • Target version set to future

#18 Updated by maritawerner almost 4 years ago

  • Subject changed from [sles][functional] LVM Thin Provisioning to [sles][functional][mandatory] LVM Thin Provisioning
  • Status changed from Feedback to New
  • Assignee changed from maritawerner to okurz

After a discussion with Stefan Behlert and Daniel Rahn we decided that that feature is important for our customers and I would like to add it to the regular feature test matrix for SLE 15. Please let me know if that is feasible. The bug mentioned above seems to be fixed for SLE 15.

#19 Updated by okurz almost 4 years ago

  • Subject changed from [sles][functional][mandatory] LVM Thin Provisioning to [sle][functional][mandatory] LVM Thin Provisioning
  • Status changed from New to In Progress
  • Assignee deleted (okurz)
  • Target version changed from future to Milestone 14

the bug mentions that only the underlying storage-ng lib properly supports thin provisioning. We can track it and potentially cover it in a short manual test but we should not invest much effort until the bug is at least RESOLVED FIXED.

#20 Updated by michalnowak almost 4 years ago

#21 Updated by riafarov over 3 years ago

  • Status changed from In Progress to Workable

#22 Updated by okurz over 3 years ago

  • Subject changed from [sle][functional][mandatory] LVM Thin Provisioning to [sle][functional][yast][mandatory] LVM Thin Provisioning
  • Due date set to 2018-03-13

#23 Updated by okurz over 3 years ago

  • Subject changed from [sle][functional][yast][mandatory] LVM Thin Provisioning to [sle][functional][yast][mandatory][medium] LVM Thin Provisioning
  • Description updated (diff)
  • Due date changed from 2018-03-13 to 2018-04-24
  • Target version changed from Milestone 14 to Milestone 15

M14 is a bit full so let's shift new tests later.

Made ticket workable with much more information.

#24 Updated by okurz over 3 years ago

  • Subject changed from [sle][functional][yast][mandatory][medium] LVM Thin Provisioning to [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning
  • Due date deleted (2018-04-24)
  • Target version changed from Milestone 15 to Milestone 17

too many new tests in sprint 15, better look for a later one, after SLE15 GMC. https://bugzilla.suse.com/show_bug.cgi?id=1027586 is still open but I would not consider ourselves blocked by it.

#25 Updated by michalnowak over 3 years ago

Per https://bugzilla.suse.com/show_bug.cgi?id=1027586#c22 this ticket may be workable on SLES15.

#26 Updated by okurz over 3 years ago

  • Target version changed from Milestone 17 to Milestone 21+

#27 Updated by okurz over 3 years ago

  • Target version changed from Milestone 21+ to Milestone 21+

#28 Updated by riafarov about 3 years ago

  • Due date set to 2018-08-14

#29 Updated by riafarov about 3 years ago

  • Estimated time set to 8.00 h

Start with TW/Leap 15.1. riafarov will convert to EPIC

#30 Updated by mloviska about 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska

#31 Updated by riafarov about 3 years ago

  • Subject changed from [sle][functional][yast][y][mandatory][medium] LVM Thin Provisioning to [sle][functional][yast][y][mandatory][medium][epic] LVM Thin Provisioning

#32 Updated by mloviska about 3 years ago

  • Status changed from In Progress to Workable
  • Assignee deleted (mloviska)

#33 Updated by okurz about 3 years ago

  • Due date changed from 2018-08-14 to 2018-09-25

due to changes in a related task

#34 Updated by mloviska about 3 years ago

  • Assignee set to mloviska

How we should proceed with this ticket ? bsc#1027586 is hitting only sle12sp4 and the rest of the distributions are fine. Could we just track the bug and close related progress tickets?

#35 Updated by okurz about 3 years ago

Yes, we can. A general acceptance criterion is always "Test is passed or fails on valid product bug" so I assume we have this covered :) But first we should close all subtasks.

#36 Updated by mloviska about 3 years ago

  • Status changed from Workable to In Progress

#37 Updated by mloviska about 3 years ago

  • Status changed from In Progress to Resolved

#38 Updated by szarate 12 months ago

  • Tracker changed from action to coordination

Also available in: Atom PDF