Bug 1814692 - openshift-apiserver should create stable backend
Summary: openshift-apiserver should create stable backend
Keywords:
Status: CLOSED DUPLICATE of bug 1814618
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.5.0
Assignee: Luis Sanchez
QA Contact: Xingxing Xia
URL:
Whiteboard:
Depends On:
Blocks: 1813919
TreeView+ depends on / blocked
 
Reported: 2020-03-18 14:20 UTC by Luis Sanchez
Modified: 2020-03-19 15:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1813919
Environment:
Last Closed: 2020-03-19 15:02:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-openshift-apiserver-operator pull 340 0 None closed Bug 1814692 - openshift-apiserver should create stable backend 2020-03-23 09:20:43 UTC

Description Luis Sanchez 2020-03-18 14:20:34 UTC
+++ This bug was initially created as a clone of Bug #1813919 +++

Description of problem: reviewing recent upgrade failures I observed
```
Mar 14 04:38:32.591 I ns/openshift-apiserver-operator deployment/openshift-apiserver-operator Updated storage urls to https://10.0.0.3:2379,https://10.0.0.4:2379,https://10.0.0.5:2379 (3001 times)
```

ref: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-etcd-operator/257/pull-ci-openshift-cluster-etcd-operator-master-e2e-gcp-upgrade/1147/artifacts/e2e-gcp-upgrade/e2e.log

I would expect this to change very infrequently.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results: backend reported by the observer is stable based on the actual client list not hot looping.


Additional info:

Comment 1 Standa Laznicka 2020-03-19 15:02:13 UTC

*** This bug has been marked as a duplicate of bug 1814618 ***


Note You need to log in before you can comment on or make changes to this bug.