[release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880) #413

openshift-cherrypick-robot · 2022-11-18T14:03:56Z

This is an automated cherry-pick of #411

/assign awgreene

Problem: The operator CR's status includes a list of componenets owned by the operator. The list of components are ordered by GVK, but the order of objects with the same GVK may change. If an operator owns many components, there is a high likelyhood that OLM will continuously update the status of the operator CR because the order of its components have changed, Solution: Order an operators component references so OLM does not attempt to update the status of the operator CR. Signed-off-by: Alexander Greene <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 793a7cc20d18f4907fc17ce2a0cebbca9a0f00be

openshift-ci-robot · 2022-11-18T14:04:02Z

@openshift-cherrypick-robot: Jira Issue OCPBUGS-3795 has been cloned as Jira Issue OCPBUGS-3876. Retitling PR to link against new bug.
/retitle [release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880)

In response to this:

This is an automated cherry-pick of #411

/assign awgreene

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-11-18T14:04:21Z

@openshift-cherrypick-robot: 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.

In response to this:

[release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880)

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-robot · 2022-11-18T14:04:22Z

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-3876, which is invalid:

expected dependent Jira Issue OCPBUGS-3795 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.

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 #411

/assign awgreene

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.

awgreene · 2022-11-21T15:39:20Z

/retest

ankitathomas · 2022-12-08T19:39:31Z

/jira refresh

openshift-ci-robot · 2022-12-08T19:39:38Z

