Description of problem: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/index doesn't document how to upgrade Websoket-Proxy running on separate host.
Here the flow should be more or less like: - take a backup on el7 - reinstall on el8 with websocket only - restore the backup PKI and configuration should be restored properly at this point, engine-setup may still be required.
(In reply to Sandro Bonazzola from comment #1) > Here the flow should be more or less like: > - take a backup on el7 > - reinstall on el8 with websocket only Can this host be the same host as the remote DWH machine (if there is one)? Can this host be used as a hypervisor as well as hosting the proxy?
(In reply to Steve Goodman from comment #2) > (In reply to Sandro Bonazzola from comment #1) > > Here the flow should be more or less like: > > - take a backup on el7 > > - reinstall on el8 with websocket only > > Can this host be the same host as the remote DWH machine (if there is one)? Yes it can > Can this host be used as a hypervisor as well as hosting the proxy? No, websocket proxy shouldn't be on the hypervisor hosts. It's better to not mix RHV-M channels with hosts channels.
Didi, Can you provide any more details on this?
Closing this bug as won't fix. It has been decided to drop the effort of maintaining the possibility to install websocket proxy on separate host.
I didn't test, but I think comment 1 is mostly correct. Not sure there is much value in this, though - it's probably easier to just install a new websocket-proxy on a new machine against the upgraded engine. This requires testing as well.