topic Re: OV 3.1 upgrade failure in HPE OneView

OV 3.1 upgrade failure

martin2176 — Tue, 08 Aug 2017 11:26:00 GMT

I will open a Support ticket as advised by Chris in another thread. Just letting you know about this issue

Update appliance to version 3.10.04-0299553
Update appliance failed

Start update
Execute pre-snapshot scripts
Shutdown services
Execute pre-update scripts
Install packages
Execute post-update scripts
Reboot appliance
Update database
Startup services
Reverting the appliance to pre-update version
Update failed

Re: OV 3.1 upgrade failure

martin2176 — Tue, 08 Aug 2017 11:36:07 GMT

I have OV GD 1.2 linked to this appliance. But, before I upgraded the OV, I removed the appliance from OV GD.

But it did not help

Re: OV 3.1 upgrade failure

sdmitriev1 — Tue, 08 Aug 2017 11:48:23 GMT

Do you have support contract for OV?

Re: OV 3.1 upgrade failure

ChrisLynch — Tue, 08 Aug 2017 22:50:53 GMT

Please open a support case in order to resolve this issue Martin. The only way to fix the issue is with supports help. We are in the final stages of publishing a CA on the issue.

Re: OV 3.1 upgrade failure

martin2176 — Thu, 10 Aug 2017 03:37:53 GMT

Chris

Is there a way to prevent t his from happening rather than fixing it after the fact. The issue was faced in lab during the upgrade
we have yet to upgrade 4 of our Production instances and anything to prevent this from happening would be great.

I hope the CA would have that info.

Also, sev2 ticket was opened on 8/8 2:30 pm EST. No one has got hold off the ticket as of yet. 36 hrs now.

opened under OV SAR ticket 104416318059

Re: OV 3.1 upgrade failure

FREDERIC COLLIN — Thu, 10 Aug 2017 18:21:30 GMT

Just saw this after opening a new ticket, same 3.1 upgrade problem from 3.0

OV ticket #5322060277

Re: OV 3.1 upgrade failure

ChrisLynch — Thu, 10 Aug 2017 18:42:13 GMT

Is there a way to prevent t his from happening rather than fixing it after the fact.

Unfortunately, no. We just published the CA last night. I will be posting a sticky thread in this forum so others know. IN order to get the "fixme.bin", you will need to open a support case, and reference the CA ID a00018007en_us.

Re: OV 3.1 upgrade failure

FREDERIC COLLIN — Thu, 10 Aug 2017 19:08:48 GMT

I seem to be having the same upgrade issue but the cause seems different from the CA a00018007en_us since i only have 474 occurences in the audit log. :-(

I also noticed i couldn't add SPP 2017-07 before trying the upgrade but i didn't write down that error.

Re: OV 3.1 upgrade failure

ChrisLynch — Thu, 10 Aug 2017 19:18:16 GMT

@FREDERIC COLLIN, we are aware of another upgrade issue where if you have your own Certificate Authority, completed a CSR and the upgrade is failing around 70%, you will need to follow this Customer Advisory.

Re: OV 3.1 upgrade failure

ChrisLynch — Thu, 10 Aug 2017 19:20:24 GMT

@FREDERIC COLLIN,

I also noticed i couldn't add SPP 2017-07 before trying the upgrade but i didn't write down that error.

The 2017.07 SPP has changed format. In order to use that SPP within HPE OneView, you will need to patch your 3.00 appliance to 3.00.08, or complete you upgrade to 3.10. This Customer Advisory talks about that change.

Re: OV 3.1 upgrade failure

FREDERIC COLLIN — Thu, 10 Aug 2017 19:25:04 GMT

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!

Re: OV 3.1 upgrade failure

ChrisLynch — Thu, 10 Aug 2017 19:29:09 GMT

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.

Re: OV 3.1 upgrade failure

FREDERIC COLLIN — Thu, 10 Aug 2017 20:27:26 GMT

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.

Re: OV 3.1 upgrade failure

ChrisLynch — Thu, 10 Aug 2017 21:06:51 GMT

Fantastic news. Glad you were able to upgrade successfully.

Re: OV 3.1 upgrade failure

martin2176 — Fri, 11 Aug 2017 13:47:15 GMT

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