[pve-devel] [PATCH cluster v3 07/14] api/cluster: add join endpoint

[Fabian Grünbichler]

On Tue, Dec 19, 2017 at 03:01:15PM +0100, Fabian Grünbichler wrote:
> On Tue, Dec 19, 2017 at 12:52:32PM +0100, Thomas Lamprecht wrote:
> > Add an enpoint to the API which allows to join an existing PVE
> > cluster by only using the API instead of CLI tools (pvecm).
> > 
> > Use a worker as this operation may need longer than 30 seconds.
> > With the worker we also get a task log entry/window for an UI for
> > free, allowing to give better feedback.
> > ---
> > 
> > changes v2 -> v3:
> > * use worker
> 
> same issue as with create:
> 
> $ pvecm add clustertest01
> Please enter superuser (root) password for 'clustertest01':
> Password for root at clustertest01:
> Etablishing API connection with host 'clustertest01'
> The authenticity of host 'clustertest01' can't be established.
> X509 SHA256 key fingerprint is
> 60:0F:DE:48:C7:1B:48:4D:F2:BF:EF:C2:98:8E:5B:F1:9B:95:EB:97:99:33:2F:C3:B6:15:CC:10:E9:D0:EC:54.
> Are you sure you want to continue connecting (yes/no)? yes
> Login succeeded.
> Request addition of this node
> Join request OK, finishing setup locally
> stopping pve-cluster service
> backup old database
> waiting for quorum...OK
> generating node certificates
> merge known_hosts file
> node certificate changed, restart pveproxy and pvedaemon services
> successfully added node 'clustertest02' to cluster.
> ipcc_send_rec[4] failed: Transport endpoint is not connected
> 

so this is not directly related to your patch series, but a general
problem when restarting pve-cluster while a forked worker is running..