Skip to content

OCPBUGS-51174: Updated the changing-cluster-network-mtu file with NIC… #89757

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dfitzmau
Copy link
Contributor

@dfitzmau dfitzmau commented Mar 6, 2025

Version(s):
4.12+

Issue:
OCPBUGS-51174 and OSDOCS-13689

Link to docs preview:

  • SME has approved this change (Kevin Anderson).
  • QE has approved this change (Anurag Saxena/Jaime Caamano).

More clarifications needed.

@openshift-ci-robot
Copy link

@dfitzmau: No Jira issue with key OCPBUGS-55174 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:

… info

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 openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 6, 2025
@openshift-ci-robot
Copy link

@dfitzmau: No Jira issue with key OCPBUGS-55174 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):
4.12+

Issue:
OCPBUGS-51174

Link to docs preview:

  • SME has approved this change.
  • 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.

@dfitzmau dfitzmau force-pushed the OCPBUGS-51174 branch 3 times, most recently from 769f37d to b5eccd9 Compare March 6, 2025 14:58
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Mar 6, 2025

🤖 Fri Mar 21 16:56:58 - Prow CI generated the docs preview:
https://89757--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@openshift-ci-robot
Copy link

@dfitzmau: No Jira issue with key OCPBUGS-55174 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):
4.12+

Issue:
OCPBUGS-51174

Link to docs preview:

  • SME has approved this change.
  • 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 openshift-ci bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 6, 2025
@dfitzmau dfitzmau force-pushed the OCPBUGS-51174 branch 2 times, most recently from c087ec1 to 5a171ac Compare March 6, 2025 16:02
@dfitzmau dfitzmau force-pushed the OCPBUGS-51174 branch 7 times, most recently from ada3169 to 7c95b15 Compare March 7, 2025 12:51
[source,ini]
----
[connection-<primary-NIC-bond-interface>-mtu]
match-device=interface-name:<bond-iface-name>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are normally at least 2 interfaces assigned to a bond, I think it would be more clear to show two.
This solution article How to change bond MTU shows 2 slave interfaces.
To make this truly be an "Example", it might be more helpful to use eth0 and eth1:

[bond0-mtu]
match-device=interface-name:bond0
ethernet.mtu=9000

[connection-eth0-mtu]
match-device=interface-name:eth0
ethernet.mtu=9000

[connection-eth1-mtu]
match-device=interface-name:eth1
ethernet.mtu=9000

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for that info. Updated!

@dfitzmau dfitzmau changed the title OCPBUGS-55174: Updated the changing-cluster-network-mtu file with NIC… OCPBUGS-51174: Updated the changing-cluster-network-mtu file with NIC… Mar 10, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 10, 2025
@openshift-ci-robot
Copy link

@dfitzmau: This pull request references Jira Issue OCPBUGS-51174, 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):
4.12+

Issue:
OCPBUGS-51174

Link to docs preview:

  • SME has approved this change.
  • 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.

@kevin-anderson-redhat
Copy link

LGTM

@dfitzmau dfitzmau added the peer-review-needed Signifies that the peer review team needs to review this PR label Mar 10, 2025
@jldohmann jldohmann added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Mar 10, 2025
Copy link
Contributor

@jldohmann jldohmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly LGTM! some comments and suggestions below

`<machine_to>`:: Specifies the MTU for the primary network interface on the underlying host network.
--
<1> Where `<overlay_from>` specifies the current cluster network MTU value.
<2> Where `<overlay_to>` specifies the target MTU for the cluster network. This value is set relative to the value of
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This callout is cut off

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️

@jldohmann jldohmann added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR peer-review-needed Signifies that the peer review team needs to review this PR labels Mar 10, 2025
@jldohmann jldohmann added this to the Continuous Release milestone Mar 10, 2025
@dfitzmau
Copy link
Contributor Author

/retest

@anuragthehatter
Copy link

Looks good to me. I would like @jcaamano to take a look as well

+
ifndef::outposts[]
.Example that increases the cluster MTU
[source,terminal]
----
$ oc patch Network.operator.openshift.io cluster --type=merge --patch \
'{"spec": { "migration": { "mtu": { "network": { "from": 1400, "to": 9000 } , "machine": { "to" : 9100} } } } }'
'{"spec": { "migration": { "mtu": { "network": { "from": 1400, "to": 8900 } , "machine": { "to" : 9000} } } } }'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

openshift-ci bot commented Mar 21, 2025

@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.

----
<1> Where `<node_name>` specifies the name of a node in your cluster.
<2> Where `ovs-if-phys0` is the primary network interface. For nodes that use multiple NIC bonds, append `bond-sub0` for the primary NIC bond interface and `bond-sub1` for the secondary NIC bond interface.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Append to what? Where does bond-sub0 and bond-sub1 come from?

where:
[NOTE]
====
For nodes that use a network interface controller (NIC) bond interface, list the bond interface and any sub-interfaces in the `<bond-interface>-mtu.conf` file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does this information come from? The MTU of the sub-interfaces should automatically acquire the same MTU of the bond interface.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the <bond-interface>-mtu.conf mentioned before in this document.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jcaamano There are 2 things that come to mind with respect to the procedure as written:

  1. The docs does not address bonded NICs or VLANs at all. It is left as an exercise for the reader to extrapolate the documented steps, covering a single NIC, to multiple NICs under a bond

  2. The OpenShift agent based installer for bare metal systems allows for the MTU to be specified on each "interface"; sub NICs, bond, VLAN. If, during install, we set the MTU at all 3 levels, for some reason, and then we apply the MTU change procedure only to the sub NICs of the bond, will the bond and the vlan interfaces inherit the new sub NIC configuration, or, will the fact that I specifically set the MTU level at all 3 places during install mean that the sub NICs have the new MTU but the bond and vlan interfaces have the old MTU because there was an actual setting provided and not just inherited?

If on the other hand, changing the sub NIC interfaces' MTU would propagate then item 1 is really the primary concern. Leaving the extrapolation of the procedure as an exercise for the reader is risky and actually did impact one of our systems.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dmc5179

  1. What do you feel this doc need to address about bonds that is missing? To my knowledge, the procedure would be exactly the same with bonds.
  2. You don't need to specify the MTU of the subordinates of the bond. They automatically acquire the MTU of the parent. Maybe this is what is being the problem but unknown without taking a deeper look. In any case, it would be impossible for this procedure to cover, or be aware of, all possible network configurations. I had already submitted a PR to add that disclaimer to this doc, I will dig that PR up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<2> Specify the local filename for the updated NetworkManager configuration file from the previous step.

.... Create the following Butane config in the `worker-interface.bu` file:
<2> Specify the local filename for the updated NetworkManager configuration file from the previous step. For NIC bonds, specify the name for the `<bond-interface>-mtu.conf` file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see why <interface> would be different than <bond-interface>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.12 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants