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-38802[*OCPBUGS-38802*])

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-38802 [* OCPBUGS-38802 *])
Release Note Type:
Bug Fix
Release Note Status:
In Progress
Target Version:

4.18.0

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:

blocks

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

is cloned by

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

links to

RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update