Bug 1811706
| Summary: | On upgrade: EtcdMemberIPMigratorDegraded: etcdserver: Peer URLs already exists | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luis Sanchez <sanchezl> |
| Component: | Etcd Operator | Assignee: | Sam Batschelet <sbatsche> |
| Status: | CLOSED DUPLICATE | QA Contact: | ge liu <geliu> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.4 | CC: | alpatel, sbatsche, sdodson, wking |
| Target Milestone: | --- | Keywords: | Upgrades |
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-03-16 17:18:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Luis Sanchez
2020-03-09 15:23:18 UTC
This came up in 4.3.5 -> 4.4.0-rc.1 CI testing [1,2]. We're asking the following questions to evaluate whether or not this bug warrants blocking an upgrade edge from either the previous X.Y or X.Y.Z. The ultimate goal is to avoid delivering an update which introduces new risk or reduces cluster functionality in any way. Sample answers are provided to give more context the UpgradeBlocker flag has been added to this bug. It will be removed if the assessment indicates that this should not block upgrade edges. Who is impacted? Customers upgrading from 4.2.99 to 4.3.z running on GCP with thousands of namespaces, approximately 5% of the subscribed fleet All customers upgrading from 4.2.z to 4.3.z fail approximately 10% of the time What is the impact? Up to 2 minute disruption in edge routing Up to 90seconds of API downtime etcd loses quorum and you have to restore from backup How involved is remediation? Issue resolves itself after five minutes Admin uses oc to fix things Admin must SSH to hosts, restore from backups, or other non standard admin activities Is this a regression? No, it’s always been like this we just never noticed Yes, from 4.2.z and 4.3.1 Looks like we hit this in CI every few hours [3], for 15 hits over the past ~3d. [1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade/443 [2]: https://github.com/openshift/cincinnati-graph-data/pull/118#issuecomment-599007279 [3]: https://search.svc.ci.openshift.org/?search=EtcdMemberIPMigratorDegraded%3A+etcdserver%3A+Peer+URLs+already+exists&maxAge=168h&context=-1&type=build-log Setting high priority until we get an impact statement, since hung updates with unknown root causes are pretty bad. Once we have a handle on the cause and impact, we can adjust the priority as appropriate. Possibly this is a bug introduced by bug 1812071 [1] or bug 1812210 [2]? [1]: https://github.com/openshift/cluster-kube-apiserver-operator/pull/791 [2]: https://github.com/openshift/cluster-kube-apiserver-operator/pull/792 *** This bug has been marked as a duplicate of bug 1812584 *** Removing UpgradeBlocker from this older bug, to remove it from the suspect queue described in [1]. If you feel like this bug still needs to be a suspect, please add keyword again. [1]: https://github.com/openshift/enhancements/pull/475 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |