https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
c
@damp-book-35965 you cancelled the operation
maybe we should not display the second error when you cancel, but it just means your service did not complete initializing.
d
Nope..this is repeatedly happening since 2-3 times so now I'm not waiting for it to timeout
c
when we say the operation was “cancelled” we mean that the kubernetes provider was sent the 
Cancel
RPC call.
d
otherwise stuck on this:
Copy code
kubernetes:helm.sh:Chart      prometheus-operator                                      
 ~      └─ kubernetes:core:Service    kube-system/prometheus-operator-prometheus  updating..     [2/3] Attempting to allocate IP address to Service
c
When I wrote this, there was exactly one place where this was called — the ctrl-c handler.
@damp-book-35965 and when you wait, it times out?
d
Yes..
c
what type is your service.
d
LoadBalancer
c
@damp-book-35965 when it times out, does it actually have an IP attached?
d
Nope. it doesnt
c
sounds like it did not finish initializing then
the error was truthful. 🙂
d
I think something else is going on..So are you saying we should increase timeout or something :?
c
no
d
It's not telling me the reason for not getting an IP .
c
When I ask whether the service has an IP address attached, I mean when you 
kubectl get
it, is there an IP address reported in the 
.status
field.
it’s not telling you the reason, because Kubernetes does not know the reason.
d
Let me check that
c
when you say it wasn’t allocated an IP, why did you say no?
d
Because it's a load balancer type and there is no load balancer spun up on AWS
c
ok, well, in any event, in general we’ll have no idea why the service does not create a LB.
d
When I do kubectl get svc it shows external IP as pending
c
it should. the service controller should be talking to AWS and spinning one up. If it doesn’t work, it’s up to the service controller to report the error through the status field
right, so that sounds like some kind of problem with AWS or the service controller.
d
Yes..
c
but we don’t know what it is.
can you show me the output of the 
.status
field with 
-o yaml
d
Yup..I was wondering what's the logic from the pulumi error message
Copy code
status:
  loadBalancer: {}
c
yeah
ok so there was no error to report, which is not great.
d
Found something else with kubectl describe events
Which gave me my answer: we reached our limits for ELBs 😥
c
@damp-book-35965 ah, we should be including that information in the error
cc @gorgeous-egg-16927
👍 1
this is part of the “events” workstream
d
Yes
w
Specifically this is part of the work tracked in https://github.com/pulumi/pulumi-kubernetes/issues/133.
5 Views
Open in Slack
PreviousNext
Powered by