-
Bug
-
Resolution: Unresolved
-
Normal
-
4.17.z
Description of problem:
Backport request of fix OCPBUGS-38507 to 4.16 and 4.17
Version-Release number of selected component (if applicable):
4.16.28
How reproducible:
Always
Steps to Reproduce:
1. Deploy BM IPI cluster with static ip on provision interface 2. 3.
Actual results:
metal3 pod in "Init:CrashLoopBackOff": ~~~ + '[' -z XXX.YYY.0.2/16 ']' + '[' -z bond1 ']' + '[' -n bond1 ']' ++ ip -o addr show dev bond1 scope global + [[ -n 17: bond1 inet XXX.YYY.1.53/16 brd XXX.YYY.255.255 scope global noprefixroute bond1\ valid_lft forever preferred_lft forever ]] + ip -o addr show dev bond1 scope global + grep -q XXX.YYY.0.2/16 + echo 'ERROR: "bond1" is already set to ip address belong to different subset than "XXX.YYY.0.2/16"' ERROR: "bond1" is already set to ip address belong to different subset than "XXX.YYY.0.2/16" + exit 1 ~~~
Expected results:
No issue
Additional info:
same issue as described in OCPBUGS-38507, requesting backport to 4.16 and 4.17
- depends on
-
OCPBUGS-38507 static IP manager crashloops for a while on pod startup
- Verified
-
OCPBUGS-49350 static IP manager crashloops for a while on pod startup
- Verified