origin
origin copied to clipboard
openshift
[release-4.17] OCPEDGE-1294: removing rteval from the realtime test suite
This is an automated cherry-pick of #29164
/assign jeff-roche
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPEDGE-1265
In response to this:
This is an automated cherry-pick of #29164
/assign jeff-roche
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.
@openshift-cherrypick-robot: This pull request references OCPEDGE-1294 which is a valid jira issue.
In response to this:
This is an automated cherry-pick of #29164
/assign jeff-roche
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.
We are removing rteval from the realtime test suite. After switching to a metal host it was exposed that this test overruns container limits when creating system load and the only logical fix is to run rteval on the host rather than containerized. That approach is beyond the scope of what this test suite is intended for. In addition, this test is primarily useful when testing hardware being used in production systems to provide platform readiness by putting the CPU under load and then evaluating with cyclictest. We are not validating the hardware with this test suite and as such rteval is a bad fit for this suite.
In our situation we are really trying to just test that there are no obvious underlying issues with the kernel or with Openshift running on top of the real-time kernel which is exposed by just running cyclictest (which we do separately of rteval).
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: eggfoobar, neisw, openshift-cherrypick-robot
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~test/extended/kernel/OWNERS~~ [eggfoobar,neisw]
- ~~test/extended/util/annotate/generated/OWNERS~~ [neisw]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
/retitle [release-4.17] OCPBUGS-44494: removing rteval from the realtime test suite
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-44494, which is invalid:
- release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
- expected Jira Issue OCPBUGS-44494 to depend on a bug targeting a version in 4.18.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #29164
/assign jeff-roche
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.
@jeff-roche: This pull request references Jira Issue OCPBUGS-44494, which is invalid:
- dependent bug OCPEDGE-1265 is not in the required
OCPBUGSproject
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@jeff-roche: This pull request references Jira Issue OCPBUGS-44494, which is invalid:
- expected dependent Jira Issue OCPBUGS-44495 to target a version in 4.18.0, but it targets "4.18" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@jeff-roche: This pull request references Jira Issue OCPBUGS-44494, which is valid.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.17.z) matches configured target version for branch (4.17.z)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-44495 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-44495 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
- bug has dependents
In response to this:
/jira refresh
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.
/retest-required
Remaining retests: 0 against base HEAD b231f7618836468e5006239cdb71cc290c579472 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b231f7618836468e5006239cdb71cc290c579472 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 1 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total
@jeff-roche: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:
/test e2e-aws-jenkins/test e2e-aws-ovn-edge-zones/test e2e-aws-ovn-fips/test e2e-aws-ovn-image-registry/test e2e-aws-ovn-serial/test e2e-gcp-ovn/test e2e-gcp-ovn-builds/test e2e-gcp-ovn-image-ecosystem/test e2e-gcp-ovn-upgrade/test e2e-metal-ipi-ovn-ipv6/test images/test lint/test unit/test verify/test verify-deps
The following commands are available to trigger optional jobs:
/test e2e-agnostic-ovn-cmd/test e2e-aws/test e2e-aws-csi/test e2e-aws-disruptive/test e2e-aws-etcd-certrotation/test e2e-aws-etcd-recovery/test e2e-aws-ovn/test e2e-aws-ovn-cgroupsv2/test e2e-aws-ovn-etcd-scaling/test e2e-aws-ovn-ipsec-serial/test e2e-aws-ovn-kube-apiserver-rollout/test e2e-aws-ovn-kubevirt/test e2e-aws-ovn-single-node/test e2e-aws-ovn-single-node-serial/test e2e-aws-ovn-single-node-techpreview/test e2e-aws-ovn-single-node-techpreview-serial/test e2e-aws-ovn-single-node-upgrade/test e2e-aws-ovn-upgrade/test e2e-aws-ovn-upi/test e2e-aws-ovn-virt-techpreview/test e2e-aws-proxy/test e2e-azure/test e2e-azure-ovn-etcd-scaling/test e2e-azure-ovn-upgrade/test e2e-baremetalds-kubevirt/test e2e-external-aws/test e2e-external-aws-ccm/test e2e-gcp-csi/test e2e-gcp-disruptive/test e2e-gcp-fips-serial/test e2e-gcp-ovn-etcd-scaling/test e2e-gcp-ovn-rt-upgrade/test e2e-gcp-ovn-techpreview/test e2e-gcp-ovn-techpreview-serial/test e2e-metal-ipi-ovn/test e2e-metal-ipi-ovn-dualstack/test e2e-metal-ipi-ovn-dualstack-local-gateway/test e2e-metal-ipi-ovn-kube-apiserver-rollout/test e2e-metal-ipi-serial/test e2e-metal-ipi-serial-ovn-ipv6/test e2e-metal-ipi-virtualmedia/test e2e-openstack-ovn/test e2e-openstack-serial/test e2e-vsphere/test e2e-vsphere-ovn-dualstack-primaryv6/test e2e-vsphere-ovn-etcd-scaling/test okd-scos-images
Use /test all to run the following jobs that were automatically triggered:
pull-ci-openshift-origin-release-4.17-e2e-agnostic-ovn-cmdpull-ci-openshift-origin-release-4.17-e2e-aws-csipull-ci-openshift-origin-release-4.17-e2e-aws-ovn-cgroupsv2pull-ci-openshift-origin-release-4.17-e2e-aws-ovn-edge-zonespull-ci-openshift-origin-release-4.17-e2e-aws-ovn-fipspull-ci-openshift-origin-release-4.17-e2e-aws-ovn-kube-apiserver-rolloutpull-ci-openshift-origin-release-4.17-e2e-aws-ovn-serialpull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-nodepull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-node-serialpull-ci-openshift-origin-release-4.17-e2e-aws-ovn-single-node-upgradepull-ci-openshift-origin-release-4.17-e2e-aws-ovn-upgradepull-ci-openshift-origin-release-4.17-e2e-azure-ovn-upgradepull-ci-openshift-origin-release-4.17-e2e-gcp-csipull-ci-openshift-origin-release-4.17-e2e-gcp-ovnpull-ci-openshift-origin-release-4.17-e2e-gcp-ovn-buildspull-ci-openshift-origin-release-4.17-e2e-gcp-ovn-rt-upgradepull-ci-openshift-origin-release-4.17-e2e-gcp-ovn-upgradepull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovnpull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-dualstack-local-gatewaypull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-ipv6pull-ci-openshift-origin-release-4.17-e2e-metal-ipi-ovn-kube-apiserver-rolloutpull-ci-openshift-origin-release-4.17-e2e-openstack-ovnpull-ci-openshift-origin-release-4.17-e2e-vsphere-ovn-dualstack-primaryv6pull-ci-openshift-origin-release-4.17-imagespull-ci-openshift-origin-release-4.17-lintpull-ci-openshift-origin-release-4.17-unitpull-ci-openshift-origin-release-4.17-verifypull-ci-openshift-origin-release-4.17-verify-deps
In response to this:
/retest required
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.
/retest-required
Remaining retests: 0 against base HEAD b295795127041873c4d6f1cc5951ae4a6b546f64 and 2 for PR HEAD ba26023aa107971daf059a598f5735c4505a93cf in total