Hey!
cockpit is stateless, so once the session ends you lose the data. The
process completes in the background.
I'll suggest to run ovirt-hosted-engine-cleanup and then start from the UI
again if needed.
You can add the port to the firewall by running
firewall-cmd --permanent --zone=public --add-port=9090/tcp
firewall-cmd --permanent --zone=public --add-port=9090/udp
This prevents the UI session timeout.
On Thu, Nov 14, 2019 at 4:18 PM wodel youchi <wodel.youchi(a)gmail.com> wrote:
Hi,
I got this behavior once and I didn't tested again.
I started the hosted-engine deployment using cockpit webui, the process
went smoothly, the LocalHosttedEngine VM was created, at that time I left
the console for sometime.
When I get back the cockpit console was closed due to idle session
timeout, I reconnect, and the hosted-engine wizard had disappeared and I
didn't find a way to get it back, the only choice was to start the process
again even if the console was showing that the host was registered with a
hosted engine Manager, so I couldn't continue the deployment (the storage
phase).
I had to stop the LocalHosttedEngine VM, delete it's temporary disk, then
restart the deployment again and this time I stick with cockpit webui to
get it done.
Regards.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/XLVYA5WBAYB...