- Community Home
- >
- Software
- >
- HPE OneView
- >
- Use of OneView External Repository with Authentica...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
- Report Inappropriate Content
09-27-2017 08:12 AM
09-27-2017 08:12 AM
Use of OneView External Repository with Authentication
I was testing the use of an external repository for OneView and noticed an apparently incorrectly formatted URL of the SPP baseline while using authentication on the external repository.
Here is the output of the SUT using the baseline hosted on the OneView appliance:
C:\WINDOWS\system32>sut /status
This operation may take a while
System Update Manager...................: HPE OneView
Update Manager URL......................: https://172.16.26.21
Deploy Type.............................: FirmwareAndOSDrivers
Task Status.............................: Bios:N/A; LocalStorage:N/A; Deploy:StageFailed
Staging Directory.......................: C:\WINDOWS\system32\config\systemprofile\AppData\Local\hpsut\stagingdirectory
Baseline URI............................: http://172.16.26.21/nossl/fwbundles/882085_001_spp-Gen8_0-SPPGen80_15.iso
Baseline Version........................: Gen8.0
Mode of Operation.......................: AutoDeploy
Polling Interval In Minutes.............: 5
Force Deploy............................: No
Optional Components.....................: None
Enable iLO Queued Updates...............: false
User Action Needed......................: Staging operation may be slowed down due to the speed of the system, network connectivity speed to the system update manager or communication to iLO is lower.
Here is the output of SUT when using the baseline from an external repository:
C:\WINDOWS\system32>sut /status
This operation may take a while
System Update Manager...................: HPE OneView
Update Manager URL......................: https://172.16.26.21
Deploy Type.............................: FirmwareAndOSDrivers
Task Status.............................: Bios:N/A; LocalStorage:N/A; Deploy:Pending
Staging Directory.......................: C:\WINDOWS\system32\config\systemprofile\AppData\Local\hpsut\stagingdirectory
Baseline URI............................: https://<********>ve1leg
Baseline Version........................: Waiting for staging
Mode of Operation.......................: AutoDeploy
Polling Interval In Minutes.............: 5
Force Deploy............................: No
Optional Components.....................: None
Enable iLO Queued Updates...............: false
User Action Needed......................: None
The correct format of the URI should be https://username:password@repository/isoname.iso yet it is putting my password at the end of the URI.
Hoping somebody can confirm this behavior. Also is there any way to set a preference which repository a server profile would pull from if a baseline exists both internally and externally?