https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# aws
s
This message was deleted.
b
fyi: when using the AWS console, i can create the listener normally...
a
Hey @bright-magician-13023. I’m sorry your experiencing this. The AWS Provider should never panic. Could you post a bug report in pulumi-aws? We would appreciate it.
b
Hi Ian, thanks for the response... This has become a blocker now… I can’t deploy my services anymore... must be a version mismatch maybe? I could deploy the stacks a couple of days ago'... I can see that in my git history, a commit from 2 days ago upgraded they python pulumi package from 
3.101.1
to 
3.105.0
and the pulumi-aws package from 
6.18.0
to 
6.22.0
a
We recently released a patch to this area. Do you see the same problem in 6.22.1?
b
not sure, I'm resetting the git history to before that change and re-deploying... it just takes a little while to "down" and "up" the stacks coz there's an RDS cluster and a nat gateway...
ill let you know in a min
ok, so, just reverting the git history to 2 days' ago' (before the version change) makes my stack work again..., I'll add back the commit (only the pulumi packages versions) and re-deploy...
ok, so, simply downgrading 
pulumi-aws
to 
6.19.0
fixes the issue above
i reverted back all the repo to the most recent version and 
poetry add pulumi-aws==6.19.0
and this seems to have fixed the issue
yes, @ancient-policeman-24615 i miss-read your message earlier, i accidentally read 
6.21.1
... I can see the new version was released last night... that is correct, upgrading to 
6.22.1
seem to have fixed the problem, thank you so much!
🎉 1
a
I’m glad that got you unblocked
10 Views
Open in Slack
PreviousNext
Powered by