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

Bug 1829233: Recreate DNS service upon Octavia upgrade #607

Merged

Conversation

MaysaMacedo
Copy link
Contributor

When Octavia is upgraded from OSP13 to OSP16 double listeners becomes
supported and the load balancers that requires TCP and UDP on same
port should be recreated.

This commit ensure the DNS service is recreated upon Octavia upgrade.

@MaysaMacedo MaysaMacedo changed the title Recreate DNS service upon Octavia upgrade wip: Recreate DNS service upon Octavia upgrade Apr 26, 2020
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 26, 2020
@MaysaMacedo MaysaMacedo changed the title wip: Recreate DNS service upon Octavia upgrade Recreate DNS service upon Octavia upgrade Apr 27, 2020
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 27, 2020
@MaysaMacedo
Copy link
Contributor Author

MaysaMacedo commented Apr 27, 2020

Verified the DNS service is recreated upon upgrade

@dulek
Copy link
Contributor

dulek commented Apr 28, 2020

Don't we need bug tied to this if we're planning to backport it?

pkg/platform/openstack/kuryr_bootstrap.go Outdated Show resolved Hide resolved
@MaysaMacedo MaysaMacedo force-pushed the delete-dns-svc-on-upgrade branch 2 times, most recently from 9db4d7b to 5fe5406 Compare April 29, 2020 08:55
@MaysaMacedo MaysaMacedo changed the title Recreate DNS service upon Octavia upgrade Bug 1829233: Recreate DNS service upon Octavia upgrade Apr 29, 2020
@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Apr 29, 2020
@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: This pull request references Bugzilla bug 1829233, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

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

In response to this:

Bug 1829233: Recreate DNS service upon Octavia upgrade

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.

When Octavia is upgraded from OSP13 to OSP16 double listeners becomes
supported and the load balancers that requires TCP and UDP on same
port should be recreated.

This commit ensure the DNS service is recreated upon Octavia upgrade.
@MaysaMacedo
Copy link
Contributor Author

/retest

@luis5tb
Copy link
Contributor

luis5tb commented May 5, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 5, 2020
@dulek
Copy link
Contributor

dulek commented May 5, 2020

/approve

@MaysaMacedo
Copy link
Contributor Author

/assign @squeed

savedOctaviaVersion := semver.MustParse(octaviaVersion)
multipleListenersVersion := semver.MustParse(MinOctaviaVersionWithMultipleListeners)
if !savedOctaviaVersion.Equal(maxOctaviaVersion) && savedOctaviaVersion.LessThan(multipleListenersVersion) && octaviaMultipleListenersSupport {
dnsService := &v1.Service{
Copy link
Contributor

Choose a reason for hiding this comment

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

Will this cause disruption to the cluster?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It will cause a small downtime of few seconds on the DNS resolution, as a new load balancer with the double listeners is getting created. After the load balancer is in place, the cluster should work normally.

Copy link
Contributor

Choose a reason for hiding this comment

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

with amphora octavia driver I would say not just a few seconds, but around a minute. Note though this only happens upon OpenStack octavia upgrade between octavia version not supporting UDP to the one supporting it -- on the same port as the TCP one.

Copy link
Contributor

Choose a reason for hiding this comment

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

That is... a bit concerning. What are the end-user expectations around this upgrade?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The path for Octavia upgrade from version 13 to 16 is still in progress.
Octavia team suggestion for the problem being solved here is to make the operator open a support ticket requesting for the upgrade of a Load Balancer. However, we can't rely on that as our approach for enforcing DNS resolution over TCP would be gone as soon as the upgrade happens.

We expect to work on other approaches for this solution to make it more ideal in following releases.

@luis5tb
Copy link
Contributor

luis5tb commented May 19, 2020

/test e2e-gcp-ovn

@squeed
Copy link
Contributor

squeed commented May 19, 2020

/override ci/prow/e2e-gcp-ovn
(Because this is an Octavia change)

@openshift-ci-robot
Copy link
Contributor

@squeed: Overrode contexts on behalf of squeed: ci/prow/e2e-gcp-ovn

In response to this:

/override ci/prow/e2e-gcp-ovn
(Because this is an Octavia 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 kubernetes/test-infra repository.

@knobunc
Copy link
Contributor

knobunc commented May 20, 2020

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dulek, knobunc, luis5tb, MaysaMacedo

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 20, 2020
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@MaysaMacedo
Copy link
Contributor Author

/hold
Let me just perform one last test prior to merging it.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 20, 2020
@MaysaMacedo
Copy link
Contributor Author

/hold cancel

@openshift-ci-robot openshift-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 27, 2020
@luis5tb
Copy link
Contributor

luis5tb commented May 27, 2020

/test e2e-gcp

1 similar comment
@MaysaMacedo
Copy link
Contributor Author

/test e2e-gcp

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 47490e0 into openshift:master May 27, 2020
@openshift-ci-robot
Copy link
Contributor

@MaysaMacedo: All pull requests linked via external trackers have merged: openshift/cluster-network-operator#607. Bugzilla bug 1829233 has been moved to the MODIFIED state.

In response to this:

Bug 1829233: Recreate DNS service upon Octavia upgrade

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.

@MaysaMacedo MaysaMacedo deleted the delete-dns-svc-on-upgrade branch May 27, 2020 18:52
@MaysaMacedo
Copy link
Contributor Author

/cherry-pick release-4.4

@openshift-cherrypick-robot

@MaysaMacedo: #607 failed to apply on top of branch "release-4.4":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	bindata/network/kuryr/003-config.yaml
M	pkg/platform/openstack/kuryr_bootstrap.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/platform/openstack/kuryr_bootstrap.go
CONFLICT (content): Merge conflict in pkg/platform/openstack/kuryr_bootstrap.go
Auto-merging bindata/network/kuryr/003-config.yaml
Patch failed at 0001 Recreate DNS service upon Octavia upgrade

In response to this:

/cherry-pick release-4.4

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
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants