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

[WIP] OCPBUGS-7359: Azure: move to kube-proxy LB probes, don't detach masters when unready #60

Closed

Conversation

damdo
Copy link
Member

@damdo damdo commented Mar 10, 2023

CCM change matching in-tree: openshift/kubernetes#1506

TODO:

  • update tests

@openshift-ci-robot openshift-ci-robot added the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label Mar 10, 2023
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 10, 2023
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 10, 2023
@openshift-ci-robot
Copy link

@damdo: This pull request references Jira Issue OCPBUGS-7359, which is invalid:

  • expected the bug to target the "4.14.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:

CCM change matching in-tree: openshift/kubernetes#1506

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.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 10, 2023
@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@damdo damdo force-pushed the azure-lb-issue-workaround-OCPBUGS-7359 branch from bb5a9a7 to 04f8b7e Compare March 10, 2023 11:59
@openshift-ci-robot
Copy link

@damdo: This pull request references Jira Issue OCPBUGS-7359, which is invalid:

  • expected the bug to target the "4.14.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.

In response to this:

CCM change matching in-tree: openshift/kubernetes#1506

TODO:

  • update tests

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.

Copy link

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

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

Would like to see some unit testing to make sure we are getting the expected ports and health paths out of this before we merge

@@ -2198,7 +2206,7 @@ func (az *Cloud) buildHealthProbeRulesForPort(serviceManifest *v1.Service, port
}
}
if path == nil {
path = pointer.String(consts.HealthProbeDefaultRequestPath)
path = pointer.String("/healthz")

Choose a reason for hiding this comment

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

What is the default request path? Is it not already /healthz?

Copy link
Member Author

Choose a reason for hiding this comment

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

No the default is / Do we want to change that at the const level?

Choose a reason for hiding this comment

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

Where else is the const used?

Copy link
Member Author

@damdo damdo Mar 10, 2023

Choose a reason for hiding this comment

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

Nowhere else. So we can probably change it.

Choose a reason for hiding this comment

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

Then I would change it yes :)

@@ -2178,7 +2186,7 @@ func (az *Cloud) buildHealthProbeRulesForPort(serviceManifest *v1.Service, port
//nolint:gosec
if item.Port == int32(port) {
//found the port
properties.Port = pointer.Int32(item.NodePort)
properties.Port = pointer.Int32(lbNodesHealthCheckPort)

Choose a reason for hiding this comment

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

Is this correct? Is this not someone having specified in an annotation that they want a specific port? I'm not sure why there seems to be an override here anyway? Can you explain why this needs to be changed?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah wanted to ask you an opinion on this.
Not sure why the probe port is being overridden by the NodePort here.
But if that's because we are "defaulting" then I think we should set it to lbNodesHealthCheckPort

Choose a reason for hiding this comment

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

Would need to dig into the code to work out and have an opinion on this, have you done any archeology to work out when this was introduced and why?

@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2023

@damdo: The following tests 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/openshift-e2e-azure-ovn-techpreview-upgrade 04f8b7e link false /test openshift-e2e-azure-ovn-techpreview-upgrade
ci/prow/unit 04f8b7e link true /test unit
ci/prow/e2e-azure-ovn-upgrade 04f8b7e link true /test e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-ccm 04f8b7e link false /test e2e-azure-ovn-ccm

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

Choose a reason for hiding this comment

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

This commit will want to be UPSTREAM: XXXX: so that once we agree on the approach upstream we can drop this, need a PR for that though

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 30, 2023
@openshift-merge-robot
Copy link

PR needs rebase.

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.

@JoelSpeed
Copy link

/close

We've superseded this now

@openshift-ci openshift-ci bot closed this Apr 3, 2023
@openshift-ci-robot
Copy link

@damdo: This pull request references Jira Issue OCPBUGS-7359. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

CCM change matching in-tree: openshift/kubernetes#1506

TODO:

  • update tests

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.

@openshift-ci
Copy link

openshift-ci bot commented Apr 3, 2023

@JoelSpeed: Closed this PR.

In response to this:

/close

We've superseded this now

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants