Working on Red Hat Hyperconverged Infrastructure, which uses Cockpit UI, but expects access to RHV Manager in order to allow VM management.
When user clicks oVirt Machines tab, it looks like there is an attempt to redirect the user to the configured RHV Manager URL. If RHV Manager is not accessible from the user's machine (wrong network, unresolved DNS) then the user just gets a browser error (Safari can't find the server, We can't connect to the server at <url>, etc.).
Is it possible to test client-side access and say something useful like "It looks like you don't have access to this service" or "It looks like the RHV Manager is down. Check that you can access the hosted engine on *url*" rather than redirecting and hoping?
Marek, please change the product/component to appropriate one
Laura, which version of cockpit and RHV do you use?
The cockpit-machines-ovirt requires connection to RHV API, otherwise functionality is very limited (sort of read-only list of running VMs).
If there's no way to make RHV API accessible from browser-machine, it makes no sense to have cockpit-machines-ovirt installed.
FQDN of RHV Manager needs to be provided to the cockpit-machines-ovirt either via dialog within UI or via post-installation script. Depending on your network topology, can you use proxy or whatever mechanism to enable access?
cockpit-machines-ovirt is part of Cockpit, so tracked here: https://github.com/cockpit-project/cockpit/issues
I understand, but my concern is more that in the case of a misconfiguration there's not a clear error to direct/assist the customer here.
Re. version, I'm not sure what is installed on dev's test server right now...
Sahina, what version are we pulling in for this version of RHHI?
I'd guess low to medium given Marek's comments?
Moved to cockpit since this is not cockpit-ovirt but cockpit machine ovirt
This will not make it in a reasonable time. Please re-open if you still feel this should be fixed