Bare Metal Platform Customization document mentions wrong field

[mzamot]

Version

$ openshift-install version

N/A

Platform:

Baremetal

What happened?

In the Bare Metal Platform Customization document the value clusterProvisioningIP is mentioned to modify the IP within the cluster where the provisioning services run. However, this field is not the correct one, instead provisioningHostIP should be used.
By using clusterProvisioningIP in the install-config.yaml file, no IP is changed, but by using provisioningHostIP the right behavior is achieved.

What you expected to happen?

The right field should be mentioned in the table.

How to reproduce it (as minimally and precisely as possible)?

N/A

[dhellmann]

/label platform/baremetal

[hardys]

This should be fixed when we land #4053 but I guess the docs should be modified to reflect the correct name on older release branches

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[stbenjam]

This was fixed in #4053

/close

[openshift-ci-robot]

@stbenjam: Closing this issue.

In response to this:

This was fixed in #4053

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.