-
Notifications
You must be signed in to change notification settings - Fork 1.9k
kata downstream tests #65534
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
base: master
Are you sure you want to change the base?
kata downstream tests #65534
Conversation
/hold |
/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Hi @tbuskey ! The periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata is marked as passed but "OSC-00102:abhbaner:Kata:[sig-kata] Kata High-deploy & delete a pod with kata runtime". The reason being that I did not find the osc-config configmap:
In your |
/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Yep. That means it will use the hardcoded variables.
Let's see what this pj-rehearse does |
osc/kataconfig was installed successfully |
ah, ok, I missed that part.
roger that! |
/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
TEST_RELEASE_TYPE: GA | ||
TEST_SCENARIOS: kata | ||
TEST_TIMEOUT: "50" | ||
workflow: sandboxed-containers-operator-e2e-azure |
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.
I'm okay to replace this sandboxed-containers-operator-e2e-azure entirely for now, but I would like to start incorporating your stuffs in it. I will send a separated PR to make use of steps like ipi-conf-azure
in sandboxed-containers-operator-e2e-azure
.
/lgtm |
/pj-rehease periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata |
/unhold |
/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse abort |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/lgtm |
/test periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata |
@tbuskey: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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 kubernetes-sigs/prow repository. |
/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
...ers-operator/openshift-sandboxed-containers-operator-devel__downstream-1.9-release-4.19.yaml
Outdated
Show resolved
Hide resolved
...ers-operator/openshift-sandboxed-containers-operator-devel__downstream-1.9-release-4.19.yaml
Show resolved
Hide resolved
...ers-operator/openshift-sandboxed-containers-operator-devel__downstream-1.9-release-4.19.yaml
Show resolved
Hide resolved
...ers-operator/openshift-sandboxed-containers-operator-devel__downstream-1.9-release-4.18.yaml
Show resolved
Hide resolved
/test ordered-prow-config |
Rebased from master |
/pj-rehearse list |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse list |
@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Install a cluster on Azure then run just the C00102 test from openshift-test-private This will subscribe to osc, create kataconfig with the defaults and then run a pod under kata https://issues.redhat.com/browse/KATA-3809 Add base_images tests-private - openshift-tests-private. Kata always uses the master branch. That isn't an option, so we use the newest 4.x branch that corresponds to master pre: Install azure cluster w/ QE profile/credentials 2 worker notes w/o spot nodes (ipi-conf-azure, azure-provision-service..., ipi-install, ipi-azure-rbac) eastus region (ipi-conf-azure-custom-region) test: (openshift-extended-test) TEST_SCENARIO - Run just the C00102 test TEST_FILTER Skip tests post: pause for 2 hrs after test finishes (cucushift-installer-wait) tear cluster down (ipi-azure-post) make update before submitting PR
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tbuskey, vvoronko, wainersm 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 |
KATA-3809
Add base_images
tests-private - openshift-tests-private. Want master which is 4.newest
tests:
azure-ipi-kata
pre:
install azure cluster w/ QE profile/credentials
2 worker notes w/o spot nodes (ipi-conf-azure,
azure-provision-service..., ipi-install, ipi-azure-rbac) eastus region (ipi-conf-azure-custom-region)
test: (openshift-extended-test)
TEST_SCENARIO - Run kata tests
TEST_FILTER
~& == don't run.
The rest must run. C00102 installs OSC w/ kata and runs 1 workload
post:
pause for 2 hrs after test finishes (cucushift-installer-wait) tear cluster down (ipi-azure-post)