Hi,

if you are using HTTPS certificate signed by custom CA, manual action is required after upgrade to 4.0 due to introduction of oVirt engine SSO feature. More info about the manual steps can be found at [1].

Thanks

Martin Perina


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1336838

On Fri, Jun 24, 2016 at 6:32 PM, Matt Haught <dmhaught@ncsu.edu> wrote:
So I switched back to the original self-signed certs that I had luckily saved and was able to get in without error. Is there a new process for using non-self-signed certs with ovirt 4.0?

Thanks,
--
Matt Haught

On Fri, Jun 24, 2016 at 11:19 AM, Matt Haught <dmhaught@ncsu.edu> wrote:
I just attempted an upgrade from 3.6 to 4.0 hosted engine and ran into an problem. The hosted engine vm updated without issue, but when I go to login to the web interface to continue the process I get:

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

at every page load and I can't login. I have a feeling that the issue comes from where I replaced the self-signed certs with trusted ca signed certs a year ago. Is there a work around?

CentOS 7.2

Thanks,

--
Matt Haught


_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users