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

OCPBUGS-29895: PowerVS: Add debugging to ServiceInstanceNameToGUID #8058

Conversation

hamzy
Copy link
Contributor

@hamzy hamzy commented Feb 23, 2024

A user noticed on delete cluster that the IPI generated service instance was not cleaned up. Add more debugging statements to find out why.

@hamzy
Copy link
Contributor Author

hamzy commented Feb 23, 2024

@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.

@r4f4
Copy link
Contributor

r4f4 commented Feb 23, 2024

@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.

@hamzy
Copy link
Contributor Author

hamzy commented Feb 23, 2024

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?

pkg/destroy/powervs/powervs.go Show resolved Hide resolved
pkg/destroy/powervs/powervs.go Outdated Show resolved Hide resolved
pkg/destroy/powervs/powervs.go Show resolved Hide resolved
@r4f4
Copy link
Contributor

r4f4 commented Feb 23, 2024

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 hamzy changed the title PowerVS: Add debugging to ServiceInstanceNameToGUID OCPBUGS-29895: PowerVS: Add debugging to ServiceInstanceNameToGUID Feb 23, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low 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 Feb 23, 2024
@openshift-ci-robot
Copy link
Contributor

@hamzy: This pull request references Jira Issue OCPBUGS-29895, which is invalid:

  • expected the bug to target the "4.16.0" version, but no target version was set

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:

A user noticed on delete cluster that the IPI generated service instance was not cleaned up. Add more debugging statements to find out why.

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.

@hamzy
Copy link
Contributor Author

hamzy commented Feb 23, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 23, 2024
@openshift-ci-robot
Copy link
Contributor

@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
  • bug is open, matching expected state (open)
  • bug target version (4.16.0) matches configured target version for branch (4.16.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @gpei

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from gpei February 23, 2024 20:00
@hamzy hamzy force-pushed the PowerVS-debug-ServiceInstanceNameToGUID branch from 339c5ec to 22bc009 Compare February 26, 2024 20:34
A user noticed on delete cluster that the IPI generated service
instance was not cleaned up.  Add more debugging statements to
find out why.
@hamzy hamzy force-pushed the PowerVS-debug-ServiceInstanceNameToGUID branch from 22bc009 to 11d4ab8 Compare February 26, 2024 20:48
Copy link
Contributor

@r4f4 r4f4 left a comment

Choose a reason for hiding this comment

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

/approve

Copy link
Contributor

openshift-ci bot commented Feb 26, 2024

[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 /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 Feb 26, 2024
@mjturek
Copy link
Contributor

mjturek commented Feb 26, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9978285 and 2 for PR HEAD 11d4ab8 in total

Copy link
Contributor

openshift-ci bot commented Feb 26, 2024

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit 51ee838 into openshift:master Feb 26, 2024
21 checks passed
@openshift-ci-robot
Copy link
Contributor

@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:

A user noticed on delete cluster that the IPI generated service instance was not cleaned up. Add more debugging statements to find out why.

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.

@hamzy
Copy link
Contributor Author

hamzy commented Feb 26, 2024

/cherry-pick release-4.15

@openshift-cherrypick-robot

@hamzy: new pull request created: #8065

In response to this:

/cherry-pick release-4.15

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

[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.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.16.0-0.nightly-2024-02-29-062601

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-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants