action #11922
closed
coordination #9572: [sles][functional][autoyast][yast][y][epic]AutoYaST testing - build autoyast.xml and then test
[sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390
Added by mgriessmeier about 9 years ago.
Updated about 7 years ago.
Description
as discussed with Marita, we want to have AutoYaST tested on s390x as well
Acceptance criteria¶
-
AC1: At least one autoyast test is scheduled on osd or o3 executing an autoyast fresh installation (upgrade scenario is already there) on s390x (any backend)
-
AC2: Check following bugs (manually) if they are still valid and/or take as starting point for automated AY-Installation
Tasks¶
- Take the easiest autoyast test with the simplest profile and run it on s390x :)
- Status changed from New to In Progress
- Status changed from In Progress to New
it's not :-)
current problem: shutdown/reboot is not implemented and missing, "reconnect console issue"
- Is duplicate of coordination #9572: [sles][functional][autoyast][yast][y][epic]AutoYaST testing - build autoyast.xml and then test added
- Subject changed from Add AutoYaST tests for s390 to [sles][functional][s390] Add AutoYaST tests for s390
- Assignee deleted (
mgriessmeier)
I'm not working on that - feel free to pick
- Subject changed from [sles][functional][s390] Add AutoYaST tests for s390 to [sle][functional][s390] Add AutoYaST tests for s390
- Target version set to Milestone 14
- Subject changed from [sle][functional][s390] Add AutoYaST tests for s390 to [sle][functional][s390][yast] Add AutoYaST tests for s390
- Description updated (diff)
- Due date set to 2018-03-13
- Due date changed from 2018-03-13 to 2018-04-10
- Target version changed from Milestone 14 to Milestone 15
- Is duplicate of deleted (coordination #9572: [sles][functional][autoyast][yast][y][epic]AutoYaST testing - build autoyast.xml and then test)
- Related to action #29101: [sle][migration][sle15] Upgrade to SLE15 with z/VM added
- Description updated (diff)
- Status changed from New to Workable
- Subject changed from [sle][functional][s390][yast] Add AutoYaST tests for s390 to [sle][functional][s390][yast][y] Add AutoYaST tests for s390
- Related to coordination #33859: [qe-core][sles][functional][saga][s390x] Review s390x Bugs found by IBM and see what can be implemented in the future added
- Description updated (diff)
- Status changed from Workable to In Progress
- Subject changed from [sle][functional][s390][yast][y] Add AutoYaST tests for s390 to [sle][functional][s390][yast][y][hard] Add AutoYaST tests for s390
pretty sure it's hard because it's covering so many different domains
- Status changed from In Progress to Feedback
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4796
After PR is merged we can enable at least reinstall scenario on zKVM.
Next steps:
Improve logs collection and verify errors during second stage (potentially by checking logs), on top collect logs even if second stage fails.
Enable more scenarios on zVM and zKVM based on profiles from the customers attached above and existing ones. s390x is special and we may either inject s390x specific configuration (e.g. disks configuration, etc.) or have special profiles.
- Due date changed from 2018-04-10 to 2018-04-24
- Status changed from Feedback to In Progress
Reinstall scenario cannot work as we get static ip address in the profile when configure it. So we should either try existing profile, or use one we had used to test installation locally.
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
great achievement. I wonder about AC2, which I did not add. I guess it was mgriessmeier and/or you. Can you comment on these?
Also available in: Atom
PDF