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-4.14] OCPBUGS-22770: destroy: gcp: fix destroying regional disks #7657

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #7643

/assign r4f4

Regional disks are replicated in multiple zones but our logic was not
taking them into account, only zonal disks. When trying to run `cluster
destroy` in a cluster with regional disks, the following panic was
observed:

```
time="2023-07-25T10:02:16Z" level=debug msg="Found disk: pvc-c8cf8f18-cd22-441e-b47a-565bed5573ee in zone europe-west2-a"
time="2023-07-25T10:02:16Z" level=debug msg="Found disk: pvc-3e703665-2271-4c16-8bf8-533b5e7be444 in zone "
E0725 10:02:16.633982       1 runtime.go:79] Observed a panic: runtime.boundsError{x:-1, y:0, signed:true, code:0x1} (runtime error: slice bounds out of range [:-1])
goroutine 1 [running]:
[k8s.io/apimachinery/pkg/util/runtime.logPanic(
{0x7b0e040|http://k8s.io/apimachinery/pkg/util/runtime.logPanic(%7B0x7b0e040]?, 0xc00007dde8}

)
                k8s.io/apimachinery@v0.24.1/pkg/util/runtime/runtime.go:75 +0x99
[k8s.io/apimachinery/pkg/util/runtime.HandleCrash(
{0x0|http://k8s.io/apimachinery/pkg/util/runtime.HandleCrash(%7B0x0], 0x0, 0xc000120260?}
)
                k8s.io/apimachinery@v0.24.1/pkg/util/runtime/runtime.go:49 +0x75
panic({0x7b0e040, 0xc00007dde8})
                runtime/panic.go:884 +0x212
github.com/openshift/installer/pkg/destroy/gcp.getRegionFromZone(...)
                github.com/openshift/installer@v0.9.0-master.0.20220901213408-25aa6a41b7ca/pkg/destroy/gcp/gcp.go:204
github.com/openshift/installer/pkg/destroy/gcp.(*ClusterUninstaller).listDisksWithFilter.func1(0xc00165eec0?)
```

This fix includes logic to deal with finding the replicated zones and
deleting the disks in all of them.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-22489 has been cloned as Jira Issue OCPBUGS-22770. Will retitle bug to link to clone.
/retitle [release-4.14] OCPBUGS-22770: destroy: gcp: fix destroying regional disks

In response to this:

This is an automated cherry-pick of #7643

/assign r4f4

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 changed the title [release-4.14] OCPBUGS-22489: destroy: gcp: fix destroying regional disks [release-4.14] OCPBUGS-22770: destroy: gcp: fix destroying regional disks Oct 31, 2023
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate 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 Oct 31, 2023
@openshift-ci-robot
Copy link
Contributor

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

  • expected dependent Jira Issue OCPBUGS-22489 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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 #7643

/assign r4f4

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.

@r4f4
Copy link
Contributor

r4f4 commented Nov 20, 2023

/cherry-pick release-4.13

@openshift-cherrypick-robot
Copy link
Author

@r4f4: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.13

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.

@jianli-wei
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 27, 2023
@openshift-ci-robot
Copy link
Contributor

@jianli-wei: This pull request references Jira Issue OCPBUGS-22770, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-22489 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-22489 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianli-wei

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 kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 27, 2023
@r4f4
Copy link
Contributor

r4f4 commented Nov 27, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 27, 2023
@jianli-wei
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 27, 2023
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-22770, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-22489 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-22489 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @jianli-wei

In response to this:

This is an automated cherry-pick of #7643

/assign r4f4

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.

Copy link
Contributor

@barbacbd barbacbd 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 Nov 27, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd

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 Nov 27, 2023
@r4f4
Copy link
Contributor

r4f4 commented Nov 28, 2023

/assign @sadasu
for the backport label

@sadasu
Copy link
Contributor

sadasu commented Dec 13, 2023

/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 Dec 13, 2023
@gpei
Copy link
Contributor

gpei commented Dec 14, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Dec 14, 2023
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 619e87d and 2 for PR HEAD 166eef0 in total

Copy link
Contributor

openshift-ci bot commented Dec 14, 2023

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-ovn-shared-vpc 166eef0 link false /test e2e-gcp-ovn-shared-vpc
ci/prow/okd-scos-e2e-vsphere 166eef0 link false /test okd-scos-e2e-vsphere
ci/prow/okd-scos-e2e-gcp-ovn-upgrade 166eef0 link false /test okd-scos-e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-upgrade 166eef0 link false /test e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-gcp 166eef0 link false /test okd-scos-e2e-gcp
ci/prow/okd-e2e-aws-ovn-upgrade 166eef0 link false /test okd-e2e-aws-ovn-upgrade

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.

@r4f4
Copy link
Contributor

r4f4 commented Dec 14, 2023

/test okd-scos-images

@openshift-merge-bot openshift-merge-bot bot merged commit 5fd7986 into openshift:release-4.14 Dec 14, 2023
25 of 31 checks passed
@openshift-ci-robot
Copy link
Contributor

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

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

In response to this:

This is an automated cherry-pick of #7643

/assign r4f4

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-cherrypick-robot
Copy link
Author

@r4f4: new pull request created: #7840

In response to this:

/cherry-pick release-4.13

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-baremetal-installer-container-v4.14.0-202312141848.p0.g5fd7986.assembly.stream for distgit ose-baremetal-installer.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.14.0-0.nightly-2023-12-15-025512

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate 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. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants