Should I open an issue Pulumi Community #general

Join Slack

Should I open an issue?

# general

early-musician-41645

10/29/2018, 10:18 PM

Should I open an issue?

microscopic-florist-22719

10/29/2018, 10:21 PM

The timeout is most likely due to an issue that causes Pulumi to serialize resource creation. This issue has been fixed; the fix will be included in the next release of the Pulumi CLI (which is happening today). For now, the easiest thing to do will be to tear down the EKS cluster and re-run, but pass

-p 10

pulumi update

. This will ensure that resources are registered in parallel and should unblock you.

microscopic-florist-22719

10/29/2018, 10:21 PM

If you want to retain your current EKS cluster, you can use

kubectl

to delete the resource that Pulumi believes does not exist

early-musician-41645

10/29/2018, 10:21 PM

thanks. Trying it out now

microscopic-florist-22719

10/29/2018, 10:21 PM

👍

microscopic-florist-22719

10/29/2018, 10:22 PM

Let me know if you want to go the

kubectl

route and I'll help you get that set up.

early-musician-41645

10/29/2018, 10:22 PM

I'm trying to do an All-Pulumi deployment so it's automated E2E without stepping in via kubectl

creamy-potato-29402

10/29/2018, 10:25 PM

hmmm

creamy-potato-29402

10/29/2018, 10:25 PM

@early-musician-41645 @microscopic-florist-22719 I think this is a different issue that we’ve solved

creamy-potato-29402

10/29/2018, 10:26 PM

https://github.com/pulumi/pulumi-kubernetes/pull/251

microscopic-florist-22719

10/29/2018, 10:26 PM

Can you elaborate? I figured it was the parallelism problem b/c the

Deployment

was never submitted

creamy-potato-29402

10/29/2018, 10:27 PM

no, it’s saying the service already exists.

creamy-potato-29402

10/29/2018, 10:27 PM

well both

microscopic-florist-22719

10/29/2018, 10:27 PM

Right, on the second run

microscopic-florist-22719

10/29/2018, 10:27 PM

Yeah

early-musician-41645

10/29/2018, 10:27 PM

It's 2 errors. 1) Timeout 2) Service already exists

creamy-potato-29402

10/29/2018, 10:27 PM

yeah, so the second problem I think is the PR I linked

creamy-potato-29402

10/29/2018, 10:27 PM

the first, you are probably right.

early-musician-41645

10/29/2018, 10:27 PM

So the service was installing, then timed out, then succeeded, then failed on the retry

creamy-potato-29402

10/29/2018, 10:27 PM

Yeah, what version of the SDK are you using?

creamy-potato-29402

10/29/2018, 10:27 PM

Try to use

v0.17.3

early-musician-41645

10/29/2018, 10:28 PM

for

@pulumi/pulumi

creamy-potato-29402

10/29/2018, 10:28 PM

@pulumi/kubernetes

early-musician-41645

10/29/2018, 10:28 PM

"latest"

Copy code

{
  "name": "eks-cluster",
  "devDependencies": {
    "@types/node": "latest"
  },
  "dependencies": {
    "@pulumi/pulumi": "latest",
    "@pulumi/aws": "latest",
    "@pulumi/eks": "0.16.1",
    "@pulumi/kubernetes": "latest"
  }
}

creamy-potato-29402

10/29/2018, 10:29 PM

whats package-lock say?

creamy-potato-29402

10/29/2018, 10:29 PM

or yarn.lock

early-musician-41645

10/29/2018, 10:29 PM

Where do I find that?

early-musician-41645

10/29/2018, 10:29 PM

I see no *lock

creamy-potato-29402

10/29/2018, 10:30 PM

no lockfile?

creamy-potato-29402

10/29/2018, 10:30 PM

did you run npm install?

creamy-potato-29402

10/29/2018, 10:30 PM

there ought to be

package-lock.json

somewhere??

early-musician-41645

10/29/2018, 10:36 PM

Ah, it's module-specific, e.g.

/node_modules/@pulumi/kubernetes/yarn.lock

Open in Slack

Previous Next