https://pulumi.com logo
Join Slack
Powered by
i’ve now gotten this error 3 times in the last cou...
# general
b
i’ve now gotten this error 3 times in the last couple days:
Copy code
Diagnostics:
  pulumi:pulumi:Stack (compute-studio-compute-studio-b-stage-eus2):
    error: transport is closing
is this the host having networking issues? or could this be pulumi related? not seeing any other obvious signs of networking trouble on the host
w
Interesting. Are you seeing this consistently? Is this in CI or also developer desktop?
t
I think I saw it once today
w
In CI? If anyone has additional client-side logs of occurrences of this - let us know.
t
on my laptop
b
I’ve seen it 3 times in about 10 days.. our main pipeline is Jenkins running pulumi in a docker container. I don’t see any other logs/notices other than this. It fails.. but on all subsequent runs it’s worked.
Got this again.. what’s the deal here? Is it the jenkins host? pulumi backend? azure backend? It’s messing with our pipeline mojo:
Copy code
@ Updating...........
 +  pulumi:pulumi:Stack myapp-myapp-b-stage-eus2 **creating failed** error: transport is closing
 +  azure:compute:VirtualMachine Studio-B-0-Stage-Eus2-Vm created 
 
Diagnostics:
  pulumi:pulumi:Stack (myapp-myapp-b-stage-eus2):
    error: transport is closing
I can send any other logs if needed also.. but right now I’m not sure what to tell the guys who are using the pulumi deployment system when it fails.. I just say I’m not sure, unfortunately 😕
I’d say it’s happening about 1 in 20 on pulumi stack updates
w
Very strange. I'm not aware of anything on the pulumi backend side that would be leading to this. But unfortunately hard to tell just from the error. I opened https://github.com/pulumi/pulumi/issues/2713 to track. If it is possible to run in verbose mode with 
pulumi update --logtostderr -v=7
that might provide a little more detail on what is failing. Note that that may produce a lot of output.
b
Ok thanks @white-balloon-205 I’ll get that into our pipeline.. lots of logs won’t be a problem.. would definitely like to get this figured out as to the culprit
we got another one of these today
has been a while, but this time we got it with the full verbose output
i’ll update the issue on github
actually, is there someone I can DM these logs too? would prefer to not put them on github
w
Feel free to DM to me.
b
ty
Open in Slack
PreviousNext
Powered by