action #34765
closedcoordination #9572: [sles][functional][autoyast][yast][y][epic]AutoYaST testing - build autoyast.xml and then test
[functional][y][medium] enable reinstall scenario on s390x
0%
Description
Motivation¶
We want to have same scenario enable for s390x, as we have for all other architectures
Now ay tests can work on zVM and zKVM with certain limitations, but reinstall scenario cannot work on none of them.
Challenges¶
On zVM scenario won't work as it is now, as we boot into image of the installed system to clone it.
On zKVM it works better, but created profile cannot be reused cause of static network configuration for particular worker, so has to be replaced.
Acceptance criteria¶
- AC1: autoyast_reinstall scenario is enabled at least for one kind of s390x machine (e.g. zkvm, xkvm)
Updated by riafarov about 6 years ago
- Category set to New test
@okurz, please consider to schedule. I guess we could do it after SLE15 release, as it's new test and may take a while to implement. On top we also need to improve logging of errors, to make investigation easier.
Updated by okurz about 6 years ago
- Target version set to Milestone 17
Having one s390x autoyast test is most important and we have that now so we can collect a bit of feedback with that one and then come back to this new test here.
Updated by okurz almost 6 years ago
- Due date changed from 2018-07-18 to 2018-07-17
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 18
Updated by riafarov almost 6 years ago
- Due date changed from 2018-07-17 to 2018-07-03
Updated by riafarov almost 6 years ago
- Subject changed from [functional][y] enable reinstall scenario on s390x to [functional][y][medium] enable reinstall scenario on s390x
Updated by riafarov almost 6 years ago
- Status changed from Workable to Resolved
https://openqa.suse.de/tests/1795141
https://openqa.suse.de/tests/1795305 - SLE 15, run will be removed as polluted dashboard with new build name.
Updated by okurz almost 6 years ago
Why not just move the jobs to the development group? I did that now
openqa_client_osd jobs/1795305 put --json-data '{"group_id": 96}'
openqa_client_osd jobs/1795292 put --json-data '{"group_id": 96}'
openqa_client_osd jobs/1795291 put --json-data '{"group_id": 96}'