@ankitathomas: This pull request references Jira Issue OCPBUGS-3876, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.11.z) matches configured target version for branch (4.11.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
dependent bug Jira Issue OCPBUGS-3795 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-3795 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

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.

ankitathomas · 2022-12-08T19:40:42Z

/retest

jianzhangbjz · 2022-12-19T03:43:13Z

Test passed, details: https://issues.redhat.com/browse/OCPBUGS-3876
/label qe-approved
/label cherry-pick-apporved
/lgtm

openshift-ci · 2022-12-19T03:43:17Z

@jianzhangbjz: The label(s) /label cherry-pick-apporved cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

Test passed, details: https://issues.redhat.com/browse/OCPBUGS-3876
/label qe-approved
/label cherry-pick-apporved
/lgtm

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.

anik120

test /e2e-gcp-olm-flaky

anik120 · 2023-01-16T15:24:05Z

/retest

anik120 · 2023-01-16T16:55:55Z

Last run failed on one flaky test:

Global Catalog Exclusion when a subscription referring to the local catalog is created when the operator group is annotated with olm.operatorframework.io/exclude-global-namespace-resolution=true [FLAKE] the broken subscription should resolve and have state AtLatest

/retest

anik120

/approve

openshift-ci · 2023-01-16T16:57:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, openshift-cherrypick-robot

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:

~~OWNERS~~ [anik120]

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

anik120 · 2023-01-16T20:19:31Z

/retest

awgreene · 2023-01-16T22:25:13Z

/retest
/label backport-risk-assessed

awgreene · 2023-01-16T22:26:22Z

@jianzhangbjz it seems like the cherry-pick label was misspelled last time you attempted to apply it, would you mind re-applying the label?

anik120 · 2023-01-17T02:48:01Z

@awgreene looks like the e2e-gcp-olm-flaky test is failing again on the same test:

Global Catalog Exclusion when a subscription referring to the local catalog is created when the operator group is annotated with olm.operatorframework.io/exclude-global-namespace-resolution=true [FLAKE] the broken subscription should resolve and have state AtLatest

Probably worth running that test locally for this branch and making sure it's not an actual test failure before we trigger CI again.

anik120 · 2023-01-17T02:48:31Z

Triggering it one last time so that it runs overnight and we have the results tomorrow morning

/test e2e-gcp-olm-flaky

awgreene · 2023-01-17T16:20:20Z

@anik120 the test passed locally:

$ make e2e/olm
/Library/Developer/CommandLineTools/usr/bin/make e2e WHAT=operator-lifecycle-manager E2E_CATALOG_NS=openshift-marketplace E2E_INSTALL_NS=openshift-operator-lifecycle-manager E2E_TEST_NS=openshift-operators E2E_TIMEOUT=120m KUBECTL=oc
scripts/e2e.sh
~/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager ~/dev/github.com/openshift/operator-framework-olm
Populating nested vendor directory
all modules verified
Running operator-lifecycle-manager e2e tests
GO111MODULE=on GOFLAGS="-mod=vendor -buildvcs=false" go run github.com/onsi/ginkgo/v2/ginkgo     -flake-attempts 1 -nodes 1 -timeout 120m -v -randomize-suites -race -trace -progress ./test/e2e  -- -namespace=openshift-operators -olmNamespace=openshift-operator-lifecycle-manager -catalogNamespace=openshift-marketplace -dummyImage=bitnami/nginx:latest -kubeconfig=/Users/agreene/Downloads/cluster-bot-2023-01-17-144614.kubeconfig.txt
Running Suite: End-to-end - /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e
======================================================================================================================================
Random Seed: 1673972311

Will run 1 of 199 specs
------------------------------
[BeforeSuite]
/Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:77
[BeforeSuite] TOP-LEVEL
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:77
------------------------------
[BeforeSuite] PASSED [0.585 seconds]
[BeforeSuite]
/Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:77

  Begin Captured GinkgoWriter Output >>
    [BeforeSuite] TOP-LEVEL
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:77
  << End Captured GinkgoWriter Output
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
Global Catalog Exclusion when a subscription referring to the local catalog is created when the operator group is annotated with olm.operatorframework.io/exclude-global-namespace-resolution=true
  the broken subscription should resolve and have state AtLatest
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:111
[BeforeEach] Global Catalog Exclusion
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:31
STEP: creating a namespace with an own namespace operator group without annotations 01/17/23 08:18:49.031
created the global-catalog-exclusion-e2e-5fpw7 testing namespace
STEP: creating a broken catalog in the global namespace 01/17/23 08:18:49.116
STEP: creating a healthy catalog in the test namespace 01/17/23 08:18:49.181
STEP: checking that the global catalog is broken 01/17/23 08:19:05.364
expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
expecting catalog source last connection state 'TRANSIENT_FAILURE' to be 'TRANSIENT_FAILURE'
[BeforeEach] when a subscription referring to the local catalog is created
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:89
STEP: creating a subscription 01/17/23 08:19:09.539
[It] the broken subscription should resolve and have state AtLatest
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:111
STEP: checking that the subscription is not resolving and has a condition with type ResolutionFailed 01/17/23 08:19:09.612
expecting subscription condition type 'ResolutionFailed' to be in [CatalogSourcesUnhealthy]
expecting subscription condition type 'ResolutionFailed' to be in [CatalogSourcesUnhealthy ResolutionFailed]
STEP: annotating the operator group with olm.operatorframework.io/exclude-global-namespace-resolution=true 01/17/23 08:19:10.691
STEP: checking that the subscription resolves and has state AtLatest 01/17/23 08:19:10.77
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state '' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
expecting subscription state 'AtLatestKnown' to be 'AtLatestKnown'
[AfterEach] Global Catalog Exclusion
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:82
tearing down the global-catalog-exclusion-e2e-5fpw7 namespace
resetting e2e kube client
deleting global-catalog-exclusion-e2e-5fpw7/local-subscription-j2nbp
deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf
deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-svc
deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-pod
deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-configmap
deleting openshift-marketplace/bad-global-catalog-bw6ms
deleting global-catalog-exclusion-e2e-5fpw7/og-x72zq
deleting <global>/global-catalog-exclusion-e2e-5fpw7
garbage collecting CRDs
------------------------------
• [SLOW TEST] [56.398 seconds]
Global Catalog Exclusion
/Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:23
  when a subscription referring to the local catalog is created
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:86
    when the operator group is annotated with olm.operatorframework.io/exclude-global-namespace-resolution=true
    /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:108
      the broken subscription should resolve and have state AtLatest
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:111

  Begin Captured GinkgoWriter Output >>
    [BeforeEach] Global Catalog Exclusion
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:31
    STEP: creating a namespace with an own namespace operator group without annotations 01/17/23 08:18:49.031
    created the global-catalog-exclusion-e2e-5fpw7 testing namespace
    STEP: creating a broken catalog in the global namespace 01/17/23 08:18:49.116
    STEP: creating a healthy catalog in the test namespace 01/17/23 08:18:49.181
    STEP: checking that the global catalog is broken 01/17/23 08:19:05.364
    expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
    expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
    expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
    expecting catalog source last connection state 'CONNECTING' to be 'TRANSIENT_FAILURE'
    expecting catalog source last connection state 'TRANSIENT_FAILURE' to be 'TRANSIENT_FAILURE'
    [BeforeEach] when a subscription referring to the local catalog is created
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:89
    STEP: creating a subscription 01/17/23 08:19:09.539
    [It] the broken subscription should resolve and have state AtLatest
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:111
    STEP: checking that the subscription is not resolving and has a condition with type ResolutionFailed 01/17/23 08:19:09.612
    expecting subscription condition type 'ResolutionFailed' to be in [CatalogSourcesUnhealthy]
    expecting subscription condition type 'ResolutionFailed' to be in [CatalogSourcesUnhealthy ResolutionFailed]
    STEP: annotating the operator group with olm.operatorframework.io/exclude-global-namespace-resolution=true 01/17/23 08:19:10.691
    STEP: checking that the subscription resolves and has state AtLatest 01/17/23 08:19:10.77
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state '' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'UpgradePending' to be 'AtLatestKnown'
    expecting subscription state 'AtLatestKnown' to be 'AtLatestKnown'
    [AfterEach] Global Catalog Exclusion
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/catalog_exclusion_test.go:82
    tearing down the global-catalog-exclusion-e2e-5fpw7 namespace
    resetting e2e kube client
    deleting global-catalog-exclusion-e2e-5fpw7/local-subscription-j2nbp
    deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf
    deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-svc
    deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-pod
    deleting global-catalog-exclusion-e2e-5fpw7/good-catsrc-72mrf-configmap
    deleting openshift-marketplace/bad-global-catalog-bw6ms
    deleting global-catalog-exclusion-e2e-5fpw7/og-x72zq
    deleting <global>/global-catalog-exclusion-e2e-5fpw7
    garbage collecting CRDs
  << End Captured GinkgoWriter Output
------------------------------
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS
------------------------------
[AfterSuite]
/Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:123
[AfterSuite] TOP-LEVEL
  /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:123
------------------------------
[AfterSuite] PASSED [0.000 seconds]
[AfterSuite]
/Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:123

  Begin Captured GinkgoWriter Output >>
    [AfterSuite] TOP-LEVEL
      /Users/agreene/dev/github.com/openshift/operator-framework-olm/staging/operator-lifecycle-manager/test/e2e/e2e_test.go:123
  << End Captured GinkgoWriter Output
------------------------------

Ran 1 of 199 Specs in 57.002 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 198 Skipped
PASS | FOCUSED

awgreene · 2023-01-17T16:22:16Z

For what it's worth, there's a comment calling out that this test typically fails in OpenShift CI, likely due to resource constraints:

// Note: this test flakes on openshift CI but passes running on a local openshift cluster
// For some reason, the subscription does not transition to a failed state in time

awgreene · 2023-01-17T16:23:07Z

/override ci/prow/e2e-gcp-olm-flaky

openshift-ci · 2023-01-17T16:23:49Z

@awgreene: Overrode contexts on behalf of awgreene: ci/prow/e2e-gcp-olm-flaky

In response to this:

/override ci/prow/e2e-gcp-olm-flaky

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.

jianzhangbjz · 2023-01-18T00:55:36Z

/label cherry-pick-approved

jianzhangbjz · 2023-01-18T01:45:23Z

/override ci/prow/e2e-gcp-olm-flaky

openshift-ci · 2023-01-18T01:45:35Z

@jianzhangbjz: jianzhangbjz unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight.

In response to this:

/override ci/prow/e2e-gcp-olm-flaky

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-robot · 2023-01-18T02:31:57Z

/retest-required

Remaining retests: 0 against base HEAD cb6810a and 2 for PR HEAD 05c3a52 in total

openshift-ci · 2023-01-18T05:14:16Z

@openshift-cherrypick-robot: all tests passed!

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

openshift-ci-robot · 2023-01-18T05:20:27Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#413

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

In response to this:

This is an automated cherry-pick of #411

/assign awgreene

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.

awgreene · 2023-01-23T14:52:48Z

/cherry-pick release-4.10

openshift-cherrypick-robot · 2023-01-23T14:53:38Z

@awgreene: new pull request created: #432

In response to this:

/cherry-pick release-4.10

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.

) Bumps [sigs.k8s.io/controller-runtime](https://github.com/kubernetes-sigs/controller-runtime) from 0.20.2 to 0.20.3. - [Release notes](https://github.com/kubernetes-sigs/controller-runtime/releases) - [Changelog](https://github.com/kubernetes-sigs/controller-runtime/blob/main/RELEASE.md) - [Commits](kubernetes-sigs/controller-runtime@v0.20.2...v0.20.3) --- updated-dependencies: - dependency-name: sigs.k8s.io/controller-runtime dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Upstream-repository: api Upstream-commit: 78ed98e0418e012aeca253f985898d659d62defc

openshift-cherrypick-robot mentioned this pull request Nov 18, 2022

[release-4.12] OCPBUGS-3795: Order an operator CR's status.Component.Refs array (#2880) #411

Merged

openshift-ci bot assigned awgreene Nov 18, 2022

openshift-ci bot changed the title ~~[release-4.11] OCPBUGS-3795: Order an operator CR's status.Component.Refs array (#2880)~~ [release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880) Nov 18, 2022

openshift-ci-robot added the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Nov 18, 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 Nov 18, 2022

openshift-ci bot requested review from ankitathomas and benluddy November 18, 2022 14:04

openshift-ci bot requested a review from jianzhangbjz December 8, 2022 19:39

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Dec 19, 2022

openshift-ci bot assigned jianzhangbjz Dec 19, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 19, 2022

anik120 reviewed Jan 16, 2023

View reviewed changes

anik120 approved these changes Jan 16, 2023

View reviewed changes

openshift-ci bot assigned anik120 Jan 16, 2023

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 16, 2023

openshift-ci bot assigned bandrade, kuiwang02 and Xia-Zhao-rh Jan 16, 2023

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 18, 2023

openshift-merge-robot merged commit 7fdc3c5 into openshift:release-4.11 Jan 18, 2023

openshift-cherrypick-robot mentioned this pull request Jan 23, 2023

[release-4.10] OCPBUGS-6498: Order an operator CR's status.Component.Refs array (#2880) #432

Merged

tmshort mentioned this pull request Apr 30, 2025

OCPBUGS-53161, OPRUN-3880:Synchronize From Upstream Repositories #996

Merged

[release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880) #413

[release-4.11] OCPBUGS-3876: Order an operator CR's status.Component.Refs array (#2880) #413

Uh oh!

Conversation

openshift-cherrypick-robot commented Nov 18, 2022

Uh oh!

openshift-ci-robot commented Nov 18, 2022

Uh oh!

openshift-ci bot commented Nov 18, 2022

Uh oh!

openshift-ci-robot commented Nov 18, 2022

Uh oh!

awgreene commented Nov 21, 2022

Uh oh!

ankitathomas commented Dec 8, 2022

Uh oh!

openshift-ci-robot commented Dec 8, 2022

Uh oh!

ankitathomas commented Dec 8, 2022

Uh oh!

jianzhangbjz commented Dec 19, 2022

Uh oh!

openshift-ci bot commented Dec 19, 2022

Uh oh!

anik120 left a comment

Choose a reason for hiding this comment

Uh oh!

anik120 commented Jan 16, 2023

Uh oh!

anik120 commented Jan 16, 2023

Uh oh!

anik120 left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Jan 16, 2023

Uh oh!

anik120 commented Jan 16, 2023

Uh oh!

awgreene commented Jan 16, 2023

Uh oh!

awgreene commented Jan 16, 2023

Uh oh!

anik120 commented Jan 17, 2023

Uh oh!

anik120 commented Jan 17, 2023

Uh oh!

awgreene commented Jan 17, 2023

Uh oh!

awgreene commented Jan 17, 2023

Uh oh!

awgreene commented Jan 17, 2023

Uh oh!

openshift-ci bot commented Jan 17, 2023

Uh oh!

jianzhangbjz commented Jan 18, 2023

Uh oh!

jianzhangbjz commented Jan 18, 2023

Uh oh!

openshift-ci bot commented Jan 18, 2023

Uh oh!

openshift-ci-robot commented Jan 18, 2023

Uh oh!

openshift-ci bot commented Jan 18, 2023

Uh oh!

openshift-ci-robot commented Jan 18, 2023

Uh oh!

awgreene commented Jan 23, 2023

Uh oh!

openshift-cherrypick-robot commented Jan 23, 2023

Uh oh!

Uh oh!