OCPBUGS-2898: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817) by timflannagan · Pull Request #389 · openshift/operator-framework-olm

timflannagan · 2022-09-20T22:03:42Z

Get the current OpenShift release version from the RELEASE_VERSION environment variable since the behavior of the original source -- the ClusterVersion desired release status field -- has changed.

Signed-off-by: Tyler Slaton tyslaton@redhat.com
Co-authored-by: Nick Hale njohnhale@gmail.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: ec9903dba891dc5fd4e42bd06b240a7a82f9283c

Get the current OpenShift release version from the RELEASE_VERSION environment variable since the behavior of the original source -- the ClusterVersion desired release status field -- has changed. Signed-off-by: Tyler Slaton <tyslaton@redhat.com> Co-authored-by: Nick Hale <njohnhale@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: ec9903dba891dc5fd4e42bd06b240a7a82f9283c

openshift-ci · 2022-09-20T22:03:46Z

@timflannagan: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)

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/test-infra repository.

openshift-ci · 2022-09-20T22:04:22Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

~~OWNERS~~ [timflannagan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

timflannagan · 2022-09-20T22:04:58Z

Manually opening a backport to 4.10 after the cherry pick operation in #347 failed. It's unclear whether this will solve https://issues.redhat.com/browse/OCPBUGS-1543 or whether that's a duplicate of the existing 4.11.z that's been verified.

tylerslaton · 2022-09-21T14:02:15Z

/lgtm

perdasilva · 2022-09-22T07:24:09Z

/retest

tylerslaton · 2022-09-23T13:43:05Z

/retest

tylerslaton · 2022-09-26T13:52:53Z

/retest

timflannagan · 2022-10-09T21:11:35Z

/test all

oceanc80 · 2022-10-26T21:03:58Z

/retitle Bug 2097557: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)

openshift-ci · 2022-10-26T21:04:09Z

@timflannagan: This pull request references Bugzilla bug 2097557, which is invalid:

expected the bug to target the "4.10.z" release, but it targets "4.12.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, but it is VERIFIED instead
expected Bugzilla bug 2097557 to depend on a bug targeting a release in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 2097557: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)

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/test-infra repository.

oceanc80 · 2022-10-26T21:12:11Z

/retitle OCPBUGS-2898: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)

openshift-ci-robot · 2022-10-26T21:12:16Z

@timflannagan: This pull request references Jira Issue OCPBUGS-2898, which is invalid:

expected the bug to target the "4.10.z" version, but no target version was set
expected Jira Issue OCPBUGS-2898 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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.

Details

In response to this:

Get the current OpenShift release version from the RELEASE_VERSION environment variable since the behavior of the original source -- the ClusterVersion desired release status field -- has changed.

Signed-off-by: Tyler Slaton tyslaton@redhat.com
Co-authored-by: Nick Hale njohnhale@gmail.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: ec9903dba891dc5fd4e42bd06b240a7a82f9283c

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/test-infra repository.

openshift-ci · 2022-10-26T21:12:17Z

@timflannagan: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

OCPBUGS-2898: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)

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/test-infra repository.

oceanc80 · 2022-10-26T21:28:40Z

/jira refresh

openshift-ci-robot · 2022-10-26T21:28:43Z

@oceanc80: This pull request references Jira Issue OCPBUGS-2898, which is invalid:

expected dependent Jira Issue OCPBUGS-2900 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA 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.

Details

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 kubernetes/test-infra repository.

kuiwang02 · 2022-10-27T02:24:37Z

/jira refresh

openshift-ci-robot · 2022-10-27T02:24:51Z

