kubernetes/kops · error

waiting for disk deletion completion: %w

Error message

waiting for disk deletion completion: %w

What it means

PollUntilDone failed while waiting for the managed disk deletion LRO to complete; the delete request was accepted but the operation failed or polling broke.

Source

Thrown at upup/pkg/fi/cloudup/azure/disk.go:81

		if err != nil {
			var respErr *azcore.ResponseError
			if errors.As(err, &respErr) && respErr.ErrorCode == "ResourceGroupNotFound" {
				return nil, nil
			}
			return nil, fmt.Errorf("listing disks: %w", err)
		}
		l = append(l, resp.Value...)
	}
	return l, nil
}

func (c *disksClientImpl) Delete(ctx context.Context, resourceGroupName, diskName string) error {
	future, err := c.c.BeginDelete(ctx, resourceGroupName, diskName, nil)
	if err != nil {
		return fmt.Errorf("deleting disk: %w", err)
	}
	if _, err := future.PollUntilDone(ctx, nil); err != nil {
		return fmt.Errorf("waiting for disk deletion completion: %w", err)
	}
	return nil
}

func newDisksClientImpl(subscriptionID string, cred *azidentity.DefaultAzureCredential) (*disksClientImpl, error) {
	c, err := compute.NewDisksClient(subscriptionID, cred, nil)
	if err != nil {
		return nil, fmt.Errorf("creating disks client: %w", err)
	}
	return &disksClientImpl{
		c: c,
	}, nil
}

View on GitHub (pinned to 4c8573c808)

Solutions

1. Inspect the wrapped error for the ARM failure reason
2. Re-run the delete; disk deletion is idempotent
3. Check whether the disk is still attached to a VM (common cause of delete failures)

When it happens

Trigger: Thrown at upup/pkg/fi/cloudup/azure/disk.go:81 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of kubernetes/kops@4c8573c808 (2026-09-05). Data as JSON: /api/errors/2d532283de1fff31. Report an issue: GitHub.