openshift
WIP: OCPBUGS-18865: disruption tests
- Reapply "Merge pull request #28944 from vrutkovs/in-cluster-fixes-v4"
- disruption: don't create junits for disruptions when loadbalancer is localhost
- disruption: specify deployment id for unique log names
- disruption: mv int-lb and svc-net test to workers
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: sanchezl Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
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}
@sanchezl: This pull request references Jira Issue OCPBUGS-18865, which is invalid:
- expected the bug to target either version "4.18." or "openshift-4.18.", but it targets "4.17.0" 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.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
- Reapply "Merge pull request #28944 from vrutkovs/in-cluster-fixes-v4"
- disruption: don't create junits for disruptions when loadbalancer is localhost
- disruption: specify deployment id for unique log names
- disruption: mv int-lb and svc-net test to workers
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.
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade
@sanchezl: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade 10
@sanchezl: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/882aead0-5a8c-11ef-8da5-419ea6b6a7b4-0
@sanchezl: This pull request references Jira Issue OCPBUGS-18865, which is valid.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.18.0) matches configured target version for branch (4.18.0)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
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.
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade 10
@vrutkovs: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5b7d8ea0-5acf-11ef-92ce-9e24e3de73cc-0
/payload-aggregate periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade 10
@sanchezl: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
- periodic-ci-openshift-release-master-ci-4.17-e2e-azure-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b8d75bd0-5b1f-11ef-9e8a-cb1800763bba-0
Job Failure Risk Analysis for sha: 1cb355f07aa9783e81bdfa350ffa198490eb5038
| Job Name | Failure Risk |
|---|---|
| pull-ci-openshift-origin-master-e2e-aws-ovn-serial | High [bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above info This test has passed 100.00% of 35 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days. |
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
PR needs rebase.
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.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
@sanchezl: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-gcp-ovn-builds | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-gcp-ovn-builds |
| ci/prow/e2e-aws-ovn-edge-zones | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-aws-ovn-edge-zones |
| ci/prow/e2e-gcp-ovn-upgrade | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-gcp-ovn-upgrade |
| ci/prow/verify | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test verify |
| ci/prow/unit | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test unit |
| ci/prow/verify-deps | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test verify-deps |
| ci/prow/images | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test images |
| ci/prow/e2e-aws-ovn-microshift-serial | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-aws-ovn-microshift-serial |
| ci/prow/e2e-gcp-ovn | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-gcp-ovn |
| ci/prow/e2e-metal-ipi-ovn-ipv6 | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-metal-ipi-ovn-ipv6 |
| ci/prow/e2e-aws-ovn-fips | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-aws-ovn-fips |
| ci/prow/e2e-vsphere-ovn-upi | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-vsphere-ovn-upi |
| ci/prow/e2e-aws-ovn-serial | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-aws-ovn-serial |
| ci/prow/okd-scos-images | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test okd-scos-images |
| ci/prow/e2e-vsphere-ovn | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-vsphere-ovn |
| ci/prow/e2e-aws-ovn-microshift | 1cb355f07aa9783e81bdfa350ffa198490eb5038 | link | true | /test e2e-aws-ovn-microshift |
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.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@sanchezl: This pull request references Jira Issue OCPBUGS-18865. The bug has been updated to no longer refer to the pull request using the external bug tracker.
In response to this:
- Reapply "Merge pull request #28944 from vrutkovs/in-cluster-fixes-v4"
- disruption: don't create junits for disruptions when loadbalancer is localhost
- disruption: specify deployment id for unique log names
- disruption: mv int-lb and svc-net test to workers
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-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.