OCPBUGS-67210: Fix: Prevent Available=False during single-replica deployment upgrades in SNO#1171
OCPBUGS-67210: Fix: Prevent Available=False during single-replica deployment upgrades in SNO#1171jianzhangbjz wants to merge 2 commits intoopenshift:mainfrom
Conversation
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8bc1cf10-d669-11f0-8615-76b52b655a64-0 |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
jianzhangbjz
force-pushed
the
OCPBUGS-67210
branch
2 times, most recently
from
4bea5b5 to
b34cd91
Compare
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7019ba10-d674-11f0-89d9-98d61609b448-0 |
jianzhangbjz
changed the title
openshift-ci-robot
added
jira/severity-important
|
@jianzhangbjz: This pull request references Jira Issue OCPBUGS-67210, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
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
force-pushed
the
OCPBUGS-67210
branch
2 times, most recently
from
1d2f31f to
03e0027
Compare
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1795f230-d996-11f0-96a2-4757ff0ab490-0 |
|
Raise it to DPTP team: https://redhat-internal.slack.com/archives/CBN38N3MW/p1765791339549229 |
jianzhangbjz
force-pushed
the
OCPBUGS-67210
branch
from
03e0027 to
55f7dfd
Compare
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/77a70e00-da24-11f0-8a3d-cc734947f98e-0 |
jianzhangbjz
force-pushed
the
OCPBUGS-67210
branch
from
55f7dfd to
d2ca984
Compare
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/390867f0-da26-11f0-9c61-91f86d1ec5dd-0 |
jianzhangbjz
force-pushed
the
OCPBUGS-67210
branch
from
d2ca984 to
5c048ee
Compare
… deployment upgrades in SNO
jianzhangbjz
force-pushed
the
OCPBUGS-67210
branch
from
5c048ee to
263f2d2
Compare
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/65c2dbb0-da60-11f0-92e1-44fb2cc276bd-0 |
|
/test e2e-gcp-olm |
|
@jianzhangbjz: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
… deployment upgrades in SNO
|
/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node |
|
/payload-job periodic-ci-openshift-release-master-ci-4.21-e2e-aws-upgrade-ovn-single-node |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ea6b7dc0-ef84-11f0-9100-fae90c95c92e-0 |
|
@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ece94f00-ef84-11f0-910e-7e7016fb33a7-0 |
|
Both of them passed the test. |
|
Closed it because the preferred approach is not run those tests in SNO environments. More on Slack: https://redhat-internal.slack.com/archives/C06KP34REFJ/p1770156011955249 |
|
@jianzhangbjz: This pull request references Jira Issue OCPBUGS-67210. The bug has been updated to no longer refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
2 participants
Don't merge. I created this PR just for testing. The upstream one: operator-framework/operator-lifecycle-manager#3720