-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
OCPBUGS-29895: PowerVS: Add debugging to ServiceInstanceNameToGUID #8058
OCPBUGS-29895: PowerVS: Add debugging to ServiceInstanceNameToGUID #8058
Conversation
@r4f4 What do you think about a PR that just adds debugging statements? Someone was verifying a previous PR and encountered a bug. Looking at the logs, I couldn't narrow it down to a clear failing condition. |
Not opposed to it but it would better if they could build a release from this PR without merging it if you don't intend for the debug logs to stay. |
I do intend the logs to stay in case similar problems surface in the future. I also plan on cherry picking it into 4.15. Does that sound reasonable? |
Then you'll need a bug for this PR. |
@hamzy: This pull request references Jira Issue OCPBUGS-29895, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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 |
@hamzy: This pull request references Jira Issue OCPBUGS-29895, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
339c5ec
to
22bc009
Compare
A user noticed on delete cluster that the IPI generated service instance was not cleaned up. Add more debugging statements to find out why.
22bc009
to
11d4ab8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: r4f4 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 |
/lgtm |
@hamzy: 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. |
@hamzy: Jira Issue OCPBUGS-29895: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-29895 has been moved to the MODIFIED state. In 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. |
/cherry-pick release-4.15 |
@hamzy: new pull request created: #8065 In 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/test-infra repository. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-installer-altinfra-container-v4.16.0-202402270439.p0.g51ee838.assembly.stream.el8 for distgit ose-installer-altinfra. |
Fix included in accepted release 4.16.0-0.nightly-2024-02-29-062601 |
A user noticed on delete cluster that the IPI generated service instance was not cleaned up. Add more debugging statements to find out why.