Update upgrade paths

[pirat89]

This is followup on announced changed from commit pirat89@5a3bded.
The support for noted RHEL releases ends on May 2024, hence the
upgrade paths related to these releases are dropped.

Upstream tests are going to be covered by #1176. Unless they start to fail due to dropped upgrade paths, we will keep them as they are for now until we can resolve them nicely.

Jira: OAMG-10452

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[github-actions]

Thank you for contributing to the Leapp project!

Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
If you want to request a review or rebuild a package in copr, you can use following commands as a comment:

• review please @oamg/developers to notify leapp developers of the review request
• /packit copr-build to submit a public copr build using packit

Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build. If you need a different version of leapp from PR#42, use /packit test oamg/leapp#42

It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported, beaker-minimal and kernel-rt, both can be used to be run on all upgrade paths or just a couple of specific ones.
To launch on-demand tests with packit:

• /packit test --labels kernel-rt to schedule kernel-rt tests set for all upgrade paths
• /packit test --labels beaker-minimal-8.9to9.3,kernel-rt-8.9to9.3 to schedule kernel-rt and beaker-minimal test sets for 8.9->9.3 upgrade path

[Deprecated] To launch on-demand regression testing public members of oamg organization can leave the following comment:

• /rerun to schedule basic regression tests using this pr build and latest upstream leapp build as artifacts
• /rerun 42 to schedule basic regression tests using this pr build and leapp*PR42* as artifacts
• /rerun-sst to schedule sst tests using this pr build and latest upstream leapp build as artifacts
• /rerun-sst 42 to schedule sst tests using this pr build and leapp*PR42* as artifacts

Please open ticket in case you experience technical problem with the CI. (RH internal only)

Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[packit-as-a-service]

Failed to load packit config file:

Cannot parse package config. ValidationError({'jobs': {3: {'trigger': ['Missing data for required field.']}, 4: {'trigger': ['Missing data for required field.']}, 5: {'trigger': ['Missing data for required field.']}, 6: {'trigger': ['Missing data for required field.']}, 9: {'trigger': ['Missing data for required field.']}, 10: {'trigger': ['Missing data for required field.']}, 12: {'trigger': ['Missing data for required field.']}, 13: {'trigger': ['Missing data for required field.']}, 14: {'trigger': ['Missing data for required field.']}, 15: {'trigger': ['Missing data for required field.']}, 16: {'trigger': ['Missing data for required field.']}, 17: {'trigger': ['Missing data for required field.']}, 18: {'trigger': ['Missing data for required field.']}, 19: {'trigger': ['Missing data for required field.']}, 20: {'trigger': ['Missing data for required field.']}, 21: {'trigger': ['Missing data for required field.']}, 22: {'trigger': ['Missing data for required field.']}, 23: {'trigger': ['Missing data for required field.']}, 24: {'trigger': ['Missing data for required field.']}}})

For more info, please check out the documentation or contact the Packit team. You can also use our CLI command validate-config or our pre-commit hooks for validation of the configuration.

[pirat89]

/packit test

[pirat89]

Note that AWS tests are broken due to a different problem (ignoring these). Tests for dropped upgrade paths started to fail. It's a question whether to wait for a change in packit or whether to do another hacks of tests in the meanwhile. I would honestly wait and ignore the failing tests in case we would be able to use the new structure I created in less than 2w.