action #18896
closed
- Status changed from New to In Progress
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
The settings of s390x online migration on zkvm-image and x86_64 are almost same, tried to unify the settings for both x86_64 and s390x in order to use 1 case to run on the 2 archs.(At least pre-created images follow the same naming rule).
Added 10 s390x online migration into the Migration(server and ha) job groups:
om_proxyscc_sles12sp1_allpatterns_full_update_by_yast
om_proxyscc_sles12sp1_allpatterns_minimal_patch_by_zypper
om_proxyscc_sles12sp1_sdk+allpatterns_full_update_by_yast
om_proxyscc_sles12sp2_allpatterns_minimal_patch_by_zypper
om_proxyscc_sles12sp2_allpatterns_full_update_by_zypper
om_proxyscc_sles12sp2_sdk+allpatterns_full_update_by_zypper
om_proxyscc_sles12sp1_ha+geo+allpatterns_full_update_by_zypper
om_proxyscc_sles12sp1_ha+allpatterns_full_update_by_yast_s390x
om_proxyscc_sles12sp2_ha+allpatterns_full_update_by_zypper
om_proxyscc_sles12sp2_ha+geo+allpatterns_full_update_by_yast
see the results in next build.
rest lower priority cases would be put into Milestone groups.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF