Patch was merged today due to HSTS being enabled on the domain again. There is also an issue with plain.resources display but I'll work on that in a separate ticket https://ovirt-jira.atlassian.net/browse/OVIRT-2057#icft=OVIRT-2057

Patch submitted for review. Need to verify it on a test system before setting +v

Please note that Duck does not want to fix that HSTS setting just for ovirt.org (see linked issue). So we need to enable SSL sooner and on all our domains. This is also in line with industry trend of "encryption by default".

Please note that accidentally ovirt.org got HSTS setting with includeSubDomains [1] and thus an unknown number of users got https requirement cached for the full *.ovirt.org zone. This might rise the priority of this. However. We removed the subdomain setting and send info to the users and devel on how to clear the browser cache.

[1] https://ovirt-jira.atlassian.net/browse/OVIRT-2006

Puppet manages HTTPD using this manifest:
https://gerrit.ovirt.org/gitweb?p=infra-puppet.git;a=blob;f=site/ovirt_resources/manifests/apache.pp;h=0ed489fa995482ad18a0aba49224ecbcd537c1c0;hb=refs/heads/production#l48

Adding another VHost should solve this, we can probably find an upstream module for letsencrypt to not have to generate certificates manually.