[release-4.19] OCPBUGS-58073: Refactor removing loadbalancer in OpenStack.#9808
Conversation
Currently, the approach for removing OpenStack loadbalancers is to look for appropriate tag (i.e. openshiftClusterID=<cluster_id>) and then delete it. Issue with this approach is that no such tags are applied on the loadbalancer resources, and also there is no such tag in description field. Hence, deleteLoadBalancer function will give 0 results for existing loadbalancers, as they have no such tag either in tags nor on description. With this patch, deleteLoadBalancer has been refactored to get all the loadbalancers and filter out that resources which have ClusterID in description, so that they will be safely deleted.
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-18510 has been cloned as Jira Issue OCPBUGS-58073. Will retitle bug to link to clone. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-58073, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tthvo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/jira refresh |
|
@gryf: An error was encountered updating to the POST state for bug OCPBUGS-58073 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
It seems that you have tried to perform a workflow operation (POST) that is not valid for the current state of this issue (OCPBUGS-58073). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.: request failed. Please analyze the request body for more details. Status code: 400:
Please contact an administrator to resolve this issue, then request a bug refresh with DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@gryf: This pull request references Jira Issue OCPBUGS-58073, which is valid. 7 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (itbrown@redhat.com), skipping review request. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/lgtm |
|
/label backport-risk-assessed |
|
/cc @gpei |
|
/label cherry-pick-approved |
|
/retest-required |
|
@openshift-cherrypick-robot: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
c2a0bea
into
openshift:release-4.19
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-58073: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-58073 has been moved to the MODIFIED state. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
@openshift-cherrypick-robot: #9808 failed to apply on top of branch "release-4.18": DetailsIn response to this:
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-sigs/prow repository. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer |
|
[ART PR BUILD NOTIFIER] Distgit: ose-baremetal-installer |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-artifacts |
|
Fix included in accepted release 4.19.0-0.nightly-2025-07-08-172809 |
This is an automated cherry-pick of #9724
/assign gryf
/cherrypick release-4.18 release-4.17 release-4.16 release-4.15 release-4.14