-
Bug
-
Resolution: Done
-
Critical
-
4.12
-
Moderate
-
None
-
1
-
Metal Platform 229, Metal Platform 230
-
2
-
Approved
-
False
-
Description of problem:
when provisioningNetwork is changed from Disabled to Managed/Unmanaged, the ironic-proxy daemonset is not removed This causes the metal3 pod to be stuck in pending, since both pods are trying to use port 6385 on the host: 0/3 nodes are available: 3 node(s) didn't have free ports for the requested pod ports. preemption: 0/3 nodes are available: 3 node(s) didn't have free ports for the requested pod ports
Version-Release number of selected component (if applicable):
4.12rc.4
How reproducible:
Every time for me
Steps to Reproduce:
1. On a multinode cluster, change the provisioningNetwork from Disabled to Unmanaged (I didn't try Managed) 2. 3.
Actual results:
0/3 nodes are available: 3 node(s) didn't have free ports for the requested pod ports. preemption: 0/3 nodes are available: 3 node(s) didn't have free ports for the requested pod ports
Expected results:
I believe the ironic-proxy daemonset should be deleted when the provisioningNetwork is set to Managed/Unmanaged
Additional info:
If I manually delete the ironic-proxy Daemonset, the controller does not re-create it.
- clones
-
OCPBUGS-4712 ironic-proxy daemonset not deleted when provisioningNetwork is changed from Disabled to Managed/Unmanaged
- Closed
- depends on
-
OCPBUGS-4712 ironic-proxy daemonset not deleted when provisioningNetwork is changed from Disabled to Managed/Unmanaged
- Closed
- links to