https://pulumi.com logo
s

sparse-insurance-40223

09/25/2018, 8:17 AM
pulumipulumiStack: operations-Babylon-4 info: panic: runtime error: invalid memory address or nil pointer dereference [signal 0xc0000005 code=0x0 addr=0x0 pc=0x128929d]
😙 2
s

stocky-spoon-28903

09/25/2018, 11:58 AM
Hi @sparse-insurance-40223! That doesn’t look so good... do you have the backtrace that came from the panic available?
s

sparse-insurance-40223

09/25/2018, 11:59 AM
sorry no 😞
all the trace was within the kubernetes bits
s

stocky-spoon-28903

09/25/2018, 1:14 PM
Ah - thanks for reporting it. That’s likely one for @creamy-potato-29402 when he’s online.
c

creamy-potato-29402

09/25/2018, 3:00 PM
Not good. Will fix ASAP.
@sparse-insurance-40223 I’m not quite sure what you mean when you say that it didn’t delete the primary resource group? You mean it tried and failed?
s

sparse-insurance-40223

09/25/2018, 4:46 PM
Yeah I think it left something behind and then got itself in a tizzy and the local state was corrupted or something
c

creamy-potato-29402

09/25/2018, 4:46 PM
Did it leave an error?
Also what version of pulumi-kubernetes are you running?
This stack trace makes no sense lol
Also can you reproduce it
s

sparse-insurance-40223

09/25/2018, 4:47 PM
lol :S
how do i get the version
c

creamy-potato-29402

09/25/2018, 4:47 PM
Just look at the NPM version of the dependency
s

sparse-insurance-40223

09/25/2018, 4:47 PM
resource-kubernetes-v0.17.0-rc1
oh i see one sec
c

creamy-potato-29402

09/25/2018, 4:48 PM
hmm
was this coming from an example?
s

sparse-insurance-40223

09/25/2018, 4:48 PM
"@echoing-match-29901/kubernetes": "v0.17.0-rc1",
oh great thanks slack
c

creamy-potato-29402

09/25/2018, 4:48 PM
lol
s

sparse-insurance-40223

09/25/2018, 4:49 PM
i was following an example yeah but had changed it pretty heavily by that point
basically scripted rg + k8s + nginx ingress + some permissions
and when i did pulumi destroy i got that panic
the only thing left in azure was the original RG (not the k8s auto-rg it makes for the cluster)
c

creamy-potato-29402

09/25/2018, 4:50 PM
hmm, so did you run
npm install
before sunday?
s

sparse-insurance-40223

09/25/2018, 4:51 PM
yeah i started on it on friday
c

creamy-potato-29402

09/25/2018, 4:51 PM
makes sense. We weren’t publishing correct dev versions until sunday.
(We’re on v0.17.1-dev)
s

sparse-insurance-40223

09/25/2018, 4:52 PM
ah
well i'm planning on destroying this cluster tomorrow i can see if it happens again then
c

creamy-potato-29402

09/25/2018, 4:55 PM
Hmm, so it looks like it’s calling
Read
during refresh, then failing because there is no live object.
s

sparse-insurance-40223

09/25/2018, 4:57 PM
ah
c

creamy-potato-29402

09/25/2018, 4:57 PM
Trying to get a repro… we should be catching the live object if it doesn’t exist.
s

sparse-insurance-40223

09/25/2018, 4:57 PM
i had a few more issues presumably relating to the confused local state, i think i ended up deleting the state folder
but they were all things like host doesnt exist cos the cluster had gone
c

creamy-potato-29402

09/25/2018, 4:58 PM
oh
you were using a local statefile?
s

sparse-insurance-40223

09/25/2018, 4:58 PM
yeah
c

creamy-potato-29402

09/25/2018, 4:58 PM
mmm got it
s

sparse-insurance-40223

09/25/2018, 4:58 PM
ah i didnt think to mention that 🙂
c

creamy-potato-29402

09/25/2018, 5:01 PM
Hmm, does it reproduce reliably?
s

sparse-insurance-40223

09/25/2018, 5:02 PM
not sure tbh
i'm going to be deleting this test cluster tomorrow probably i can try then and get more info for the bug report
c

creamy-potato-29402

09/25/2018, 5:06 PM
Ok well
please do try to reproduce it… I can’t get it to fail in quite this way.
I’ll add more detail.
s

sparse-insurance-40223

09/25/2018, 5:10 PM
hometime here, 6pm! i'll let you know how i get on tomorrow
ok will do
c

creamy-potato-29402

09/25/2018, 5:21 PM
@sparse-insurance-40223 I think I understand the bug: https://github.com/pulumi/pulumi/issues/1984#issuecomment-424428743
if we can get a repro the fix should be trivially easy, I just want to make sure it is what we think. 🙂
@sparse-insurance-40223 I’ve developed a repro, and fixed the issue in https://github.com/pulumi/pulumi-kubernetes/pull/221
🙂
s

sparse-insurance-40223

09/26/2018, 8:14 AM
nice!