Bug 2093827 - an etcd member is not removed from the the etcd-endpoints configmap
Summary: an etcd member is not removed from the the etcd-endpoints configmap
Keywords:
Status: CLOSED DUPLICATE of bug 2093819
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: melbeher
QA Contact: ge liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-06 07:40 UTC by Lukasz Szaszkiewicz
Modified: 2022-07-20 11:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-20 11:22:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lukasz Szaszkiewicz 2022-06-06 07:40:15 UTC 
In this run [1] the scaling test was able to remove a machine and the controller was able to remove an etcd member for that machine from the etcd cluster. However the member was never removed from the etcd-endpoints configmap and the test failed.

Timeline:
...
successfully deleted the machine "ci-op-nz207tgr-04345-rr7bv-master-0-clone" from the API
cluster has reached the expected number of 3 voting members, the members are:
ensuring that the openshift-etcd/etcd-endpoints cm has the expected number of 3 voting members
unexpected number of voting members in the openshift-etcd/etcd-endpoints cm, expected exactly 3, got: 4
...
unexpected number of voting members in the openshift-etcd/etcd-endpoints cm, expected exactly 3, got: 4


[1] https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-nightly-4.11-e2e-vsphere-techpreview-serial/1533039934233907200
Note You need to log in before you can comment on or make changes to this bug.