Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--target leads to "snapshot integrity failure; refusing to use it" error #15959

Open
blampe opened this issue Apr 17, 2024 · 1 comment
Open
Assignees
Labels
impact/snapshot-integrity Snapshot integrity failure kind/bug Some behavior is incorrect or out of spec p1 Bugs severe enough to be the next item assigned to an engineer
Milestone

Comments

@blampe
Copy link
Contributor

blampe commented Apr 17, 2024

What happened?

I ran pulumi up --target 'urn:...::aws:ecs/service:Service::ratelimit-' --target-dependents.

The preview correctly identified the resource as being deleted, but the actual up returned an error for unrelated resources:

error: could not deserialize deployment: snapshot integrity failure; refusing to use it: resource urn:...::aws:ecs/taskDefinition:TaskDefinition::consoleTaskDefinition’s dependency urn:...::pulumi-service:infrastructure:Service$docker:buildx/image:Index::consoleImage comes after it

Subsequent ups had the same error.

I was eventually able to get past this with up --disable-integrity-checking -- once that succeeded everything worked as normal again.

Example

Steps:

Output of pulumi about

CLI
Version 3.113.0
Go Version go1.22.2
Go Compiler gc

Host
OS darwin
Version 14.1
Arch arm64

Backend
Name pulumi.com
URL https://app.pulumi.com/bryce-pulumi-corp
User bryce-pulumi-corp
Organizations bryce-pulumi-corp, pulumi
Token type personal

Additional context

Both resources have retainOnDelete set.

The targeted resource was expected to be deleted, because I had replaced it with a different type/provider in my program.

I exported a state file shortly before running the update with --target, so it might be possible to repo using that. Ping me and I can send it over.

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@blampe blampe added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Apr 17, 2024
@justinvp justinvp added impact/snapshot-integrity Snapshot integrity failure p1 Bugs severe enough to be the next item assigned to an engineer and removed needs-triage Needs attention from the triage team labels Apr 18, 2024
@justinvp justinvp added this to the 0.103 milestone Apr 19, 2024
@1oglop1
Copy link

1oglop1 commented May 1, 2024

I have the same problem, but different resources

const users = ['u1', 'u2']
const iamUsers = usersNames.map( u => new aws.iam.User(u, {name: u}))

// note this is not UserPolicy because it has already been attached
new aws.iam.PolicyAttachment(
  "self-management",
  {
    policyArn: selfManagePolicy.arn,
    users: iamUsers.map((u) => u.name),
  },
  {
    provider: awsFrankfurt,
  }
);

pulumi up --target '**u1**' --target-dependents won't update self-management

CLI          
Version      3.112.0
Go Version   go1.22.1
Go Compiler  gc

Plugins
NAME     VERSION
aws      6.31.0
command  0.10.0
nodejs   unknown

@justinvp justinvp modified the milestones: 0.103, 0.104 May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact/snapshot-integrity Snapshot integrity failure kind/bug Some behavior is incorrect or out of spec p1 Bugs severe enough to be the next item assigned to an engineer
Projects
None yet
Development

No branches or pull requests

4 participants