action #35706
[functional][y] partitioning_splitusr need to process warning message
0%
Description
Observation¶
We resize root partition to 1.5GiB, so even if we have big enough HDD for proposal, we need to adjust test to either process warning message (as snapshots are enabled), or increase size of '/' partition.
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-splitusr@64bit fails in
partitioning_splitusr
Reproducible¶
Fails since (at least) Build 20180426
Expected result¶
Last good: 20180425 (or more recent)
Acceptance criteria¶
- AC1: Test scenario "splitusr" is fine on all SLE15, SLE12, TW, Leap tests
Further details¶
Always latest result in this scenario: latest
I'm filing it here as I'm not entirely sure where the expectation for the root partition comes from and if YaST was supposed to pre-crrate this (the earlier screenshots mentioned no proposal possible, thus entering guided mode - so not having a root pre-defined would sound reasonable too)
History
#1
Updated by okurz almost 5 years ago
- Subject changed from partitioning_splitusr: no root partition defined to [functional][y] partitioning_splitusr: no root partition defined
- Due date set to 2018-06-19
- Target version set to Milestone 17
#2
Updated by riafarov almost 5 years ago
Actual issue is that we don't get proposal for 10GB disk https://openqa.opensuse.org/tests/668420#step/partitioning/1 See https://bugzilla.suse.com/show_bug.cgi?id=1089274
#3
Updated by riafarov almost 5 years ago
- Subject changed from [functional][y] partitioning_splitusr: no root partition defined to [functional][y] partitioning_splitusr need to process warning message
- Description updated (diff)
#4
Updated by okurz almost 5 years ago
- Description updated (diff)
#5
Updated by riafarov almost 5 years ago
- Due date changed from 2018-06-19 to 2018-06-05
- Status changed from New to Workable
Suggest for S18, as have capacity.
#6
Updated by mloviska almost 5 years ago
- Status changed from Workable to In Progress
- Assignee set to mloviska
#7
Updated by mloviska almost 5 years ago
- Status changed from In Progress to Feedback
#8
Updated by mloviska almost 5 years ago
- Status changed from Feedback to Resolved
#9
Updated by okurz almost 5 years ago
guys, you are becoming so fast to fix issues, it's a joy, really :) Thanks.
#10
Updated by okurz almost 5 years ago
- Target version changed from Milestone 17 to Milestone 17