@kuiwang02: This pull request references Jira Issue OCPBUGS-2898, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.10.z) matches configured target version for branch (4.10.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
dependent bug Jira Issue OCPBUGS-2900 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
dependent Jira Issue OCPBUGS-2900 targets the "4.11.z" version, which is one of the valid target versions: 4.11.0, 4.11.z
bug has dependents

Requesting review from QA contact:
/cc @kuiwang02

Details

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 kubernetes/test-infra repository.

kuiwang02 · 2022-10-27T03:26:16Z

/label qe-approved
/label cherry-pick-approved

awgreene · 2022-10-27T15:06:55Z

/label backport-risk-assessed

oceanc80 · 2022-10-27T15:45:07Z

/retest-required

oceanc80 · 2022-10-28T17:00:04Z

/retest-required

perdasilva · 2022-11-14T08:53:43Z

/retest

openshift-ci · 2022-11-14T11:11:54Z

@timflannagan: The following test 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-aws-olm	`4f8a9c9`	link	true	`/test e2e-aws-olm`

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.

oceanc80 · 2022-11-16T15:53:02Z

/retest-required

openshift-ci-robot · 2022-11-16T20:01:49Z

@timflannagan: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#389

Jira Issue OCPBUGS-2898 has been moved to the MODIFIED state.

Details

In response to this:

Get the current OpenShift release version from the RELEASE_VERSION environment variable since the behavior of the original source -- the ClusterVersion desired release status field -- has changed.

Signed-off-by: Tyler Slaton tyslaton@redhat.com
Co-authored-by: Nick Hale njohnhale@gmail.com
Upstream-repository: operator-lifecycle-manager
Upstream-commit: ec9903dba891dc5fd4e42bd06b240a7a82f9283c

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/test-infra repository.

openshift-ci Bot requested review from anik120 and kevinrizza September 20, 2022 22:04

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 20, 2022

openshift-ci Bot assigned tylerslaton Sep 21, 2022

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 21, 2022

openshift-ci Bot changed the title ~~[release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)~~ Bug 2097557: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817) Oct 26, 2022

openshift-ci Bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Oct 26, 2022

openshift-ci Bot changed the title ~~Bug 2097557: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817)~~ OCPBUGS-2898: [release-4.10] fix(openshift): use env var instead of clusterversion status (#2817) Oct 26, 2022

openshift-ci Bot removed the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Oct 26, 2022

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Oct 26, 2022

openshift-ci Bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Oct 26, 2022

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 27, 2022

openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 27, 2022

openshift-ci Bot requested a review from kuiwang02 October 27, 2022 02:24

openshift-ci Bot added qe-approved Signifies that QE has signed off on this PR cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Oct 27, 2022

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 27, 2022

openshift-merge-robot merged commit 7837ef2 into openshift:release-4.10 Nov 16, 2022

Conversation

timflannagan commented Sep 20, 2022

Uh oh!

openshift-ci Bot commented Sep 20, 2022

Uh oh!

openshift-ci Bot commented Sep 20, 2022

Uh oh!

timflannagan commented Sep 20, 2022

Uh oh!

tylerslaton commented Sep 21, 2022

Uh oh!

perdasilva commented Sep 22, 2022

Uh oh!

tylerslaton commented Sep 23, 2022

Uh oh!

tylerslaton commented Sep 26, 2022

Uh oh!

timflannagan commented Oct 9, 2022

Uh oh!

oceanc80 commented Oct 26, 2022

Uh oh!

openshift-ci Bot commented Oct 26, 2022

Uh oh!

oceanc80 commented Oct 26, 2022

Uh oh!

openshift-ci-robot commented Oct 26, 2022

Uh oh!

openshift-ci Bot commented Oct 26, 2022

Uh oh!

oceanc80 commented Oct 26, 2022

Uh oh!

openshift-ci-robot commented Oct 26, 2022

Uh oh!

kuiwang02 commented Oct 27, 2022

Uh oh!

openshift-ci-robot commented Oct 27, 2022

Uh oh!

kuiwang02 commented Oct 27, 2022

Uh oh!

awgreene commented Oct 27, 2022

Uh oh!

oceanc80 commented Oct 27, 2022

Uh oh!

oceanc80 commented Oct 28, 2022

Uh oh!

perdasilva commented Nov 14, 2022

Uh oh!

openshift-ci Bot commented Nov 14, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

oceanc80 commented Nov 16, 2022

Uh oh!

openshift-ci-robot commented Nov 16, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

openshift-ci Bot commented Nov 14, 2022 •

edited

Loading