HPE OneView
1748239 Members
3635 Online
108759 Solutions
New Discussion

Re: OV 3.1 upgrade failure

 
FREDERIC COLLIN
Advisor

Re: OV 3.1 upgrade failure

Thanks Chris, indeed we also have our own internal CAs (Microsoft). I had read in the 3.1 upgrade guide about the SHA-1 signing issue (p18) but since our internal CAs were all using SHA-256 already i tought we'd be safe.

I'll try switching back to a self signed cert and retry the upgrade, thanks!

ChrisLynch
HPE Pro

Re: OV 3.1 upgrade failure

That note you saw unfortunately has nothing to do with the issue preventing the upgrade in your case.  And the workaround in the CA is only temporary, and only for upgrading to 3.10.  We will have this issue, and the main upgrade defect that this thread is discussing in a patch soon.


I am an HPE employee

Accept or Kudo

FREDERIC COLLIN
Advisor

Re: OV 3.1 upgrade failure

It was indeed the CA signed cert that was causing the problem, the customer advisory a00020832en_us was spot on ! I'm running OV 3.10 now and SPP 2017-07 was also uploaded successfuly after the upgrade!

 

Thanks.

ChrisLynch
HPE Pro

Re: OV 3.1 upgrade failure

Fantastic news.  Glad you were able to upgrade successfully.


I am an HPE employee

Accept or Kudo

martin2176
Advisor

Re: OV 3.1 upgrade failure

I got the lab instance upgraded to 3.1 after L2 support deleted the 3000 or so sessions in the DB.