https://pulumi.com logo
#general
Title
# general
c

cool-egg-852

06/05/2019, 4:57 PM
Any idea what to do when this happens? We got the first error, and then when running up again, we got the second.
Copy code
~   └─ gcp:container:Cluster         gke                     updated     [diff: ~addonsConfig]
panic: fatal: An assertion has failed

goroutine 535 [running]:
<http://github.com/pulumi/pulumi/pkg/util/contract.failfast(...)|github.com/pulumi/pulumi/pkg/util/contract.failfast(...)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/pkg/util/contract.Assert(...)|github.com/pulumi/pulumi/pkg/util/contract.Assert(...)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:26
<http://github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).mustWrite(0xc000010470|github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).mustWrite(0xc000010470>, 0xc000a6a9a0, 0xc0006607e0, 0xc0003e1f60)
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:192 +0x3f4
<http://github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).End.func1(0xc0003e1f60)|github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).End.func1(0xc0003e1f60)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:237 +0xd0
<http://github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager.func1(0xc0019f18c0|github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager.func1(0xc0019f18c0>, 0xc001a21600, 0xc0019f1920, 0xc0019f1980)
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:564 +0x108
created by <http://github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager|github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:554 +0x150
error: [409] Conflict: Another update is currently in progress.
w

white-balloon-205

06/05/2019, 4:58 PM
What Pulumi cli version were you running? You should be able to
Pulumi cancel
to address the second issue. But would love to understand what caused the first.
c

cool-egg-852

06/05/2019, 5:01 PM
0.17.15
w

white-balloon-205

06/05/2019, 5:05 PM
If you are still seeing this after cancel - you could try downgrading to 0.17.14 as a workaround. I opened https://github.com/pulumi/pulumi/issues/2804 to investigate the assert.
c

cool-egg-852

06/05/2019, 5:06 PM
I’m trying it on a different stack (same project) right now. I’m curious to see if it fails as well.
The issue didn’t happen on the stack. So we shall see as I have 4 stacks to go through in total, and I’ll circle back to the one that had an issue.
b

bitter-oil-46081

06/06/2019, 12:19 AM
FWIW, @cool-egg-852 We pushed a change that we believe should address the issue. You can install a dev version of the CLI with the following gesture:
curl <https://get.pulumi.com/> | bash -s -- --version 0.17.16-dev.1559777246
But we plan to release a 0.17.16 shortly with the fix. Would be great to know if that ends up addressing your issue.
c

cool-egg-852

06/06/2019, 12:29 AM
I was never able to reproduce it so I can’t really test.
b

bitter-oil-46081

06/06/2019, 5:34 PM
I was never able to reproduce it so I can’t really test.
Okay, thanks.