Solved oVirt and Cockpit: Please provide valid oVirt engine fully qualified domain name (FQDN)

[scottalanmiller]

Getting this error...

Please provide valid oVirt engine fully qualified domain name (FQDN) and port (443 by default)

But my FQDN is definitely correct and working, port is 443 (default.) I can see oVirt no issue on both 80 and 443. But Cockpit comes back instantly with the error, as if it doesn't like the FQDN given and is somehow checking it or something, but way too fast to actually be looking it up.

[scottalanmiller]

Looks like a bug. You can get it to run correctly from the command line...

cd /usr/share/cockpit/ovirt/
chmod +x install.sh
./install.sh https://my.ovirt.com/ovirt-engine 443

Running in this way produces good output. And it creates the necessary /etc/cockpit/machines-ovirt.config file.

[scottalanmiller]

Here is the code segment that is generating this error:

function configureOvirtUrl(oVirtFqdn, oVirtPort) {
    console.info('configureOvirtUrl: ', oVirtFqdn, oVirtPort);

    const dfd = cockpit.defer();
    dfd.notify(_("Registering oVirt to Cockpit"));

    const failHandler = (ex, data) => {
        if (ex && ex.status === 302) { // Found, redirects would follow
            doRegisterOvirt(oVirtFqdn, oVirtPort, dfd);
            return;
        }

        console.info('Unable to access oVirt engine: ', JSON.stringify(ex), JSON.stringify(data));
        dfd.reject(_("Please provide valid oVirt engine fully qualified domain name (FQDN) and port (443 by default)"));
    };

https://github.com/cockpit-project/cockpit/blob/master/pkg/ovirt/components/InstallationDialog.jsx

[scottalanmiller]

Looks like a bug. You can get it to run correctly from the command line...

cd /usr/share/cockpit/ovirt/
chmod +x install.sh
./install.sh https://my.ovirt.com/ovirt-engine 443

Running in this way produces good output. And it creates the necessary /etc/cockpit/machines-ovirt.config file.

[Starke427]

Ran into this same problem today on 4.3 node installation.

The install script didn't work for me, it just made the web interface loop back to the engine in a weird way.

I wound up coming across the cli command for registering the node with the engine.

vdsm-tool register --engine-fqdn engine.localdomain

https://ovirt.org/develop/release-management/features/node/genericregistration.html

[dyasny]

it relies on DNS (or hosts files) to resolve itself and generate SSL certs, this has to work before you install the engine. If it did work, and you still get this error, this is a bug