-
Bug
-
Resolution: Done
-
Critical
-
None
-
4.17
-
None
-
Proposed
-
False
-
Description of problem: 4.16 to 4.17 upgrades are broken
Version-Release number of selected component (if applicable): 4.17
How reproducible: ALWAYS
Steps to Reproduce:
3.
Actual results:
Expected results:
Additional info:
Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.
Affected Platforms:
Is it an
- internal CI failure - YES
customer issue / SDinternal RedHat testing failure
If it is a CI failure:
- Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
- Same lanes; links attacked above
- Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
- N/A no more SDN in 4.17
- Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
- susceptible to all platforms
- When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
- Probably from the last two downstream merges we did
CNI side is expecting role:primary on all pods but older pods won't have this, we forgot to account for backwards compatibility
FIX:
- All CNI bits must be behind a feature gate
- We must handle role:primary being absent for pods and ignore them in the checks except for when network is default