-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In the documentation, we refer that IMDSv2 can only be updated for clusters installed from 4.7 and onwards: https://docs.openshift.com/container-platform/4.17/machine_management/creating_machinesets/creating-machineset-aws.html#machineset-imds-options_creating-machineset-aws
It was because of the following reference: https://issues.redhat.com/browse/OCPBUGS-9971
"When the MCO eventually supports updating boot images, we can allow earlier clusters to use the feature and remove the note"
Now it is possible to update bootimage like AWS so updating the doc should be reviewed, regarding that warning, that first it is required to update the bootmage for old clusters: https://access.redhat.com/articles/7053165
Version-Release number of selected component (if applicable):
4.18
How reproducible:
100%
Actual results:
If we do not include this, cluster nodes will not boot with old bootimage.
Expected results:
To have procedure of updating bootimage in the section of IMDSv2
Additional info:
- links to