Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Major
Fix Version/s: None
Affects Version/s: 4.10.0
Component/s: Installer / OpenShift on Bare Metal IPI
Labels:
- triaged

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None
Epic Link:
METAL-4

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Rejected
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

An install-config like this is currently allowed:

platform: 
  baremetal: 
    provisioningNetwork: Disabled
    clusterProvisioningIP: 1.2.3.4

However this will not work - the metal3 services will wait forever for the specified IP to come up on the host running the metal3 pod.

For some time we've [disabled the initContainer](https://github.com/openshift/cluster-baremetal-operator/pull/165) that runs [set-static-ip](https://github.com/openshift/ironic-static-ip-manager) so the IP will never become active

We should add validation to the installer so this combination is not allowed

is related to

OCPBUGS-4003 CBO: Webhook validations to prevent provisioningNetwork configuration when disabled

Closed

Assignee:: Unassigned

Reporter:: Steven Hardy (Inactive)

Need Info From:: None

Contributors:: None

QA Contact:: None

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2022/05/30 10:23 AM

Updated:: 2025/10/29 8:27 AM

Resolved:: 2023/03/10 8:08 PM