action #33262
closed
coordination #29042: [sle][functional][y][saga] offline installation
coordination #33259: [sle][functional][epic][u] offline installation - test for openSUSE with a SUT that does not have access to any external server, e.g. no dns resolution
[sle][functional][u][hard]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution
Added by okurz about 6 years ago.
Updated about 6 years ago.
Description
Acceptance criteria¶
- AC1: New test scenario with no access to any external server conducting at least the installation (INSTALLONLY?)
Suggestions¶
- Experiment with qemu network parameters to disable network, fallback to linuxrc parameters
- Conduct an openQA test and see what can be covered without major changes to test code
- Optionally: Based on a test parameter exit test early, e.g. INSTALLONLY=1 in case later test modules do not work without proper network
- Subject changed from [sle][functional][epic] offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution to [sle][functional]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution
- Subject changed from [sle][functional]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution to [sle][functional][u]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution
- Status changed from New to Workable
actually it is already workable. Please set to "In Progress" when actually working on it.
- Subject changed from [sle][functional][u]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution to [sle][functional][u][hard]offline installation - test for openSUSE TW with a SUT that does not have access to any external server, e.g. no dns resolution
- Status changed from Workable to In Progress
PRs merged.
Waiting for next update cycle on openQA as backend code was modified.
Settings for new testsuite to be created after openQA update:
Testsuite name: install_offline
DESKTOP=textmode
INSTALLONLY=1
OFFLINE_SUT=1
VIDEOMODE=text
- Status changed from In Progress to Feedback
- Due date changed from 2018-04-10 to 2018-04-24
- Due date changed from 2018-04-24 to 2018-05-08
- Status changed from Feedback to Blocked
- Target version changed from Milestone 15 to Milestone 16
waiting for deployment of o3
- Status changed from Blocked to Workable
o3 was deployed and has the corresponding os-autoinst support. I checked with looking into the changelog of the package os-autoinst on openqaworker4 looking for "Add OFFLINE_SUT mode to QEMU backend (#940)".
- Status changed from Workable to In Progress
testsuite install_offline created on o3.
- Status changed from In Progress to Resolved
- Status changed from Resolved to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF