So, I just got the same error referred to in this post (from June 25th) -> https://pulumi-community.slack.com/archives/CRH5ENVDX/p1719318472402359

$ pulumi version
v3.122.0

I had previously executed this command:

$ pulumi up --parallel 35 --fully-qualify-stack-names --show-replacement-steps --continue-on-error --stack stage1

And I fully expected some errors (which I got), due to some existing resources, but the resources I expected to be created were. However, I made no other changes and re-ran the command, and got this:

$ pulumi up --parallel 35 --fully-qualify-stack-names --show-replacement-steps --continue-on-error --stack stage1

error: could not deserialize deployment: snapshot integrity failure; refusing to use it: child resource urn:pulumi:stage1::infra::aws:lb:ApplicationLoadBalancer$aws:route53/record:Record$aws:acm/certificate:Certificate::<http://xxx.yyy.mydomain.com|xxx.yyy.mydomain.com> refers to missing parent urn:pulumi:stage1::infra::aws:lb:ApplicationLoadBalancer$aws:route53/record:Record::<http://xxx.yyy.mydomain.com|xxx.yyy.mydomain.com>

Hi, thanks for reporting this and sorry about the trouble. This definitely looks like a bug on our side. I'll open an issue, and we'll make sure to prioritize it. To unblock you, you should be able to run your pulumi command with

--disable-integrity-checking

in the meantime. Also another question, just to double check a theory I have. Is

urn:pulumi:stage1::infra::aws:lb:ApplicationLoadBalancer$aws:route53/record:Record::xxx.yyy.mydomain.com

one of the resources that previously failed to be created?

Also another question, just to double check a theory I have. Is

urn:pulumi:stage1::infra::aws:lb:ApplicationLoadBalancer$aws:route53/record:Record::<http://xxx.yyy.mydomain.com|xxx.yyy.mydomain.com>

one of the resources that previously failed to be created? (edited)

@steep-pager-59220 - yes, I believe so (need to go back and double check logs). By using the flag, I was able to do a

pulumi refresh ...

and "recover" state.

Glad to hear you were able to recover from the issue. Pulumi 3.124.0 should fix the issue for good.