After upgrading to Pulumi

3.32.0

, I just got this error:

panic: fatal: An assertion has failed: action must be non empty

goroutine 2009 [running]:
<http://github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.failfast(...)|github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.failfast(...)>
	/private/tmp/pulumi-20220504-79959-1budjvw/sdk/go/common/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.Assertf|github.com/pulumi/pulumi/sdk/v3/go/common/util/contract.Assertf>(0x0?, {0x1053aa67e?, 0x140010182d0?}, {0x0?, 0x10537c4e7?, 0x3?})
	/private/tmp/pulumi-20220504-79959-1budjvw/sdk/go/common/util/contract/assert.go:33 +0xe4
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.makeActionProgress({0x106864480|github.com/pulumi/pulumi/pkg/v3/backend/display.makeActionProgress({0x106864480>, 0x1}, {0x0, 0x0})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:59 +0xa8
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshColumns(0x14001d94780|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshColumns(0x14001d94780>, {0x106864480, 0x1}, {0x140021259f0, 0x5, 0x5}, {0x14000a46060, 0x5, 0x5})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:437 +0x9c
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0x14001d94780)|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).refreshAllRowsIfInTerminal(0x14001d94780)>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:655 +0x598
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processNormalEvent(0x14001d94780|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processNormalEvent(0x14001d94780>, {{0x105398980?, 0x7?}, {0x105a667e0?, 0x14000849400?}})
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:1134 +0xd48
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processEvents(0x14002d61e40|github.com/pulumi/pulumi/pkg/v3/backend/display.(*ProgressDisplay).processEvents(0x14002d61e40>?, 0x140035a49b0, 0x1400079f6e0)
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:1202 +0xc0
<http://github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents.func1()|github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents.func1()>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:342 +0x34
created by <http://github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents|github.com/pulumi/pulumi/pkg/v3/backend/display.ShowProgressEvents>
	/private/tmp/pulumi-20220504-79959-1budjvw/pkg/backend/display/progress.go:341 +0x658

Any ideas why this may happen?

@thousands-hairdresser-72380 could you file an issue in pulumi/pulumi with a repro, sorry about this

@thousands-hairdresser-72380 what version where you on before updating to 3.32? I don't think the .31 to .32 change broke this

I was previously on

3.31.1

(I’m fairly certain) I use pulumi daily for work and always update when there’s a an update available.

huh that's very surprising. can you try going back to 3.31.1 with

curl -fsSL <https://get.pulumi.com> | sh -s -- --version 3.31.1

and confirm that?

When I submitted the message above, I then downgraded by downloading

3.31.1

manually and the deploy worked.

Thanks! That narrows the search down a bit.

Let me know if you need any other assistance with troubleshooting!

If you could run with

-v11 --logtostderr

and send me those logs (fraser@pulumi.com) they nearly always help

Should I upgrade to 3.32 first?

yes with 3.32 and any run of

preview

or

up

that triggers the panic

I’m not able to reproduce the error. I’ll do some more troubleshooting. It may have been stack-related, but I may not be able to touch that stack for a while as it’s actively in use. (I’m testing on another stack)

Understood, complicates things that maybe this isn't deterministic but I'll check through the display code to see if I can find anything

Thank you! I’ll try a few more variations. Perhaps it was a one-off related to some broken state in AWS. (missing property value, etc)

I had this happen the other day, since we were playing around with Pulumi I assumed it was something we were doing and did a destroy and up again. Everything worked after that.