-
Notifications
You must be signed in to change notification settings - Fork 114
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
[6.14.z] Integrate FAM pipeline into robottelo #14157
Merged
Griffin-Sullivan
merged 2 commits into
6.14.z
from
cherry-pick-6.14.z-7aca395efcc61aa74809491d02e1c7e1175d36f3
Mar 15, 2024
Merged
[6.14.z] Integrate FAM pipeline into robottelo #14157
Griffin-Sullivan
merged 2 commits into
6.14.z
from
cherry-pick-6.14.z-7aca395efcc61aa74809491d02e1c7e1175d36f3
Mar 15, 2024
Conversation
This file contains 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
(cherry picked from commit 7aca395)
Satellite-QE
added
6.14.z
Introduced in or relating directly to Satellite 6.14
Auto_Cherry_Picked
Automatically cherrypicked PR using GHA
No-CherryPick
PR doesnt need CherryPick to previous branches
labels
Feb 21, 2024
trigger: test-robottelo |
Satellite-QE
added
the
AutoMerge_Cherry_Picked
The cherrypicked PRs of master PR would be automerged if all checks passing
label
Feb 21, 2024
PRT Result
|
Satellite-QE
added
the
PRT-Failed
Indicates that latest PRT run is failed for the PR
label
Feb 21, 2024
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
Satellite-QE
removed
the
PRT-Failed
Indicates that latest PRT run is failed for the PR
label
Mar 15, 2024
PRT Result
|
Satellite-QE
added
the
PRT-Failed
Indicates that latest PRT run is failed for the PR
label
Mar 15, 2024
Griffin-Sullivan
deleted the
cherry-pick-6.14.z-7aca395efcc61aa74809491d02e1c7e1175d36f3
branch
March 15, 2024 14:12
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
6.14.z
Introduced in or relating directly to Satellite 6.14
Auto_Cherry_Picked
Automatically cherrypicked PR using GHA
AutoMerge_Cherry_Picked
The cherrypicked PRs of master PR would be automerged if all checks passing
No-CherryPick
PR doesnt need CherryPick to previous branches
PRT-Failed
Indicates that latest PRT run is failed for the PR
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: #14028
Problem Statement
Current FAM misc pipeline has been broken for a couple releases. This is due to some version changes, but also we were not testing things as accurately as possible. For instance, we were cloning upstream and running the develop branch.
Solution
Integrate the FAM pipeline into robottelo. This now runs everything on the satellite against itself, so we know that the collection being packaged in Satellite is working correctly.
Note
The expectation is not that this will pass 100%. Getting all of the modules and roles to pass will take individual setup that needs to be done in robottelo, AAP, or upstream in the test playbook itself. For now I would like to see that the tests are executing as expected and the results show helpful output on failure (ie: the actual ansible tasking logs). After merging, we will need to evaluate as teams how to remediate the issues based on component and team.