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

[release-ocm-2.8] OCPBUGS-15813: Fix singular Ingress and API cluster VIPs removal #5337

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #5216

/assign nmagnezi

This change fixes a case where the user attempts to remove Ingress and API VIPs.
Cleanup used to fail due to a missing deletion as a part of the deletion db transaction.

Added unit tests to verify all deletion combination works for
singular, plural, and a combination of VIP params.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-13621 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

In response to this:

This is an automated cherry-pick of #5216

/assign nmagnezi

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 jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 5, 2023
@openshift-ci-robot
Copy link

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-13621, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
  • expected Jira Issue OCPBUGS-13621 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-13621 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

In response to this:

This is an automated cherry-pick of #5216

/assign nmagnezi

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.

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 added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 5, 2023
@openshift-ci openshift-ci bot requested review from eliorerz and gamli75 July 5, 2023 13:44
@nmagnezi
Copy link
Contributor

nmagnezi commented Jul 5, 2023

/retitle [release-ocm-2.8] OCPBUGS-15813: Fix singular Ingress and API cluster VIPs removal

@openshift-ci openshift-ci bot changed the title [release-ocm-2.8] OCPBUGS-13621: Fix singular Ingress and API cluster VIPs removal [release-ocm-2.8] OCPBUGS-15813: Fix singular Ingress and API cluster VIPs removal Jul 5, 2023
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15813, which is invalid:

  • expected Jira Issue OCPBUGS-15813 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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:

This is an automated cherry-pick of #5216

/assign nmagnezi

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.

@codecov
Copy link

codecov bot commented Jul 5, 2023

Codecov Report

Merging #5337 (5343f64) into release-ocm-2.8 (5ca343d) will increase coverage by 0.00%.
The diff coverage is 62.96%.

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##           release-ocm-2.8    #5337   +/-   ##
================================================
  Coverage            67.52%   67.53%           
================================================
  Files                  218      218           
  Lines                32709    32731   +22     
================================================
+ Hits                 22088    22104   +16     
- Misses                8631     8638    +7     
+ Partials              1990     1989    -1     
Impacted Files Coverage Δ
internal/cluster/validations/validations.go 25.19% <ø> (+0.09%) ⬆️
internal/network/utils.go 28.90% <33.33%> (+0.21%) ⬆️
internal/bminventory/inventory.go 69.86% <86.66%> (-0.03%) ⬇️

... and 1 file with indirect coverage changes

@filanov filanov removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 5, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 5, 2023
@openshift-ci
Copy link

openshift-ci bot commented Jul 5, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jul 5, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 5ca343d and 2 for PR HEAD 5343f64 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 7e8f662 and 1 for PR HEAD 5343f64 in total

@openshift-ci
Copy link

openshift-ci bot commented Jul 6, 2023

@openshift-cherrypick-robot: all tests passed!

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.

@openshift-merge-robot openshift-merge-robot merged commit 91db753 into openshift:release-ocm-2.8 Jul 6, 2023
13 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-15813: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #5216

/assign nmagnezi

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-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2023-09-11-201102

@openshift-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2023-09-12-024050

@openshift-merge-robot
Copy link

Fix included in accepted release 4.14.0-0.nightly-2023-09-15-101929

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/severity-important Referenced Jira bug's severity is important 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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants