Skip to content

[release-4.10] BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention#820

Merged
openshift-merge-robot merged 1 commit intoopenshift:release-4.10from
gcs278:bz2094051-release4.10
Sep 22, 2022
Merged

[release-4.10] BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention#820
openshift-merge-robot merged 1 commit intoopenshift:release-4.10from
gcs278:bz2094051-release4.10

Conversation

@gcs278
Copy link
Contributor

@gcs278 gcs278 commented Aug 26, 2022

This is an manual cherry-pick of #707 due to merge conflicts for the release-4.10 branch.

Merge Conflicts:
[gspence@gspence cluster-ingress-operator]$ git cherry-pick dba837a

Auto-merging test/e2e/operator_test.go
CONFLICT (content): Merge conflict in test/e2e/operator_test.go
Auto-merging pkg/operator/controller/ingress/load_balancer_service_test.go
CONFLICT (content): Merge conflict in pkg/operator/controller/ingress/load_balancer_service_test.go
Auto-merging pkg/operator/controller/ingress/load_balancer_service.go

test/e2e/operator_test.go:

  • TestTunableRouterKubeletProbesForDefaultIngressController and TestTunableRouterKubeletProbesForCustomIngressController moved/removed while I added TestIngressControllerServiceNameCollision right next to them

pkg/operator/controller/ingress/load_balancer_service_test.go

  • Added TestServiceIngressOwner and conflicted with existing TestLoadBalancerServiceAnnotationsChanged

/assign gcs278

@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high 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 Aug 26, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 26, 2022

@gcs278: This pull request references Bugzilla bug 2094051, 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.10.z) matches configured target release for branch (4.10.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2054200 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2054200 targets the "4.11.0" release, which is one of the valid target releases: 4.11.0, 4.11.z
  • bug has dependents

Requesting review from QA contact:
/cc @quarterpin

Details

In response to this:

BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention

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.

@Miciah
Copy link
Contributor

Miciah commented Aug 31, 2022

/assign

@candita
Copy link
Contributor

candita commented Aug 31, 2022

/assign

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2022

@gcs278: This pull request references Bugzilla bug 2094051, which is valid.

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

Requesting review from QA contact:
/cc @quarterpin

Details

In response to this:

BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention

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.

@gcs278 gcs278 force-pushed the bz2094051-release4.10 branch from 4b257b9 to dfe06ae Compare August 31, 2022 18:27
@candita
Copy link
Contributor

candita commented Aug 31, 2022

Looks identical to previous PR
/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 31, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: candita

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 Aug 31, 2022
@candita
Copy link
Contributor

candita commented Sep 1, 2022

/retest-required

@quarterpin
Copy link

/label qe-approved
/label cherry-pick-approved

Verified via pre-merge workflow, for more details : https://bugzilla.redhat.com/show_bug.cgi?id=2094051#c2

@openshift-ci openshift-ci bot added qe-approved Signifies that QE has signed off on this PR cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Sep 5, 2022
@gcs278
Copy link
Contributor Author

gcs278 commented Sep 12, 2022

Thanks, needs a lgtm from @candita or @Miciah

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 12, 2022

@gcs278: This pull request references Bugzilla bug 2094051, which is valid.

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

Requesting review from QA contact:
/cc @quarterpin

Details

In response to this:

BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention

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.

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 21, 2022

/retest

if actual := isServiceOwnedByIngressController(tc.service, ic); actual != tc.expect {
t.Errorf("expected ownership %t got %t", tc.expect, actual)
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

has an extra newline here. Any reason it's absent from this backport? Are we going to delete the newline in the main branch?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Wow good eye. Yea this was collateral damage from the merge. I'll fix real quick.

@Miciah
Copy link
Contributor

Miciah commented Sep 21, 2022

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 21, 2022
@gcs278 gcs278 force-pushed the bz2094051-release4.10 branch from dfe06ae to e0df790 Compare September 21, 2022 21:04
@gcs278
Copy link
Contributor Author

gcs278 commented Sep 22, 2022

/retest

@gcs278
Copy link
Contributor Author

gcs278 commented Sep 22, 2022

/retitle [release-4.10] BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention

@openshift-ci openshift-ci bot changed the title BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention [release-4.10] BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention Sep 22, 2022
@Miciah
Copy link
Contributor

Miciah commented Sep 22, 2022

Thanks!
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2022
@openshift-merge-robot openshift-merge-robot merged commit b1a3bc3 into openshift:release-4.10 Sep 22, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 22, 2022

@gcs278: All pull requests linked via external trackers have merged:

Bugzilla bug 2094051 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.10] BUG 2094051: Fix removing custom created service in openshift-ingress with same naming convention

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-high Referenced Bugzilla bug's severity is high 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.

8 participants