-
Notifications
You must be signed in to change notification settings - Fork 301
fleetctl submit/start for more than 5 units at a time fails #1425
Comments
relates to #1352 |
Have reproduced the issue. It relates to |
Looks like that on any failed request fleetd closes the unix socket. Closed socket terminates fleetctl fd-forward /var/run/fleet.sock, but local fleetctl doesn't know about that and still tries to send data to ssh. possible solution is fix |
It turned out that it is not a reason. Still investigating. |
The actual reason was multiple "auth-agent-req@openssh.com" requests, which is not supported by SSH daemon. Had to add additional check whether request was sent or not. |
Similar issue in python's paramiko paramiko/paramiko#23 |
Is there a release with this fix? |
Even the CoreOS alpha is on v0.11.8, it's hard to believe all CoreOS users are affected by this bug :( |
@ohjames True. v0.11.8 does not contain the fix. |
When invoking fleetctl as:
$ fleetctl --tunnel 54.191.250.126 submit 1.service ... 6.service
with more than 5 units, I get
Error creating units: failed creating unit a.service: Put http://domain-sock/fleet/v1/units/6.service?alt=json: ssh: rejected: administratively prohibited (open failed)
This same error occurs whether the operation is submit, start, or load, but destroy with many services appears to work
The text was updated successfully, but these errors were encountered: