search

openshift / cluster-kube-apiserver-operator

The kube-apiserver operator installs and maintains the kube-apiserver on a cluster
Apache License 2.0
74 stars 159 forks source link

OCPBUGS-42083: Don't rollout revision until three etcd endpoints are listed #1743

Closed vrutkovs closed 1 month ago

vrutkovs commented 2 months ago

Prevent apiserver from pointing to a single etcd endpoint (IP and localhost), which will lose connection when the single etcd is being updated

vrutkovs commented 2 months ago

/test e2e-azure-ovn /payload-aggregate periodic-ci-openshift-release-master-nightly-4.17-e2e-azure-ovn-kube-apiserver-rollout 10

openshift-ci[bot] commented 2 months ago

@vrutkovs: 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/f3e3cdf0-7c9c-11ef-9614-4fb038d9905b-0

vrutkovs commented 2 months ago

/test e2e-azure-ovn /payload-aggregate periodic-ci-openshift-release-master-nightly-4.17-e2e-azure-ovn-kube-apiserver-rollout 10

openshift-ci[bot] commented 2 months ago

@vrutkovs: 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/8898f0e0-7ca4-11ef-9d68-6af2d98e5388-0

openshift-ci-robot commented 2 months ago

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

3 validation(s) were run on this bug * bug is open, matching expected state (open) * bug target version (4.18.0) matches configured target version for branch (4.18.0) * bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1743): >Prevent apiserver from pointing to a single etcd endpoint (IP and localhost), which will lose connection when the single etcd is being updated Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
vrutkovs commented 1 month ago

/retest

vrutkovs commented 1 month ago

/payload-aggregate periodic-ci-openshift-release-master-nightly-4.17-e2e-azure-ovn-kube-apiserver-rollout 10

openshift-ci[bot] commented 1 month ago

@vrutkovs: 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/8c0e55c0-800b-11ef-8f16-62d28d7d5e0a-0

vrutkovs commented 1 month ago

/test e2e-azure-ovn

vrutkovs commented 1 month ago

/retest-required

vrutkovs commented 1 month ago

/test e2e-aws-ovn

vrutkovs commented 1 month ago

/test e2e-aws-ovn

vrutkovs commented 1 month ago

/test e2e-gcp-operator

dgrisonnet commented 1 month ago

/lgtm /approve

openshift-ci[bot] commented 1 month ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgrisonnet, vrutkovs

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](https://github.com/openshift/cluster-kube-apiserver-operator/blob/master/OWNERS)~~ [dgrisonnet,vrutkovs] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
openshift-ci-robot commented 1 month ago

/retest-required

Remaining retests: 0 against base HEAD 3a58fd77c6f8883fb9d8683f7896070346425051 and 2 for PR HEAD 992114aa1298e9c10d2ae7df3a203a02f55c3d59 in total

openshift-ci[bot] commented 1 month ago

@vrutkovs: 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-gcp-operator-single-node 7067c16d6ed7a40edbaef52afd62652aca35df1f link false /test e2e-gcp-operator-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
deads2k commented 1 month ago

The problem this is targeting just failed another payload. I think the operator job is failing in general. I'm overriding and will notify the team in slack.

/override ci/prow/e2e-gcp-operator

openshift-ci[bot] commented 1 month ago

@deads2k: Overrode contexts on behalf of deads2k: ci/prow/e2e-gcp-operator

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1743#issuecomment-2402244928): >The problem this is targeting just failed another payload. I *think* the operator job is failing in general. I'm overriding and will notify the team in slack. > >/override ci/prow/e2e-gcp-operator > > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
openshift-ci-robot commented 1 month ago

@vrutkovs: Jira Issue OCPBUGS-42083: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to [this](https://github.com/openshift/cluster-kube-apiserver-operator/pull/1743): >Prevent apiserver from pointing to a single etcd endpoint (IP and localhost), which will lose connection when the single etcd is being updated Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-kube-apiserver-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.
openshift-bot commented 1 month ago

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-kube-apiserver-operator This PR has been included in build ose-cluster-kube-apiserver-operator-container-v4.18.0-202410092141.p0.ga64efd0.assembly.stream.el9. All builds following this will include this PR.