action #32008
closed[sles][functional][s390x] Adapt bootloader_s390 to be able to work properly with z/VM 6.3
0%
Description
User story¶
With the breakdown of our storage backend (DS8100) for s390x, we've lost all z/VM guests which were running on z/VM 5.4
right now it's not clear yet if the DS8100 will become functional again, since the machine is already out of support
For now we've installed a z/VM 6.3 on the new storage backend (DS8870) as temporary solution.
However, even if we manage to get the z/VM 5.4 back, since it's pretty old, we will also migrate all existing guests on z/VM 5.4 to a newer version (6.3 or 6.4)
Since the behaviour of the x3270 terminal changed significantly in z/VM 6.3 compared to 5.4, it's necessary to adapt the bootloader_s390 test, to match this new behaviour
Further details¶
I don't think it's necessary to provide compability for both versions due to the reasons stated above
Workaround¶
Right now, there is a workaround in implementation, which uses needles instead of checking the actual output.
The task in this ticket is mainly to rewrite this workaround to be more robust an reliable
Tasks¶
- Rewrite current workaround to rely again on actual output from the x3270 terminal
- remove workaround needles
Updated by mgriessmeier about 6 years ago
- Follows action #32011: [sles][functional][s390x][fast] Adapt openQA to use temporary z/VM guests after breakdown of our Mainframe storage system added
Updated by okurz about 6 years ago
- Status changed from New to In Progress
- Assignee set to mgriessmeier
Is this now covered with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4446 already?
Updated by mgriessmeier about 6 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
mgriessmeier)
okurz wrote:
Is this now covered with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4446 already?
no it's not.
Right now, there is a workaround in implementation, which uses needles instead of checking the actual output.
The task in this ticket is mainly to rewrite this workaround to be more robust an reliable
see also preceding ticket.
this one should be planned for later
Updated by mgriessmeier about 6 years ago
- Status changed from Workable to Rejected
rejecting, since we switched back to the old configuration
at some point in the future, our guests will be migrated to z/VM 6.3 - but that's another story