https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
f
I had a problem similar to this the other day. Perhaps this issue may be related? https://github.com/pulumi/pulumi/issues/2067
b
@full-dress-10026 the plugin version installed for my provider is the same as whats in my checkpoint
i ran into that issue as well before though
c
cc @bitter-oil-46081
b
updates are showing a missing parent?
Copy code
error: failed to load language plugin nodejs: failed to perform plugin load callback: failed to verify snapshot: child resource urn:pulumi:containers-dev::con
tainers::standard:Deploy$kubernetes:apps/v1:StatefulSet$kubernetes:core/v1:Service::eth refers to missing parent urn:pulumi:containers-dev::containers::standard:Deploy$kubernetes:apps/v1:StatefulSet::eth
b
Unfortunately, the version information stored in the manifest section for plugins isn't consulted in this case. If you look at the full checkpoint, in the resources section there should be a resource with the URN "urnpulumicontainers-dev:containerspulumiproviderskubernetes:default". The inputs property of that will say what version of the provider was being used, and we'll try to load that. What version is there?
b
@bitter-oil-46081 the inputs is what i was referring to
its the first jq output
b
Oh, sorry, completely skipped by that 😞.
I'm not 100% sure what is going on then. If you run with 
-v=10 --logtostderr
there will be a lot of diagnostics information, some of which would be related to plugin loading. I'm not sure if this is related to the other issue you see about a missing resource in the checkpoint. I would think they are not related, but I can not be certain.
b
destroy fails with the missing provider so i dont think its related
wow you werent kidding when you said a lot of info
b
🙂
b
it looks like it spins up the provider on localhost and send one request
Copy code
I1018 14:52:19.555373   83909 plugins.go:329] GetPluginPath(resource, kubernetes, 0.17.2): found candidate (#0.17.2)
I1018 14:52:19.555488   83909 plugins.go:345] GetPluginPath(resource, kubernetes, 0.17.2): found in cache at /Users/azamat/.pulumi/plugins/resource-kubernetes-v0.17.2/pulumi-resource-kubernetes
I1018 14:52:19.755571   83909 plugin.go:98] Launching plugin 'kubernetes (resource)' from '/Users/azamat/.pulumi/plugins/resource-kubernetes-v0.17.2/pulumi-resource-kubernetes' with args: 127.0.0.1:49914
I1018 14:52:19.900355   83909 provider_plugin.go:617] Provider[kubernetes, 0xc000e1c7d0].GetPluginInfo() executing
I1018 14:52:19.901543   83909 snapshot.go:125] SnapshotManager: RecordPlugin(kubernetes-0.17.2)
I1018 14:52:19.908699   83909 api.go:148] Making Pulumi API call:
some interesting info
Copy code
I1018 14:52:20.590815   83909 api.go:150] Pulumi API call details (<https://api.pulumi.com/api/stacks/XXXXXXXXX/complete>): headers=map[Content-Type:[application/json] User-Agent:[pulumi-cli/1 (v0.16.0; darwin)] Accept:[application/vnd.pulumi+1] Authorization:[update-token XX.XXX.XXXXXX]]; body={"status":"failed"}
status: failed
Pulumi API call response code 204 No Content
stack trace afterwards
Copy code
I1018 14:52:20.988109   83909 sink.go:154] defaultSink::Error(error: could not find plugin for provider 'urn:pulumi:cointainers-dev::cointainers::pulumi:providers:kubernetes::default'
<http://github.com/pulumi/pulumi/pkg/resource/deploy/providers.NewRegistry|github.com/pulumi/pulumi/pkg/resource/deploy/providers.NewRegistry>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/resource/deploy/providers/registry.go:107
<http://github.com/pulumi/pulumi/pkg/resource/deploy.NewPlan|github.com/pulumi/pulumi/pkg/resource/deploy.NewPlan>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan.go:210
<http://github.com/pulumi/pulumi/pkg/engine.plan|github.com/pulumi/pulumi/pkg/engine.plan>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/engine/plan.go:158
<http://github.com/pulumi/pulumi/pkg/engine.update|github.com/pulumi/pulumi/pkg/engine.update>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/engine/update.go:134
<http://github.com/pulumi/pulumi/pkg/engine.Refresh|github.com/pulumi/pulumi/pkg/engine.Refresh>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/engine/refresh.go:44
<http://github.com/pulumi/pulumi/pkg/backend/httpstate.(*cloudBackend).runEngineAction|github.com/pulumi/pulumi/pkg/backend/httpstate.(*cloudBackend).runEngineAction>
        /private/tmp/pulumi-20181017-83944-7lcm2y/src/github.com/pulumi/pulumi/pkg/backend/httpstate/backend.go:820
b
Hrm. The call to complete (and it returning 204) is expected. We call /complete when the updated has terminated (this is what releases the lease you have to update the stack, to prevent multiple updates from running concurrently). In this case, the update failed and so the CLI is telling the service that the update failed.
I think this is something I might need @microscopic-florist-22719's help investigating.
(and unfortunately, right now, I think his in an airplane over the Atlantic heading back from Italy to the US).
c
I thought he was already here today
are vacations on our team calendar somewhere
b
@busy-umbrella-36067 Can you share the checkpoint with me? I want to look more at what's going in it to see if I can understand why we are hitting this. DMing me a link to a private gist or something works.
I opened https://github.com/pulumi/pulumi/issues/2076 to track this after talking with @busy-umbrella-36067 a little more. He's unblocked for now, by manually removing the bad parent reference from his checkpoint.
Open in Slack
PreviousNext
Powered by