OCPBUGS-55288: Added note about bonded interface and node IP address …

[dfitzmau]

Version(s):

Issue:
OCPBUGS-55228

Link to docs preview:

• Establishing communication between subnets

• SME has approved this chanage.
• QE has approved this change.

[openshift-ci-robot]

@dfitzmau: No Jira issue with key OCPBUGS-55288 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

…issues

Version(s):

Issue:

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@dfitzmau: No Jira issue with key OCPBUGS-55288 exists in the tracker at https://issues.redhat.com/.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

In response to this:

Version(s):

Issue:
OCPBUGS-55228

Link to docs preview:

• SME has approved this chanage.
• QE has approved this change.

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 openshift-eng/jira-lifecycle-plugin repository.

[ocpdocs-previewbot]

🤖 Fri Apr 25 11:05:13 - Prow CI generated the docs preview:

https://92534--ocpdocs-pr.netlify.app/openshift-enterprise/latest/installing/installing_bare_metal/ipi/ipi-install-installation-workflow.html

[palonsoro]

Hi. I made a review with what the comment should look like. However, I see it is focused in baremetal IPI edge clusters, while we would need to document this for all kinds of both baremetal IPI and UPI clusters (and text might slightly change between scenarios).

So not sure if you could please move/clone the text to wherever it applies and we can then do further review.

Thanks.

[cybertron]

/lgtm

At some point I think we want more explicit documentation about the two-step process that can be used in day one configuration, but for now this is better than nothing.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci-robot]

@dfitzmau: This pull request references Jira Issue OCPBUGS-55288, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Version(s):

Issue:
OCPBUGS-55228

Link to docs preview:

• Establishing communication between subnets

• SME has approved this chanage.
• QE has approved this change.

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@dfitzmau: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

[palonsoro]

This is much better now.

I'd just clarify that if this happens, node installation may never end correctly.

[dfitzmau]

Thanks, @palonsoro . If any steps exist that I could embed in the docs, please let me know.

Maybe somewhere around https://docs.redhat.com/en/documentation/openshift_container_platform/4.18/html-single/installing_on_bare_metal/index#ipi-install-setting-cluster-node-hostnames-dhcp_ipi-install-installation-workflow?

[palonsoro]

I cannot think of concrete steps, because what you need to do is either already in the docs or out the scope of it.