-
Story
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
None
User Story:
As a user of HyperShift, I would like the error handling to be improved when deleting an Azure HC and there is no resource group. Currently this is what happens:
% ./bin/hypershift destroy cluster azure --name $CLUSTER_NAME --azure-creds $AZURE_CREDS2024-01-12T08:45:28-05:00 INFO Found hosted cluster {"namespace": "clusters", "name": "brcox-hypershift-arm"}2024-01-12T08:45:28-05:00 INFO Deleting hosted cluster {"namespace": "clusters", "name": "brcox-hypershift-arm"}2024-01-12T08:45:28-05:00 INFO Using credentials from file {"path": "/Users/brcox/.azure/credentials"}2024-01-12T08:45:29-05:00 ERROR Failed to destroy cluster {"error": "failed to start deletion: DELETE https://management.azure.com/subscriptions/5f99720c-6823-4792-8a28-69efb0719eea/resourcegroups/brcox-hypershift-arm-brcox-hypershift-arm-8rc5r\n--------------------------------------------------------------------------------\nRESPONSE 404: 404 Not Found\nERROR CODE: ResourceGroupNotFound\n--------------------------------------------------------------------------------\n{\n \"error\": {\n \"code\": \"ResourceGroupNotFound\",\n \"message\": \"Resource group 'brcox-hypershift-arm-brcox-hypershift-arm-8rc5r' could not be found.\"\n }\n}\n--------------------------------------------------------------------------------\n"}github.com/openshift/hypershift/cmd/cluster/azure.NewDestroyCommand.func1 /Users/brcox/bryan-cox/hypershift/cmd/cluster/azure/destroy.go:46github.com/spf13/cobra.(*Command).execute /Users/brcox/bryan-cox/hypershift/vendor/github.com/spf13/cobra/command.go:987github.com/spf13/cobra.(*Command).ExecuteC /Users/brcox/bryan-cox/hypershift/vendor/github.com/spf13/cobra/command.go:1115github.com/spf13/cobra.(*Command).Execute /Users/brcox/bryan-cox/hypershift/vendor/github.com/spf13/cobra/command.go:1039github.com/spf13/cobra.(*Command).ExecuteContext /Users/brcox/bryan-cox/hypershift/vendor/github.com/spf13/cobra/command.go:1032main.main /Users/brcox/bryan-cox/hypershift/main.go:78runtime.main /usr/local/go/src/runtime/proc.go:267
Acceptance Criteria:
Description of criteria:
- Upstream documentation
- Point 1
- Point 2
- Point 3
(optional) Out of Scope:
Detail about what is specifically not being delivered in the story
Engineering Details:
- (optional) https://github/com/link.to.enhancement/
- (optional) https://issues.redhat.com/link.to.spike
- Engineering detail 1
- Engineering detail 2
This requires/does not require a design proposal.
This requires/does not require a feature gate.