handsome-rainbow-9879106/02/2022, 11:19 PM
$ pulumi destroy git:peer_to_rds* Previewing destroy (ironnetcybersecurity/jcc) View Live: <https://app.pulumi.com/ironnetcybersecurity/salamander/jcc/previews/7ac2218e-7bbe-4d24-9f10-27a93537ba82> Do you want to perform this destroy? yes Destroying (ironnetcybersecurity/jcc) View Live: <https://app.pulumi.com/ironnetcybersecurity/salamander/jcc/updates/114> Type Name Status Info pulumi:pulumi:Stack salamander-jcc **failed** 1 error; 1 warning - └─ kubernetes:core/v1:Namespace global-services **deleting failed** 1 error Diagnostics: pulumi:pulumi:Stack (salamander-jcc): warning: Attempting to deploy or update resources with 1 pending operations from previous deployment. * urn:pulumi:jcc::salamander::kubernetes:core/v1:Namespace::global-services, interrupted while deleting These resources are in an unknown state because the Pulumi CLI was interrupted while waiting for changes to these resources to complete. You should confirm whether or not the operations listed completed successfully by checking the state of the appropriate provider. For example, if you are using AWS, you can confirm using the AWS Console. Once you have confirmed the status of the interrupted operations, you can repair your stack using 'pulumi refresh' which will refresh the state from the provider you are using and clear the pending operations if there are any. Note that 'pulumi refresh' will not clear pending CREATE operations since those could have resulted in resources which are not tracked by pulumi. To repair the stack and remove pending CREATE operation, use 'pulumi stack export' which will export your stack to a file. For each operation that succeeded, remove that operation from the "pending_operations" section of the file. Once this is complete, use 'pulumi stack import' to import the repaired stack. error: update failed kubernetes:core/v1:Namespace (global-services): error: Timeout occurred polling for 'global-services' $ pulumi cancel git:peer_to_rds* This will irreversibly cancel the currently running update for 'jcc'! Please confirm that this is what you'd like to do by typing ("jcc"): jcc error:  Conflict: The Update has already completed $ pulumi refresh
little-cartoon-1056906/02/2022, 11:21 PM
isn't fixing this, you'll need to resolve it manually. Export your stack, delete your pending operations, import it again.
, Delete that copy.
handsome-rainbow-9879106/02/2022, 11:26 PM
I’ve already tried to delete the individual resources inside of my state, but it doesn’t find some of the resources it says it is trying to delete
blue ➤ pulumi stack export | grep "deleted" git:peer_to_rds* blue ➤ pulumi stack export | grep "pending" git:peer_to_rds* "acceptStatus": "pending-acceptance",
Diagnostic: kubernetes:core/v1:ConfigMap (grampus-cluster-nodeAccess): warning: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: Get "<https://C1143BA1BB162FB02862B32FB3AF21B0.yl4.us-west-1.eks.amazonaws.com/openapi/v2?timeout=32s>": dial tcp: lookup <http://C1143BA1BB162FB02862B32FB3AF21B0.yl4.us-west-1.eks.amazonaws.com|C1143BA1BB162FB02862B32FB3AF21B0.yl4.us-west-1.eks.amazonaws.com> on 10.40.13.197:53: no such host error: Preview failed: failed to read resource state due to unreachable cluster. If the cluster has been deleted, you can edit the pulumi state to remove this resource error: No such resource "urn:pulumi:jcc::salamander::eks:index:Clusterore/v1:ConfigMap::grampus-cluster-nodeAccess" exists in the current state
little-cartoon-1056906/02/2022, 11:27 PM
pulumi state delete
is easier 🙂 )
pulumi state delete
handsome-rainbow-9879106/02/2022, 11:27 PM
blue ➤ pulumi state delete -y urn:pulumi:jcc::salamander::eks:index:Cluster$kubernetes:core/v1:ConfigMap::grampus-cluster-nodeAccess git:peer_to_rds* error: No such resource "urn:pulumi:jcc::salamander::eks:index:Clusterore/v1:ConfigMap::grampus-cluster-nodeAccess" exists in the current state
little-cartoon-1056906/02/2022, 11:30 PM
handsome-rainbow-9879106/02/2022, 11:34 PM
little-cartoon-1056906/02/2022, 11:35 PM
handsome-rainbow-9879106/02/2022, 11:37 PM
little-cartoon-1056906/02/2022, 11:37 PM
will do the rest.
handsome-rainbow-9879106/02/2022, 11:38 PM
little-cartoon-1056906/02/2022, 11:58 PM
to identify a problem (which was always, Pulumi thought resource X existed but really it didn't). 2. If there wasn't a problem, run
and end. 3. Else delete the problem resource(s) from state (
). 4. Go to 1.
pulumi state delete...
handsome-rainbow-9879106/03/2022, 5:09 PM
little-cartoon-1056906/05/2022, 11:49 PM