-
Bug
-
Resolution: Unresolved
-
Major
-
4.21
-
None
-
False
-
-
1
-
Important
-
Yes
-
None
-
Rejected
-
NI&D Sprint 283, NI&D Sprint 284
-
2
-
In Progress
-
Bug Fix
-
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-67232. The following is the description of the original issue:
—
Description of problem
OpenShift router's Dynamic Configuration Manager (DCM) was added to the TechPreviewNoUpgrade feature set in OpenShift 4.18.
DCM was removed from the TechPreviewNoUpgrade feature set during the OpenShift 4.20 development cycle because of a defect that caused tests to fail in "techpreview" CI jobs, which enable this feature set (see OCPBUGS-62987). This defect has since been fixed (see OCPBUGS-49908). DCM is now in only the DevPreviewNoUpgrade feature set, meaning it has been downgraded from tech preview to developer preview.
DCM should be added back to TechPreviewNoUpgrade in OpenShift 4.20 so that the feature that was previously tech preview doesn't regress to dev preview between 4.19 and 4.20.
Version-Release number of selected component (if applicable)
OpenShift 4.20.
How reproducible
100%.
Steps to Reproduce
1. Install an OpenShift 4.20 cluster and enable the "TechPreviewNoUpgrade" feature set.
2. Check whether the "IngressControllerDynamicConfigurationManager" feature gate is enabled
3. Check whether the ROUTER_HAPROXY_CONFIG_MANAGER=true environment variable is set on the "default" IngressController's "router-default" deployment.
Actual results
The feature gate is not enabled, and the environment variable is not set.
Expected results
The feature gate should be enabled, and the environment variable should be set.
- clones
-
OCPBUGS-67232 DynamicConfigurationManager regressed from TPNU to DPNU
-
- Verified
-
- is blocked by
-
OCPBUGS-67232 DynamicConfigurationManager regressed from TPNU to DPNU
-
- Verified
-
- links to