This message was deleted.

sparse-intern-71089

09/11/2020, 2:38 PM

This message was deleted.

gentle-diamond-70147

09/11/2020, 3:24 PM

Verbose and debug logging would be the first thing to try -

-v9 --logtostderr --debug

limited-rainbow-51650

09/11/2020, 3:31 PM

Wow… the flood of messages is crashing the terminal inside VSCode…

gentle-diamond-70147

09/11/2020, 3:32 PM

Can try a lower verbosity level first then, hehe.

-v5

limited-rainbow-51650

09/11/2020, 3:33 PM

Since your arguments specify logging to

stderr

, I can redirect to file with

2> pulumi.txt

right?

gentle-diamond-70147

09/11/2020, 3:36 PM

yes

limited-rainbow-51650

09/11/2020, 3:43 PM

@gentle-diamond-70147 wont’t know exactly what to look for now. Log file is 107886 lines.

limited-rainbow-51650

09/11/2020, 3:52 PM

Update: although my package.json pointed to

@pulumi/kubernetes:2.3.0

, I still had an old 1.5.6 in my

node_modules

folder. Running

npm install

fixed that. When I preview now, it doesn’t hang anymore, but pulumi now wants to replace my full AKS cluster because it reports a change in

networkProfile

?!?!?!

limited-rainbow-51650

09/11/2020, 4:05 PM

After adding the

loadbalancerSku

to my AKS cluster, no changes anymore. It seems the default value was changed. Then, I bumped to

@pulumi/kubernetes:2.6.0

and the

hang

is gone… sigh

5 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.