Project

General

Profile

action #47447

[functional][y][SLE-4193][fate316134] Create btrfs subvolume instead of home directory

Added by riafarov about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
okurz
Category:
New test
Target version:
SUSE QA - Milestone 25
Start date:
2019-02-12
Due date:
2019-06-04
% Done:

0%

Estimated time:
3.00 h
Difficulty:

Description

See https://github.com/yast/yast-users/pull/195 for more details

jira: https://jira.suse.de/browse/SLE-4193
fate: https://fate.suse.com/316134
qa-task on the Desktop team: https://jira.suse.de/browse/SLE-4319

Here are some test descriptions:
https://gist.github.com/dgdavid/20b7602d7f03578c1ec9ec4fd7465aa4

SR in review for TW: https://build.opensuse.org/request/show/673894 -> https://build.opensuse.org/request/show/674443

Related issues

Related to openQA Tests - action #45770: [functional][y][opensuse] test separate home for TW and leap 15.1Resolved2019-01-072019-03-12

History

#1 Updated by riafarov about 4 years ago

  • Description updated (diff)

#2 Updated by okurz about 4 years ago

  • Category set to New test
  • Target version set to Milestone 23

The referenced jira issue is a "Dev" subtask for SLED and it's tracked by the "Desktop" team. https://jira.suse.de/issues/?jql=%22External%20Id%22%20~%20%22316134%22 shows all related tickets. This new jira based workflow is a mess :,(

We can plan for ourselves how to test it manually once or think about automation but for now I would not care about an "offical feature test"

#3 Updated by riafarov about 4 years ago

  • Priority changed from Normal to Low

Nice catch, we definitely should not do same thing twice, so I lower priority.
SR for SLE15: https://build.suse.de/request/show/184338

#4 Updated by okurz about 4 years ago

  • Description updated (diff)
  • Status changed from Blocked to Workable

Both SRs for SLE and TW are accepted 4 days ago, i.e. current/next builds should how the feature in action. If you like give it a quick manual test and inform the Desktop team about the test results, e.g. with a comment in the various duplicate jira tickets. Or we just wait for the Desktop team to do it. In that case again we have choices, e.g. reject this ticket and see what happens or set it to "Blocked" by the QA task in the jira ticket on the Desktop team. I leave the choice to you :)

#5 Updated by riafarov about 4 years ago

  • Assignee deleted (riafarov)

As per last comment.

#6 Updated by riafarov about 4 years ago

  • Related to action #45770: [functional][y][opensuse] test separate home for TW and leap 15.1 added

#7 Updated by riafarov about 4 years ago

  • Estimated time set to 3.00 h

#8 Updated by okurz about 4 years ago

  • Due date changed from 2019-03-12 to 2019-06-04
  • Target version changed from Milestone 23 to Milestone 25

Let's give the Desktop team their time to validate that feature. We can catch in M25 if they don't

#9 Updated by okurz about 4 years ago

  • Description updated (diff)
  • Status changed from Workable to Blocked
  • Assignee set to okurz

I will track the QA Task on the desktop team.

#10 Updated by riafarov about 4 years ago

okurz wrote:

Let's give the Desktop team their time to validate that feature. We can catch in M25 if they don't

Makes sense. Thanks!

#11 Updated by okurz about 4 years ago

  • Status changed from Blocked to Resolved

Grace has set the QA task to done.

The comment lists the detailed test results. I guess this should be enough for now.

Also available in: Atom PDF