[6.19.z] Move test_podman_login_check to destructive tests - #21128
Merged
Gauravtalreja1 merged 1 commit intoApr 7, 2026
Merged
Conversation
(cherry picked from commit 5deb533)
Collaborator
Author
|
trigger: test-robottelo |
Contributor
Reviewer's GuideMoves the IoP-specific podman login health check test from the generic maintain health test module into a new destructive health test module without changing its behavior, so that it no longer affects subsequent tests on the same host. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Gauravtalreja1
approved these changes
Apr 7, 2026
Gauravtalreja1
deleted the
cherry-pick-6.19.z-5deb533b2a67bc6ad02c573197025f82a401f277
branch
April 7, 2026 06:54
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
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.
Cherrypick of PR: #20849
Problem Statement
On an IoP-enabled Satellite, test_podman_login_check logs out of the container registry at the end of the test and uses a finalizer that also calls podman_logout. That leaves the host in a logged-out state. Other tests that run on the same host (e.g. test_positive_health_check_pre_upgrade when the “satellite” host is IoP) then run pre-upgrade health checks that include “Check whether podman needs to be logged in to the registry,” and those checks fail because podman is still logged out.
Solution
Move the test_podman_login_check to destructive so other test are successfully run
Related Issues
Summary by Sourcery
Bug Fixes:
Summary by Sourcery
Tests: