-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
OCPBUGS-43478: generalize the RHEL8 and RHEL9 subscription_content.go test #29315
base: master
Are you sure you want to change the base?
Conversation
@chandra0007: This pull request references Jira Issue OCPBUGS-43478, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
The bug has been updated to refer to the pull request using the external bug tracker. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small nits...
/lgtm
/retest-required |
Job Failure Risk Analysis for sha: 3ba811b
|
/retest-required |
e2e-gcp-ovn-builds is blocked by https://issues.redhat.com/browse/OCPBUGS-44257 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
based on a review, these changes make sense. I'll watch the verify job.
Hey @adambkaplan I hope you are well. We are updating the subscription_content.go tests to be multiarch. Could you review / approve or assign? Thanks, Paul |
/retest |
Job Failure Risk Analysis for sha: 2149030
|
For ubi 8 and 9, I believe the RHEL repositories use the following convention:
I think you are better off editing the YAML in test/extended/testdata/builds/subscription-content directly. |
Hey @adambkaplan Are you suggesting we have multiple yamls? One for each arch? If so, we'd happily make that change. Thanks Paul |
Quite the opposite - one YAML per RHEL version, but in-line the |
Got it! I'll chat with Chandra when he is back in office (tomorrow) |
Job Failure Risk Analysis for sha: 9b4bbee
|
Thanks Chandra, this looks good, let's watch the job results. |
/retest |
/retest-required |
1 similar comment
/retest-required |
Job Failure Risk Analysis for sha: 074e750
|
Hey @adambkaplan We analyzed the logs and find this PR is ready for LGTM and further review. The only failure we see is known: The PR #29355 and bug https://issues.redhat.com/browse/OCPBUGS-44257
Thanks, Paul |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Realized that what we need is the output from the arch
command to get the right RPM repo.
As a bonus, much of the changes in subscription_content.go
can be reverted here.
test/extended/testdata/builds/subscription-content/buildconfig-subscription-content-rhel9.yaml
Outdated
Show resolved
Hide resolved
test/extended/testdata/builds/subscription-content/buildconfig-subscription-content-rhel8.yaml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thanks Chandra
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: chandra0007, prb112 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Job Failure Risk Analysis for sha: 00ad317
|
… test Signed-off-by: Chandrasekhar B <[email protected]>
New changes are detected. LGTM label has been removed. |
/retest |
/retest-required |
/retest |
Job Failure Risk Analysis for sha: 6339c97
|
/retest |
@chandra0007: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Hey @adambkaplan I think this is ready for your re-review. Thanks, Paul |
No description provided.