Actions
action #60617
closedcoordination #60071: [functional][y][epic] SLE 15 SP2 feature testing
[functional][y][SLE-7737][SLE-7687][timeboxed:24h] boot timeout handling (ensure fallback to emergency shell, speedup safe mode, handle encrypted device fails)
Status:
Resolved
Priority:
High
Assignee:
Category:
Spike/Research
Target version:
SUSE QA (private) - Milestone 33
Start date:
2019-12-04
Due date:
2020-05-05
% Done:
0%
Estimated time:
Difficulty:
Description
See https://jira.suse.com/browse/SLE-7687 and https://jira.suse.com/browse/SLE-7737
Exploratory manual testing.
So it's just about "So the request is for YaST to add the "nofail" parameter to crypttab in the respective case.". iSCSI can be started in docker container https://github.com/rwx788/docker_images
but we need ibft to boot from it.
For ibft configuration:
- Download https://ipxe.org/download
- Specify path to the file as path to kernel (Direct kernel boot in VM manager or '-kernel /usr/share/qemu/ipxe.lkrn' for qemu command)
- Specify iscsi target parameter dhcp && sanhook %iSCSI_TARGET% (kernel args in VM manager or '-append dhcp && sanhook iscsi:10.160.1.93::3260:1:iqn.2016-02.openqa.de:for.openqa' for qemu)
- Specify withiscsi=1 boot option for the installer to get iSCSI disks configuration page
Acceptance criteria¶
- Scope of changes is learned
- Exploratory testing is conducted for the parts which are not covered by the automated tests
- Follow-up tickets for automated tests are created with detailed description in case are considered to be useful (efforts vs profit)
- jira ticket is updated accordingly
Updated by riafarov about 5 years ago
- Subject changed from [functional][y][SLE-7737][SLE-7687] boot timeout handling (ensure fallback to emergency shell, speedup safe mode, handle encrypted device fails) to [functional][y][SLE-7737][SLE-7687][timeboxed:24h] boot timeout handling (ensure fallback to emergency shell, speedup safe mode, handle encrypted device fails)
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
Updated by JERiveraMoya about 5 years ago
- Status changed from Workable to Blocked
Updated by riafarov about 5 years ago
- Target version changed from Milestone 29 to Milestone 30+
Updated by riafarov about 5 years ago
- Due date changed from 2019-12-17 to 2020-01-28
- Assignee changed from JERiveraMoya to riafarov
Changing assignee to me to track the bug progress.
Updated by mgriessmeier almost 5 years ago
- Target version changed from Milestone 30+ to Milestone 30
bulk moved to M30 for revisiting
Updated by riafarov almost 5 years ago
- Due date changed from 2020-01-28 to 2020-02-25
Updated by riafarov almost 5 years ago
- Due date changed from 2020-02-25 to 2020-03-10
Updated by JERiveraMoya almost 5 years ago
- Due date changed from 2020-03-10 to 2020-03-24
Updated by riafarov almost 5 years ago
- Due date changed from 2020-03-24 to 2020-04-07
- Target version changed from Milestone 30 to Milestone 33
Still blocked.
Updated by riafarov over 4 years ago
- Due date changed from 2020-04-07 to 2020-04-21
Patch for one of bugs is fixed and other is submitted to factory. So might get unblocked soon.
Updated by riafarov over 4 years ago
- Due date changed from 2020-04-21 to 2020-05-05
- Status changed from Blocked to Workable
- Assignee deleted (
riafarov)
Updated by riafarov over 4 years ago
- Status changed from Workable to In Progress
- Assignee set to riafarov
Updated by riafarov over 4 years ago
- Status changed from In Progress to Resolved
#66052 is created for automation.
Actions