-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The Openshift on Openstack installation documentation [1] explicitly states that the platform.openstack.computeFlavor property is deprecated, recommending the use of the type key within platform.openstack.defaultMachinePlatform or individual machine pools instead. However, several sample install-config.yaml files, such as the "Example single stack install-config.yaml file" [2] and "Sample customized install-config.yaml file for restricted OpenStack installations" [3] (and also in dual-stack and on restricted network examples), continue to include the deprecated computeFlavor: m1.xlarge alongside the recommended type: ml.large parameter. This inconsistency between the stated deprecation and the provided examples can lead to confusion and potentially incorrect configurations.
Version-Release number of selected component (if applicable):
4.19 and before
How reproducible:
Steps to Reproduce:
1. Check openshift on openstack installation docs [1][2][3]
Actual results:
References to the deprecated computeFlavor parameter
Expected results:
Example install-config.yaml files should not include references to deprecated parameters
Additional info:
