openshift
[release-4.18] OCPBUGS-45548: reenable OLMv1 test for maxOpenShiftversion
This is an automated cherry-pick of #29328
/assign gallettilance
@openshift-cherrypick-robot: Jira Issue OCPBUGS-44808 has been cloned as Jira Issue OCPBUGS-45548. Will retitle bug to link to clone. /retitle [release-4.18] OCPBUGS-45548: reenable OLMv1 test for maxOpenShiftversion
In response to this:
This is an automated cherry-pick of #29328
/assign gallettilance
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 Jira Issue OCPBUGS-45548, 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.
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 #29328
/assign gallettilance
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: joelanford, 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/olm/OWNERS~~ [joelanford]
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}
@gallettilance: This pull request references Jira Issue OCPBUGS-45548, which is invalid:
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
- 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.
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.
@gallettilance: This pull request references Jira Issue OCPBUGS-45548, which is valid.
7 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)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-44808 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
- dependent Jira Issue OCPBUGS-44808 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
- bug has dependents
Requesting review from QA contact: /cc @Xia-Zhao-rh
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 f5a460e98df6ae0f232754ee7d1e2aea92e020d1 and 2 for PR HEAD eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 in total
/retest-required
Remaining retests: 0 against base HEAD f5a460e98df6ae0f232754ee7d1e2aea92e020d1 and 2 for PR HEAD eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 in total
/retest-required
Remaining retests: 0 against base HEAD c00c0867ee2fe6a05e75cbc55038d93611a1e657 and 1 for PR HEAD eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 in total
/retest-required
Remaining retests: 0 against base HEAD 43d6e7aed243d19c42dddec5fe44dce65ef0b917 and 0 for PR HEAD eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 in total
@openshift-cherrypick-robot: 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/okd-scos-e2e-aws-ovn | eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 | link | false | /test okd-scos-e2e-aws-ovn |
| ci/prow/e2e-aws-ovn-edge-zones | eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 | link | true | /test e2e-aws-ovn-edge-zones |
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.
/hold
Revision eb958f8e5cde78bd60bf951a42479a9f9bd2ff76 was retested 3 times: holding
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
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
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
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-45548. The bug has been updated to no longer refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #29328
/assign gallettilance
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.