Skip to content

[release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic#771

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.9from
openshift-cherrypick-robot:cherry-pick-729-to-release-4.9
Jun 8, 2022
Merged

[release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic#771
openshift-merge-robot merged 1 commit intoopenshift:release-4.9from
openshift-cherrypick-robot:cherry-pick-729-to-release-4.9

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #729

/assign gcs278

Delete the deletion logic for the "ingress.openshift.io/operator" finalizer
for LoadBalancer-type services.  This finalizer has not been needed since
OpenShift 4.2, when the DNSRecord CRD was added.  OpenShift 4.8 removed the
logic that added the finalizer and added logic to remove the finalizer.
Thus with OpenShift versions after OpenShift 4.8, this finalizer no longer
exists, and the corresponding logic can be deleted.

Follow-up to commit 081081a.

This commit fixes bug 2069457.

https://bugzilla.redhat.com/show_bug.cgi?id=2069457

* pkg/manifests/manifests.go (LoadBalancerServiceFinalizer): Delete const.
* pkg/operator/controller/ingress/controller.go (ensureIngressDeleted):
Delete calls to finalizeLoadBalancerService.
* pkg/operator/controller/ingress/load_balancer_service.go
(ensureLoadBalancerService): Delete calls to deleteLoadBalancerService.
(deleteLoadBalancerService, finalizeLoadBalancerService): Delete methods.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2022

@openshift-cherrypick-robot: Bugzilla bug 2069457 has been cloned as Bugzilla bug 2094054. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic

Details

In response to this:

[release-4.9] Bug 2069457: Delete LoadBalancer-type service finalizer logic

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 openshift-ci bot changed the title [release-4.9] Bug 2069457: Delete LoadBalancer-type service finalizer logic [release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic Jun 6, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 6, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2094054, which is invalid:

  • expected dependent Bugzilla bug 2069457 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

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

Details

In response to this:

[release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic

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 openshift-ci bot requested review from lmzuccarelli and rfredette June 6, 2022 17:22
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2022

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@Miciah Miciah added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 6, 2022
@Miciah
Copy link
Contributor

Miciah commented Jun 6, 2022

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 6, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 6, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Miciah, openshift-cherrypick-robot

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

The pull request process is described here

Details 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 Jun 6, 2022
@openshift-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2022

@openshift-bot: This pull request references Bugzilla bug 2094054, which is invalid:

  • expected dependent Bugzilla bug 2069457 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

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

Details

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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-bot
Copy link
Contributor

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2022

@openshift-bot: This pull request references Bugzilla bug 2094054, which is invalid:

  • expected dependent Bugzilla bug 2069457 to target a release in 4.10.0, 4.10.z, but it targets "4.11.0" instead

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

Details

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

@lihongan
Copy link
Contributor

lihongan commented Jun 8, 2022

/bugzilla refresh

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jun 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2022

@lihongan: This pull request references Bugzilla bug 2094054, 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.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.z) matches configured target release for branch (4.9.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2082161 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2082161 targets the "4.10.z" release, which is one of the valid target releases: 4.10.0, 4.10.z
  • bug has dependents

Requesting review from QA contact:
/cc @lihongan

Details

In response to this:

/bugzilla refresh

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 openshift-ci bot requested a review from lihongan June 8, 2022 01:44
@lihongan
Copy link
Contributor

lihongan commented Jun 8, 2022

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jun 8, 2022
@lihongan
Copy link
Contributor

lihongan commented Jun 8, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 8, 2022
@openshift-merge-robot openshift-merge-robot merged commit b59abfc into openshift:release-4.9 Jun 8, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2094054 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.9] Bug 2094054: Delete LoadBalancer-type service finalizer logic

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-low Referenced Bugzilla bug's severity is low 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants