Skip to content

OCPBUGS-67210: Fix: Prevent Available=False during single-replica deployment upgrades in SNO #1171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
jianzhangbjz wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OCPBUGS-67210: Fix: Prevent Available=False during single-replica deployment upgrades in SNO #1171

jianzhangbjz wants to merge 1 commit into from
+514 −27

Conversation

@jianzhangbjz
Copy link
Member

@jianzhangbjz jianzhangbjz commented Dec 11, 2025

Don't merge. I created this PR just for testing. The upstream one: operator-framework/operator-lifecycle-manager#3720

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 11, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 11, 2025

@jianzhangbjz: 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.21-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8bc1cf10-d669-11f0-8615-76b52b655a64-0

@openshift-ci openshift-ci bot requested review from grokspawn and oceanc80 December 11, 2025 08:15
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 11, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2025
@jianzhangbjz jianzhangbjz force-pushed the OCPBUGS-67210 branch 2 times, most recently from 4bea5b5 to b34cd91 Compare December 11, 2025 08:56
@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 11, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 11, 2025

@jianzhangbjz: 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.21-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7019ba10-d674-11f0-89d9-98d61609b448-0

@jianzhangbjz jianzhangbjz changed the title UPSTREAM: <carry>: Fix: Prevent Available=False during single-replica deployment upgrades in SNO OCPBUGS-67210: Fix: Prevent Available=False during single-replica deployment upgrades in SNO Dec 15, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Dec 15, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 15, 2025

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-67210, which is invalid:

  • expected the bug to target the "4.22.0" version, but no target version was set

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:

Don't merge. I created this PR just for testing. The upstream one: operator-framework/operator-lifecycle-manager#3720

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.

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 15, 2025

To address https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-operator-framework-olm-1171-ci-4.21-e2e-aws-upgrade-ovn-single-node/1999049874103865344

Dec 11 10:57:17.949 E clusteroperator/operator-lifecycle-manager-packageserver condition/Available reason/ClusterServiceVersionNotSucceeded status/False ClusterServiceVersion openshift-operator-lifecycle-manager/packageserver observed in phase Failed with reason: APIServiceResourceIssue, message: the server was unable to return a response in the time allotted, but may still be processing the request (get serviceaccounts olm-operator-serviceaccount)

@jianzhangbjz jianzhangbjz force-pushed the OCPBUGS-67210 branch 2 times, most recently from 1d2f31f to 03e0027 Compare December 15, 2025 08:59
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 15, 2025

@jianzhangbjz: 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/verify-deps 1d2f31f link true /test verify-deps
ci/prow/verify 1d2f31f link true /test verify
ci/prow/okd-scos-images 1d2f31f link true /test okd-scos-images

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

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 15, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 15, 2025

@jianzhangbjz: 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.21-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1795f230-d996-11f0-96a2-4757ff0ab490-0

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 15, 2025

Raise it to DPTP team: https://redhat-internal.slack.com/archives/CBN38N3MW/p1765791339549229

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 16, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 16, 2025

@jianzhangbjz: 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.21-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/77a70e00-da24-11f0-8a3d-cc734947f98e-0

@jianzhangbjz
Copy link
Member Author

jianzhangbjz commented Dec 16, 2025

/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 16, 2025

@jianzhangbjz: 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.21-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/390867f0-da26-11f0-9c61-91f86d1ec5dd-0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@grokspawn grokspawn Awaiting requested review from grokspawn

@oceanc80 oceanc80 Awaiting requested review from oceanc80

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jianzhangbjz @openshift-ci-robot