Feature #12050
closed
connect to the correct VNC server when using pools
Added by Anonymous about 9 years ago.
Updated about 9 years ago.
Description
While the general connection to the specific node when running in pool node was resolved in #9374, VM consoles will not work.
I've tried it now on Foreman 1.9.2, fog 1.32.0, foreman_xen 0.2.1 and VM console works with a pool.
I'm switching VM between nodes - console disconnects, but going back and forth connects it again with correct node IP (https://IP/console?uuid=xxx - VNCTunnel started in production.log)
Could someone else confirm/deny it?
- Status changed from New to Resolved
This seems to be resolved with recent versions.
Also available in: Atom
PDF
Updated by