-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.15
-
No
-
False
-
Description of problem:
When trying to install cluster with static IPs, control plane nodes are recreated by CPMS and the IPs is no longer static, details see https://redhat-internal.slack.com/archives/CH06KMDRV/p1706255642178569
Version-Release number of selected component (if applicable):
4.15.0-0.nightly-2024-01-22-160236
How reproducible:
always
Steps to Reproduce:
1. install cluster with static IPs defined 2. check control plane nodes IPs
Actual results:
control plane nodes are reconciled by CPMS and the IPs is no longer static
Expected results:
control plane nodes should use static IPs defined
Additional info:
There are some differences in manifest, maybe that's the reason why CPMS recreated master nodes
# cat cluster/openshift/99_openshift-cluster-api_master-machines-0.yaml ... providerSpec: value: apiVersion: machine.openshift.io/v1beta1 credentialsSecret: name: vsphere-cloud-credentials diskGiB: 120 kind: VSphereMachineProviderSpec memoryMiB: 16384 metadata: creationTimestamp: null network: devices: - gateway: 192.168.221.1 ipAddrs: - 192.168.221.121/24 nameservers: - 192.168.221.1 networkName: devqe-segment-221 numCPUs: 4 numCoresPerSocket: 4 snapshot: "" template: sgao-devqe-2cfqg-rhcos-generated-region-generated-zone userDataSecret: name: master-user-data workspace: datacenter: DEVQEdatacenter datastore: /DEVQEdatacenter/datastore/vsanDatastore folder: /DEVQEdatacenter/vm/sgao-devqe-2cfqg resourcePool: /DEVQEdatacenter/host/DEVQEcluster//Resources server: vcenter.devqe.ibmc.devcluster.openshift.com status: {} # cat cluster/openshift/99_openshift-machine-api_master-control-plane-machine-set.yaml ... providerSpec: value: apiVersion: machine.openshift.io/v1beta1 credentialsSecret: name: vsphere-cloud-credentials diskGiB: 120 kind: VSphereMachineProviderSpec memoryMiB: 16384 metadata: creationTimestamp: null network: devices: - nameservers: - 192.168.221.1 numCPUs: 4 numCoresPerSocket: 4 snapshot: "" template: "" userDataSecret: name: master-user-data workspace: {} status: {}