- Community Home
- >
- Software
- >
- HPE OneView
- >
- Re: OV 3.1 upgrade failure
-
-
Forums
- Products
- Servers and Operating Systems
- Storage
- Software
- Services
- HPE GreenLake
- Company
- Events
- Webinars
- Partner Solutions and Certifications
- Local Language
- China - 简体中文
- Japan - 日本語
- Korea - 한국어
- Taiwan - 繁體中文
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Blog, Poland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Forums
-
Blogs
-
Information
-
English
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-10-2017 12:25 PM
08-10-2017 12:25 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-10-2017 12:29 PM
08-10-2017 12:29 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-10-2017 01:27 PM
08-10-2017 01:27 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-10-2017 02:06 PM
08-10-2017 02:06 PM
Re: OV 3.1 upgrade failure
Fantastic news. Glad you were able to upgrade successfully.
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
08-11-2017 06:47 AM
08-11-2017 06:47 AM
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.
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2022 Hewlett Packard Enterprise Development LP