This message was deleted.

sparse-intern-71089

07/10/2018, 8:10 PM

This message was deleted.

stocky-spoon-28903

07/10/2018, 8:11 PM

Doing a

pulumi destroy

results in the same error message when it fails to load the plugin:

Copy code

error: failed to load resource plugin aws: failed to perform plugin load callback: failed to save snapshot: after mutation of snapshot: resource urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::operator-error:aws:Vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation::demo-public-rta-1 dependency urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::aws:ec2/vpc:Vpc$aws:ec2/routeTable:RouteTable::demo-public-rt refers to missing resource

microscopic-florist-22719

07/10/2018, 9:34 PM

This gets a bit gross: you're going to need to export the stack's checkpoint, edit it manually to remove the offending dependency, and import the repaired checkpoint.

microscopic-florist-22719

07/10/2018, 9:35 PM

The export is performed by incanting

pulumi stack export

. This will dump the checkpoint to

stdout

, so you'll want to redirect to a file.

microscopic-florist-22719

07/10/2018, 9:36 PM

The checkpoint is exported as JSON, so I usually do something like

$ pulumi stack export > d.json

microscopic-florist-22719

07/10/2018, 9:38 PM

Once you have the exported checkpoint in hand, it is probably sufficient to search for

urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::aws:ec2/vpc:Vpc$aws:ec2/routeTable:RouteTable::demo-public-rt

. If my guess is correct (and it certainly may not be), you'll find a single reference to this resource in the dependency list for

urn:pulumi:pulumi-subnets-test-dev::pulumi-subnets-test::operator-error:aws:Vpc$aws:ec2/vpc:Vpc$aws:ec2/subnet:Subnet$aws:ec2/routeTableAssociation:RouteTableAssociation::demo-public-rta-1

. You'll need to delete that reference from the list.

microscopic-florist-22719

07/10/2018, 9:38 PM

Once the delete is finished, you can import the repaired checkpoint using

$ pulumi stack import < repaired.json

microscopic-florist-22719

07/10/2018, 9:38 PM

I'd recommend saving the original, invalid checkpoint just in case of further disaster.

microscopic-florist-22719

07/10/2018, 9:39 PM

(it would also be helpful if you can share it with myself or @white-balloon-205 via DM)

microscopic-florist-22719

07/10/2018, 11:34 PM

cc @bitter-oil-46081 who has hit this recently and may also be able to help

bitter-oil-46081

07/10/2018, 11:41 PM

In my case I ran into this when trying to create a RolePolicyAttachment, using an

aws.iam.Role

that I obtained via

aws.iam.Role.get

. Since this resource was "read" it is not in the checkpoint. Presumably https://github.com/pulumi/pulumi/issues/1521 when fixed will address my case.

bitter-oil-46081

07/10/2018, 11:55 PM

In my case I was able to "recover" by exporting the checkpoint with

pulumi stack export

, hand editing to remove the bogus URN from the list of dependencies, and then import it and run my program again, after editing it so I didn't immediately fall into this case again.

stocky-spoon-28903

07/11/2018, 12:38 AM

Ah, that makes sense. In this case the offending item was the default route table of a VPC

stocky-spoon-28903

07/11/2018, 12:38 AM

I’ll try exporting and manually editing the checkpoint

9 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.