for-azure
for-azure copied to clipboard
Unable to SSH into Manager VMSS's after upgrading the instance(s) to the last mode on Azure portal
Expected behavior
Manager should be accessible via SSH after upgrading instances to the last model.
Actual behavior
Got a "Connection refused" error message when trying to connect through SSSH after upgrading instances to the last model on Azure portal.
Steps to reproduce the behavior
- Create a resource group on Azure using Docker CE for Azure.
- Selected the value
Standard_D2s_v3
for VM sizes. - Once the resource group is created, open
swarm-manager-vmss
details. // SSH connection is working at this point - Go to "Instances" on the left menu and upgrade the instance(s) to the last model. // SSH connection STOPPED working
- Restart the instance(s). // SSH connection is still NOT working
- Select the instance(s) and click on "Reimage". // SSH connection is working again, the fingerprint for the RSA key changed, and the instance reverted to its initial state and any data / app deployed to it was lost
It seems that this is the same problem when stopping a manager or worker node and start it again. After a shutdown and start the nodes are no longer accessible via ssh (connection refused). This Problem exist since a long time now and should befixed now. I don't know why they doesn't fix it?
@th3000 I don't think they are supporting this project any longer (see #74 ). So I wouldn't expect anything to be fixed from this point on.