Re: [ovirt-devel] oVirt 3.5 test day 2 results

Thanks Francesco, some comments between the lines. ----- Original Message ----- We choose that way to avoid to ask to the user to provide the root password of the engine host, in order to automatically copying files via SCP or executing commands over ssh on the remote host, for security reasons. I agree with you that due to that assumption this result is not so usable. As a default value, engine-setup configure the engine to look for a websocket proxy on localhost. The setup on the two host are asynchronous but we always need a value for the websocket proxy location so we use localhost as the default value for that. On the second host, setting up the websocket proxy, engine-setup produces all the command that the user have to run on the engine host in order to enroll the certificate and to have it pointing to the right websocket proxy. That command in my case is: engine-config -s WebSocketProxy=f19t6.localdomain:6100 and should be enough to configure the websocket proxy location without manually touching the DB. I tried to reproduce and I also encountered the problem you stated: the engine still points to localhost for websocket proxy. Going deeper, 'engine-config -g WebSocketProxy' already returns the new correct value but the web console still points on localhost. Now I had to reload the whole engine to make that property effective; if I remember correctly with past release it was enough to change the property value without reloading it. I'm reporting a bug for that: https://bugzilla.redhat.com/1124851 ok, I'll do.