Skip to content

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

kata downstream tests #65534

wants to merge 2 commits into from

Conversation

tbuskey
Copy link

@tbuskey tbuskey commented May 30, 2025

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)

@tbuskey
Copy link
Author

tbuskey commented May 30, 2025

/hold
/assign @wainersm

@openshift-ci openshift-ci bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 30, 2025
@openshift-ci openshift-ci bot requested review from c3d and jensfr May 30, 2025 19:44
@tbuskey
Copy link
Author

tbuskey commented May 30, 2025

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@wainersm
Copy link
Contributor

wainersm commented Jun 2, 2025

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:

I0530 21:16:39.864875 575 client.go:1016] Error running /cli/oc --kubeconfig=/tmp/kubeconfig-3917880332 get configmap -n default osc-config -o json:
  Error from server (NotFound): configmaps "osc-config" not found
  I0530 21:16:39.864972 575 kata_util.go:2033] Configmap is not found: Error from server (NotFound): configmaps "osc-config" not found exit status 1

In your as workflow you will need to call sandboxed-containers-operator-env-cm step in the pre stage, and export the ENABLEPEERPODS environment variable to false, this way the osc-config will be created.

@tbuskey
Copy link
Author

tbuskey commented Jun 2, 2025

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey
Copy link
Author

tbuskey commented Jun 2, 2025

Hi @tbuskey !

Error from server (NotFound): configmaps "osc-config" not found
I0530 21:16:39.864972 575 kata_util.go:2033] Configmap is not found: Error from server (NotFound): configmaps "osc-config" not found exit status 1

Yep. That means it will use the hardcoded variables.

In your as workflow you will need to call sandboxed-containers-operator-env-cm step in the pre stage, and export the ENABLEPEERPODS environment variable to false, this way the osc-config will be created.

Let's see what this pj-rehearse does

@tbuskey
Copy link
Author

tbuskey commented Jun 2, 2025

osc/kataconfig was installed successfully
I wasn't able to manually install a pod.
This may be a OCP 4.19.0-rc.4 error

@wainersm
Copy link
Contributor

wainersm commented Jun 2, 2025

Hi @tbuskey !

Error from server (NotFound): configmaps "osc-config" not found
I0530 21:16:39.864972 575 kata_util.go:2033] Configmap is not found: Error from server (NotFound): configmaps "osc-config" not found exit status 1

Yep. That means it will use the hardcoded variables.

ah, ok, I missed that part.

In your as workflow you will need to call sandboxed-containers-operator-env-cm step in the pre stage, and export the ENABLEPEERPODS environment variable to false, this way the osc-config will be created.

Let's see what this pj-rehearse does

roger that!

@tbuskey
Copy link
Author

tbuskey commented Jun 2, 2025

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey
Copy link
Author

tbuskey commented Jun 2, 2025

/assign @wainersm
/assign @vvoronko
/assign @ldoktor

OCP 4.18 passed. This need to merge for the next step

TEST_RELEASE_TYPE: GA
TEST_SCENARIOS: kata
TEST_TIMEOUT: "50"
workflow: sandboxed-containers-operator-e2e-azure
Copy link
Contributor

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.

@wainersm
Copy link
Contributor

wainersm commented Jun 2, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2025
@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehease periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata

@wainersm
Copy link
Contributor

wainersm commented Jun 3, 2025

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 3, 2025
@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehearse abort

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@vvoronko
Copy link

vvoronko commented Jun 3, 2025

/lgtm

@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/test periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata

Copy link
Contributor

openshift-ci bot commented Jun 3, 2025

@tbuskey: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test app-ci-config-dry
/test boskos-config
/test boskos-config-generation
/test build01-dry
/test build03-dry
/test build04-dry
/test build05-dry
/test build06-dry
/test build07-dry
/test build09-dry
/test build10-dry
/test build11-dry
/test check-gh-automation
/test check-gh-automation-tide
/test ci-operator-config
/test ci-operator-config-metadata
/test ci-operator-registry
/test ci-secret-bootstrap-config-validation
/test ci-testgrid-allow-list
/test clusterimageset-validate
/test config
/test core-valid
/test generated-config
/test generated-dashboards
/test hosted-mgmt-dry
/test image-mirroring-config-validation
/test jira-lifecycle-config
/test openshift-image-mirror-mappings
/test ordered-prow-config
/test owners
/test pr-reminder-config
/test prow-config
/test prow-config-filenames
/test prow-config-semantics
/test pylint
/test release-config
/test release-controller-config
/test rover-groups-config-validation
/test secret-generator-config-valid
/test services-valid
/test stackrox-stackrox-stackrox-stackrox-check
/test step-registry-metadata
/test step-registry-shellcheck
/test sync-rover-groups
/test vsphere02-dry
/test yamllint

The following commands are available to trigger optional jobs:

/test check-cluster-profiles-config

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-release-check-gh-automation
pull-ci-openshift-release-master-ci-operator-config
pull-ci-openshift-release-master-ci-operator-config-metadata
pull-ci-openshift-release-master-ci-operator-registry
pull-ci-openshift-release-master-config
pull-ci-openshift-release-master-core-valid
pull-ci-openshift-release-master-generated-config
pull-ci-openshift-release-master-ordered-prow-config
pull-ci-openshift-release-master-owners
pull-ci-openshift-release-master-prow-config-filenames
pull-ci-openshift-release-master-prow-config-semantics
pull-ci-openshift-release-master-release-controller-config
pull-ci-openshift-release-openshift-image-mirror-mappings
pull-ci-openshift-release-yamllint

In response to this:

/test periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata

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.

@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehearse periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2025
@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/test ordered-prow-config

@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

Rebased from master

@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehearse list

@openshift-ci-robot
Copy link
Contributor

@tbuskey: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2025
@tbuskey
Copy link
Author

tbuskey commented Jun 3, 2025

/pj-rehearse list

@openshift-ci-robot
Copy link
Contributor

@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
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 3, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@tbuskey: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.18-azure-ipi-kata N/A periodic Periodic changed
periodic-ci-openshift-sandboxed-containers-operator-devel-downstream-1.9-release-4.19-azure-ipi-kata N/A periodic Periodic changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@wainersm
Copy link
Contributor

wainersm commented Jun 3, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2025
Copy link
Contributor

openshift-ci bot commented Jun 3, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants