Skip to content
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

OCPBUGS-41785: Validate MTU when controlPlanePort uses FixedIPs #9081

Merged

Conversation

mandre
Copy link
Member

@mandre mandre commented Oct 8, 2024

The minimum MTU for the IPv6 network was previously only enforced when the controlPlanePort used the Network filter. This commit change the validation to also work when using the Subnet filter from FixedIPs.

This commit does two things:

  • populate the ControlPlanePortNetwork struct in CloudInfo even when using the Subnet filter and not the Network one.
  • move the validation for MTU out of the branch for Network filter from the install-config.yaml

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 8, 2024
@openshift-ci-robot
Copy link
Contributor

@mandre: This pull request references Jira Issue OCPBUGS-41785, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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

In response to this:

The minimum MTU for the IPv6 network was previously only enforced when the controlPlanePort used the Network filter. This commit change the validation to also work when using the Subnet filter from FixedIPs.

This commit does two things:

  • populate the ControlPlanePortNetwork struct in CloudInfo even when using the Subnet filter and not the Network one.
  • move the validation for MTU out of the branch for Network filter from the install-config.yaml

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 openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 8, 2024
The minimum MTU for the IPv6 network was previously only enforced when
the controlPlanePort used the Network filter. This commit change the
validation to also work when using the Subnet filter from FixedIPs.

This commit does two things:
- populate the ControlPlanePortNetwork struct in CloudInfo even when
  using the Subnet filter and not the Network one.
- move the validation for MTU out of the branch for Network filter from
  the install-config.yaml
@mandre mandre force-pushed the mtu-validation-fix branch from 1005bb2 to 3ab8bca Compare October 8, 2024 11:02
@pierreprinetti
Copy link
Member

Looks legit, but I think I'll need the CI results to build a bit more confidence

/approve
/lgtm
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 8, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 8, 2024
Copy link
Contributor

openshift-ci bot commented Oct 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierreprinetti

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 8, 2024
@mandre
Copy link
Member Author

mandre commented Oct 8, 2024

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 8, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 7534652 and 2 for PR HEAD 3ab8bca in total

Copy link
Contributor

openshift-ci bot commented Oct 8, 2024

@mandre: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack-nfv-intel 3ab8bca link false /test e2e-openstack-nfv-intel

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.

@openshift-merge-bot openshift-merge-bot bot merged commit e61b787 into openshift:master Oct 8, 2024
21 of 22 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the mtu-validation-fix branch October 8, 2024 18:02
@openshift-ci-robot
Copy link
Contributor

@mandre: Jira Issue OCPBUGS-41785: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-41785 has been moved to the MODIFIED state.

In response to this:

The minimum MTU for the IPv6 network was previously only enforced when the controlPlanePort used the Network filter. This commit change the validation to also work when using the Subnet filter from FixedIPs.

This commit does two things:

  • populate the ControlPlanePortNetwork struct in CloudInfo even when using the Subnet filter and not the Network one.
  • move the validation for MTU out of the branch for Network filter from the install-config.yaml

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants