[6.16.z] Fix test_positive_global_registration_end_to_end flakiness#21675
Open
Satellite-QE wants to merge 1 commit into
Open
[6.16.z] Fix test_positive_global_registration_end_to_end flakiness#21675Satellite-QE wants to merge 1 commit into
Satellite-QE wants to merge 1 commit into
Conversation
* fixGlobalRegistrationFlakiness * Improve error message in assert. (cherry picked from commit b91b818)
Collaborator
Author
|
Collaborator
Author
|
PRT Result |
Contributor
|
Collaborator
Author
|
PRT Result |
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: #21668
Problem Statement
The
test_positive_global_registration_end_to_endtest fails intermittently due to a date-boundary race condition.The test asserts that today's date appears in yum history output, but when the test runs
near midnight in the content host's local timezone, the yum operations can complete just before midnight (e.g., 2026-05-14 23:59) while the assertion executes just after midnight (e.g., 2026-05-15 00:00:53).
This causes the date check to fail because datetime.now() returns the next day's date, which doesn't match any entry in yum history.
Solution
Accept either today's or yesterday's date in the yum history assertion, accounting for the possibility that operations span the midnight boundary in the content host's timezone.
Error message
PRT test Cases example
Summary by Sourcery
Tests: