Bug 2007448 - cluster-etcd-operator: render command should fail if machineCidr contains reserved address [NEEDINFO]
Summary: cluster-etcd-operator: render command should fail if machineCidr contains res...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.7
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.7.z
Assignee: Haseeb Tariq
QA Contact: ge liu
URL:
Whiteboard: LifecycleStale
Depends On: 2007450
Blocks: 2004081
TreeView+ depends on / blocked
 
Reported: 2021-09-23 21:50 UTC by Haseeb Tariq
Modified: 2022-08-24 17:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2004081
: 2007450 (view as bug list)
Environment:
Last Closed: 2022-08-24 17:15:55 UTC
Target Upstream Version:
Embargoed:
mfojtik: needinfo?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2004081 1 medium CLOSED cluster-etcd-operator: render command should fail if machineCidr contains reserved address 2024-12-20 21:02:50 UTC

Internal Links: 2007450

Description Haseeb Tariq 2021-09-23 21:50:18 UTC 
+++ This bug was initially created as a clone of Bug #2004081 +++

Description of problem: OCP explicitly does not allow the use of the following reserved address blocks.

2001:db8::/32

192.0.2.0/24

If the render command observes these in the install-config as machineCidr it should fail and provide a clear message to admin.

https://github.com/openshift/cluster-kube-apiserver-operator/blob/d6a60b2c18806d69dcf27228aacb830a699126f3/pkg/operator/configobservation/etcdendpoints/observe_etcd_endpoints.go#L72



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


How reproducible: 100%


Steps to Reproduce:
1. create a cluster with machineCidr defined using one of the ranges above
2. cluster will fail to bootstrap because we will skip these endpoints in the observers used by the control-plane operators[1].
3.

Actual results: bootstrap fails for an unknown reason.


Expected results: bootstrap fails early as possible with a clear message indicating the address range is unsupported.


Additional info:

[1] https://github.com/openshift/cluster-kube-apiserver-operator/blob/d6a60b2c18806d69dcf27228aacb830a699126f3/pkg/operator/configobservation/etcdendpoints/observe_etcd_endpoints.go#L72
Comment 1 Michal Fojtik 2021-11-22 11:09:29 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.
Comment 4 Scott Dodson 2022-08-24 17:15:55 UTC 
With no customer cases attached and fixes having made it no further than 4.9 I'm going ahead and closing this as 4.7 is now EOL.
Note You need to log in before you can comment on or make changes to this bug.