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.
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.
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.
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.
@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.
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.
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!
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.
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!
