Loading...

XML

Word

Printable

Severity:
Moderate
Regression:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
* Previously, during installation the `oc adm node-image create` command used the kube-system/cluster-config-v1 resource to determine the platform type. With this release, the installation program uses the infrastructure resource, which provides more accurate information about the platform type. (link:https://issues.redhat.com/browse/OCPBUGS-39092[*~~OCPBUGS-39092~~*])

Show
* Previously, during installation the `oc adm node-image create` command used the kube-system/cluster-config-v1 resource to determine the platform type. With this release, the installation program uses the infrastructure resource, which provides more accurate information about the platform type. (link: https://issues.redhat.com/browse/OCPBUGS-39092 [* OCPBUGS-39092 *])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.17.0

This is a clone of issue OCPBUGS-38802. The following is the description of the original issue:
—
Description of problem:

    Infrastructure object with platform None is ignored by node-joiner tool

Version-Release number of selected component (if applicable):

    4.17

How reproducible:

    Always

Steps to Reproduce:

    1. Run the node-joiner add-nodes command

Actual results:

    Currently the node-joiner tool retrieves the platform type from the kube-system/cluster-config-v1 config map

Expected results:

Retrieve the platform type from the infrastructure cluster object

Additional info:

clones

OCPBUGS-38802 node-joiner add-nodes ignores infrastructure platform type

is blocked by

OCPBUGS-38802 node-joiner add-nodes ignores infrastructure platform type

links to

RHEA-2024:3718 OpenShift Container Platform 4.17.z bug fix update