https://pulumi.com logo
#general
Title
# general
e

early-musician-41645

10/29/2018, 10:18 PM
Should I open an issue?
m

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
to
pulumi update
. This will ensure that resources are registered in parallel and should unblock you.
If you want to retain your current EKS cluster, you can use
kubectl
to delete the resource that Pulumi believes does not exist
e

early-musician-41645

10/29/2018, 10:21 PM
thanks. Trying it out now
m

microscopic-florist-22719

10/29/2018, 10:21 PM
👍
Let me know if you want to go the
kubectl
route and I'll help you get that set up.
e

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
c

creamy-potato-29402

10/29/2018, 10:25 PM
hmmm
@early-musician-41645 @microscopic-florist-22719 I think this is a different issue that we’ve solved
m

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
c

creamy-potato-29402

10/29/2018, 10:27 PM
no, it’s saying the service already exists.
well both
m

microscopic-florist-22719

10/29/2018, 10:27 PM
Right, on the second run
Yeah
e

early-musician-41645

10/29/2018, 10:27 PM
It's 2 errors. 1) Timeout 2) Service already exists
c

creamy-potato-29402

10/29/2018, 10:27 PM
yeah, so the second problem I think is the PR I linked
the first, you are probably right.
e

early-musician-41645

10/29/2018, 10:27 PM
So the service was installing, then timed out, then succeeded, then failed on the retry
c

creamy-potato-29402

10/29/2018, 10:27 PM
Yeah, what version of the SDK are you using?
Try to use
v0.17.3
e

early-musician-41645

10/29/2018, 10:28 PM
for
@pulumi/pulumi
?
c

creamy-potato-29402

10/29/2018, 10:28 PM
@pulumi/kubernetes
e

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"
  }
}
c

creamy-potato-29402

10/29/2018, 10:29 PM
whats package-lock say?
or yarn.lock
e

early-musician-41645

10/29/2018, 10:29 PM
Where do I find that?
I see no *lock
c

creamy-potato-29402

10/29/2018, 10:30 PM
no lockfile?
did you run npm install?
there ought to be
package-lock.json
somewhere??
e

early-musician-41645

10/29/2018, 10:36 PM
Ah, it's module-specific, e.g.
/node_modules/@pulumi/kubernetes/yarn.lock