OCPBUGS-23538,OCPBUGS-25448,OCPBUGS-24526: Synchronize From Upstream Repositories #627
Conversation
openshift-bot
added
approved
openshift-ci-robot
added
the
jira/valid-reference
|
@openshift-bot: This pull request explicitly references no jira issue. In response to this:
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-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-ecosystem. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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-bot
force-pushed
the
synchronize-upstream
branch
from
086d18a
to
e19edb1
Compare
|
@openshift-bot: This pull request explicitly references no jira issue. In response to this:
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. |
|
/retest |
openshift-bot
force-pushed
the
synchronize-upstream
branch
from
e19edb1
to
ce7fda1
Compare
|
@openshift-bot: This pull request explicitly references no jira issue. In response to this:
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. |
|
/retest |
|
Failed with more flaky tests. |
|
/retitle OCPBUGS-24526: Synchronize From Upstream Repositories |
openshift-ci
bot
changed the title
openshift-ci-robot
added
jira/severity-moderate
|
@openshift-bot: This pull request references Jira Issue OCPBUGS-24526, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
|
/jira refresh |
openshift-ci-robot
added
the
jira/valid-bug
|
@dtfranz: This pull request references Jira Issue OCPBUGS-24526, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
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
removed
the
jira/invalid-bug
openshift-bot
changed the title
…ead of the CatalogSource Namespace. Signed-off-by: Daniel Franz <dfranz@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: d70de0797c1604cb2b6d6aa043e1e7731fc830e3
Our controllers must not share runtime with controllers of previous versions, as we expect that the set of actors on the cluster to be coherent with respect to what they're trying to do. RollingUpdate strategies do not guarantee this and lead to cases where previous versions of the operators issue spurious mutating calls that the current operator needs to un-do. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: cee062283539d08f25333bfa53b2963725e35914
openshift-bot
force-pushed
the
synchronize-upstream
branch
from
b07e798
to
62087f0
Compare
|
LGTM for https://issues.redhat.com/browse/OCPBUGS-25448 |
openshift-ci
bot
added
the
qe-approved
|
/retest |
|
@openshift-bot: The following test failed, say
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. |
|
Manually merging to get past flakes (which we are separately actively investigating) |
|
[ART PR BUILD NOTIFIER] This PR has been included in build operator-lifecycle-manager-container-v4.16.0-202312202231.p0.g18aa3be.assembly.stream for distgit operator-lifecycle-manager. |
|
/cherry-pick release-4.15 |
|
/retitle OCPBUGS-24526: Synchronize From Upstream Repositories |
openshift-ci
bot
changed the title
|
@openshift-bot: Jira Issue OCPBUGS-24526: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-24526 has been moved to the MODIFIED state. In response to this:
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. |
|
@stevekuznetsov: new pull request created: #643 In response to this:
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. |
|
/cherry-pick release-4.15 |
|
@stevekuznetsov: new pull request could not be created: failed to create pull request against openshift/operator-framework-olm#release-4.15 from head openshift-cherrypick-robot:cherry-pick-627-to-release-4.15: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-627-to-release-4.15."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} In response to this:
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. |
|
/retitle OCPBUGS-25448,OCPBUGS-24526: Synchronize From Upstream Repositories |
openshift-ci
bot
changed the title
|
@openshift-bot: Jira Issue OCPBUGS-25448: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-25448 has been moved to the MODIFIED state. Jira Issue OCPBUGS-24526 is in an unrecognized state (MODIFIED) and will not be moved to the MODIFIED state. In response to this:
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. |
|
/retitle OCPBUGS-23538,OCPBUGS-25448,OCPBUGS-24526: Synchronize From Upstream Repositories |
openshift-ci
bot
changed the title
|
@openshift-bot: Jira Issue OCPBUGS-23538 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. Jira Issue OCPBUGS-25448 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. Jira Issue OCPBUGS-24526 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state. In response to this:
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. |
The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:
github.com/ghodss/yamlwithsigs.k8s.io/yaml(#1171)This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.
/cc @openshift/openshift-team-operator-runtime
/cc @openshift/openshift-team-operator-ecosystem