-
Notifications
You must be signed in to change notification settings - Fork 61
Fix 9 to 10 upgrade tests #302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
spetrosi
merged 2 commits into
redhat-cop:main
from
PeterMocary:fix-9-10-upgrade-with-interpret-fixes
Dec 8, 2025
Merged
Fix 9 to 10 upgrade tests #302
spetrosi
merged 2 commits into
redhat-cop:main
from
PeterMocary:fix-9-10-upgrade-with-interpret-fixes
Dec 8, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
richm
reviewed
Dec 1, 2025
richm
reviewed
Dec 1, 2025
d5c723c to
cb257cf
Compare
Collaborator
Author
|
Fixed the linter issues. |
richm
approved these changes
Dec 1, 2025
Collaborator
|
[citest] |
cb257cf to
572a8b2
Compare
richm
approved these changes
Dec 2, 2025
Collaborator
|
[citest] |
572a8b2 to
7a7cab8
Compare
Collaborator
Author
|
Rebased onto main. |
Collaborator
|
[citest] |
10 similar comments
Collaborator
Author
|
[citest] |
Collaborator
|
[citest] |
Collaborator
Author
|
[citest] |
Collaborator
|
[citest] |
Collaborator
|
[citest] |
Collaborator
|
[citest] |
Collaborator
|
[citest] |
Collaborator
|
[citest] |
Collaborator
|
[citest] |
Collaborator
Author
|
[citest] |
7a7cab8 to
b4f5a66
Compare
Collaborator
Author
|
Trying to run the upgrades without the interpreter fix. |
Collaborator
Author
|
[citest] |
b4f5a66 to
2ee11f6
Compare
Collaborator
Author
|
Rebased onto main. |
Collaborator
Author
|
[citest] |
richm
approved these changes
Dec 8, 2025
The post-upgrade task which updates the system packages failed when running upgrade with custom repositories. Since leapp does not update the repositories in /etc/yum.repos.d when upgrading with custom repositories, the post-upgrade update task is now skipped in the case when the leapp_upgrade_type is custom and when the local_repos_post_upgrade are not defined. Jira: RHELMISC-21816
2ee11f6 to
4b25f6a
Compare
Collaborator
Author
|
Added the changelog fragment. |
Collaborator
Author
|
[citest] |
spetrosi
approved these changes
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The post-upgrade task which updates the system packages failed when
running upgrade with custom repositories. Since leapp does not update the
repositories in
/etc/yum.repos.dwhen upgrading with custom repositories,the post-upgrade update task is now skipped in the case when
the
leapp_upgrade_typeis custom and when thelocal_repos_post_upgradeare not defined.
This PR includes commits from the PR#285 already since these fix some issuesThe last commit acts aswith python interpreter encountered in 9 to 10 tests.
a minor fix to the clean up of role tests, since executing these without it caused
them to fail. The analysis role test fails on leapp being not installed since its
dependencies are not satisfied and there is no rescue block for error handling
as in the upgrade role test. Currently these are here just to execute the roles
independently. We need to decide what to do with them in future.