Bug 2007698 - [ceo] [release-4.6] Operator goes degraded when a second internal node ip is added after install [NEEDINFO]
Summary: [ceo] [release-4.6] Operator goes degraded when a second internal node ip is ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.7.z
Assignee: Dean West
QA Contact: ge liu
URL:
Whiteboard: LifecycleStale
Depends On: 1954121 1954129
Blocks: 1965535
TreeView+ depends on / blocked
 
Reported: 2021-09-24 15:59 UTC by Alan Chan
Modified: 2022-04-27 11:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1954121
Environment:
Last Closed: 2022-04-27 11:32:02 UTC
Target Upstream Version:
Embargoed:
mfojtik: needinfo?


Attachments (Terms of Use)

Comment 2 Sam Batschelet 2021-09-27 13:16:35 UTC
etcd team did attempt a backport of this PR which was not clean[1]. We have not had the cycles to address during this spring but will revisit.

[1] https://github.com/openshift/cluster-etcd-operator/pull/577#issuecomment-849369393

Comment 3 Michal Fojtik 2021-11-24 08:09:30 UTC
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Whiteboard if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.


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