action #115487
Updated by JERiveraMoya over 1 year ago
#### Motivation #### ## **Motivation** After the migration takes places, there are plenty of test modules schedules unrelated with migration. Refer cases: https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=12.1&groupid=267 ## **Scope** Other modules like ` migration/openldap_to_389ds` or `console/orphaned_packages_check` or basic checks Include all of the migrated system should remain there. migration path in regression job group ## **Acceptance criteria** But test java or curl or libc, according to history of test runs there is no justification to do it, if it would worth it because we would encounter some bug we could consider to communicate other QE squad to take over for the this userspace tools. Need update all of yaml regression files: sle/schedule/migration # ls *regression* aarch64_regression_test_offline.yaml ppc64le_regression_test_offline.yaml s390x_regression_test_offline.yaml x86_regression_test_offline.yaml aarch64_regression_test_online.yaml ppc64le_regression_test_online.yaml s390x_regression_test_online.yaml x86_regression_test_online.yaml #### Scope #### Include all migration path in [regression job group](https://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=12.1&groupid=267) #### Acceptance criteria #### **AC1**: Update all the schedules mentioned above according to the motivation ## **Suggestions**