-
Notifications
You must be signed in to change notification settings - Fork 38
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
Enable Fedora 38 support to OAI test case #260
base: main
Are you sure you want to change the base?
Conversation
167c9b8
to
8e6dbbb
Compare
/approve |
/retest |
Signed-off-by: Victor Morales <[email protected]>
8e6dbbb
to
9613c51
Compare
/retest |
@electrocucaracha Thank you for this MR. Though is there any specific reason to choose Fedora 38? We can use 39, right? |
|
There is |
@electrocucaracha Should we merge this MR as it is once the test passes? |
Let me give it another try /test e2e-oai-fedora-38 |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liamfallon, radoslawc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test e2e-oai-fedora-38 |
1 similar comment
/test e2e-oai-fedora-38 |
@electrocucaracha: The following test failed, say
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/test-infra repository. I understand the commands that are listed here. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Until now, the creation of the sandbox has been tested with three OS releases, used for testing four different scenarios. This change offers the option to validate the Sandbox creation with fedora38, covering OAI test case.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: