- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- SimpliVity Upgrade Manager error
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
03-15-2022 10:16 AM - last edited on 03-15-2022 10:44 PM by support_s
03-15-2022 10:16 AM - last edited on 03-15-2022 10:44 PM by support_s
SimpliVity Upgrade Manager error
Hi
I'm getting an error when trying to upgrade a two node SimpliVity cluster from 4.1.0 to 4.1.1U1
The error occurs when Upgrade mamager runs the Pre-Upgrade validation tests which fail with the error
""internal error when trying to validate firmware availability""
This is associated with the SVT-2021._1201.02 firmware and when I select the option to take 'no action' with the firmware upgrade the validation test are fine.
I've the SVT-2021_1201.02 iso and sig file in the same directory as the upgrade manager and this must be fine as it detects the firmaware as 'ready for upgrade'
Has anyone- any idea on what could be causing this? Could it be a corrupt firmware image download?
many thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 11:17 AM
03-15-2022 11:17 AM
Query: SimpliVity Upgrade Manager error
System recommended content:
2. SimpliVity - " !FAILED! Verify Node Compute Cluster Deployment" Error Seen During Failed Upgrades
Please click on "Thumbs Up/Kudo" icon to give a "Kudo".
Thank you for being a HPE valuable community member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2022 12:34 PM - edited 03-15-2022 12:35 PM
03-15-2022 12:34 PM - edited 03-15-2022 12:35 PM
Re: SimpliVity Upgrade Manager error
we always install the firmware manually before upgrading the omnistacks.
booting directly into the ifirmware so mounted via iLO, following the automated update process. when done we use the upgrade manager and do the rest. gives less errors, less worries, less headache
we have never been successful using the upgrade manager installing the firmware iso on our nodes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 02:18 AM
03-16-2022 02:18 AM
Re: SimpliVity Upgrade Manager error
Thanks - I think I've always done the same.... its probably my first attempt to use this feature.
It's a good feature and a shame it doesn't work.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2022 04:28 AM
03-16-2022 04:28 AM
Re: SimpliVity Upgrade Manager error
Hello @CadenLange
Please upload a copy of the SvtUpgradeManager.txt file to review and see why it's failing to validate. Most of the issue I've encountered are related to iLO credentials. The file is located in %localappdata%\UpgradeManager\ folder in your Windows machine. You could search for ERROR in the file and post it here.
Thanks
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2022 01:36 AM
03-22-2022 01:36 AM
Re: SimpliVity Upgrade Manager error
Sorry for the delayed reply
I've added what I hope is the correct log file - the environment consists of 3 SimpliVity clusters within a single Federation. I was seeing the same error on all clusters (which I was attempting to upgrade individually) although the log file is from my attempt to upgrade cluster2.
I couldn't see anything with "ERROR" so have had to post the entire section that looked like it was relevent to the issue.
2022-03-16 09:57:47,574 [20] INFO SvtRestClient [GetClusterComponents] - GET cluster components successfully
2022-03-16 09:57:47,575 [20] INFO FederationMapper [UpdateClusterComponents] - Updating cluster components for Cluster2 de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:57:47,576 [20] INFO FederationMapper [InitializeComponents] - Component refresh done setting NeedsComponentRefresh to false
2022-03-16 09:57:47,577 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node01.mydomain.com Omnistack state: UPGRADE_AVAILABLE Version: 4.1.0.284 Available Omnistack component: 1
2022-03-16 09:57:47,577 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node01.mydomain.com ESXi state: UPGRADE_AVAILABLE Version: 7.0.1:16850804 Available Hypervisor component: 1
2022-03-16 09:57:47,577 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node01.mydomain.com Firmware state: UPGRADE_AVAILABLE Version: Multiple Available Firmware component: 1
2022-03-16 09:57:47,578 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node01.mydomain.com Component refresh done setting NeedsComponentRefresh to false
2022-03-16 09:57:47,579 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node02.mydomain.com Omnistack state: UPGRADE_AVAILABLE Version: 4.1.0.284 Available Omnistack component: 1
2022-03-16 09:57:47,579 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node02.mydomain.com ESXi state: UPGRADE_AVAILABLE Version: 7.0.1:16850804 Available Hypervisor component: 1
2022-03-16 09:57:47,580 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node02.mydomain.com Firmware state: UPGRADE_AVAILABLE Version: Multiple Available Firmware component: 1
2022-03-16 09:57:47,580 [20] INFO FederationMapper [InitializeComponents] - Cluster2_Node02.mydomain.com Component refresh done setting NeedsComponentRefresh to false
2022-03-16 09:57:47,580 [20] INFO FederationViewModel [ExecuteNavigation] - Validation successful. Now navigating from FederationViewModel
2022-03-16 09:57:57,566 [23] INFO SvtRestClient [GetHostBundleDictionary] - GetHostBundleDictionary for cluster- de9c44e4-a5f4-4981-8223-f8558f95cf89:Cluster2
2022-03-16 09:58:02,037 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:58:02,038 [23] INFO SvtRestClient [GetHostBundleDictionary] - GetHostBundleDictionary successful
2022-03-16 09:58:02,039 [23] INFO SelectUpgradeComponentViewModel [ExecuteNavigation] - Validation successful. Now navigating from SelectUpgradeComponentViewModel
2022-03-16 09:58:02,058 [1] INFO IloCredentialViewModel [MapHostCredentials] - ILO IP address present
2022-03-16 09:58:02,059 [1] INFO IloCredentialViewModel [MapHostCredentials] - ILO IP address present
2022-03-16 09:58:52,626 [17] INFO IloCredentialViewModel [ExecuteNavigation] - Validation successful. Now navigating from IloCredentialViewModel
2022-03-16 09:58:52,914 [22] INFO SvtRestClient [LoadUpgradeValidationTests] - Create & start pre-upgrade validations for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:21,516 [22] INFO SvtRestClient [SendHttpRequest] - Response: Accepted
2022-03-16 09:59:21,517 [22] INFO SvtRestClient [LoadUpgradeValidationTests] - Pre-upgrade validation started successfully
2022-03-16 09:59:22,026 [23] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:22,535 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:23,036 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:23,547 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:24,049 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:24,217 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:24,217 [23] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:24,219 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:24,551 [23] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:25,053 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:25,562 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:26,063 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:26,564 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:27,065 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:27,566 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:28,040 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:28,041 [23] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:28,043 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:28,098 [23] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:28,599 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:29,113 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:29,311 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:29,312 [23] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:29,315 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:29,614 [17] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:30,118 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:30,619 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:30,837 [17] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:30,838 [17] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:30,842 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:31,120 [22] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:31,623 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:32,125 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:32,550 [22] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:32,551 [22] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:32,555 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:32,626 [23] INFO SvtRestClient [GetValidationsStatus] - Get pre-upgrade validations status for cluster de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 09:59:33,131 [17] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:33,632 [22] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Update validation status skipped
2022-03-16 09:59:34,122 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 09:59:34,123 [23] INFO SvtRestClient [GetValidationsStatus] - Get validation status successfully
2022-03-16 09:59:34,124 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Mismatch found in validations, so creating new validation tree
2022-03-16 09:59:34,125 [23] INFO PreUpgradeValidationViewModel [GetValidationStatus] - Validation completed so validation status retrieving stopped
2022-03-16 10:00:14,843 [23] INFO PreUpgradeValidationViewModel [ExecuteNavigation] - Validation failed so hiding spinner visibility
2022-03-16 10:00:14,911 [4] INFO FederationViewModel [<LoadFederation>b__0] - Get federation task completed first, waiting for OVC state task to complete
2022-03-16 10:00:14,914 [23] INFO SvtRestClient [CheckUpgradePackageAvailability] - Get OmniStack package availability status
2022-03-16 10:00:14,937 [23] INFO SvtRestClient [CheckUpgradePackageAvailability] - Status retrieval completed. state: COMPLETE
2022-03-16 10:00:14,946 [4] INFO FederationViewModel [<LoadFederation>b__0] - Get OVC state task completed
2022-03-16 10:00:14,947 [4] INFO FederationViewModel [<LoadFederation>b__0] - OVC State: COMPLETE
2022-03-16 10:00:14,947 [4] INFO FederationViewModel [<LoadFederation>b__0] - rendering federation
2022-03-16 10:00:14,948 [4] INFO SvtRestClient [GetCommitScope] - GET commit-scope
2022-03-16 10:00:15,644 [4] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:15,645 [4] INFO SvtRestClient [IsFederationCommit] - Federation commit not allowed. Commit ScopeId received: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac,7d93820b-6cca-4bd8-b444-035e62a15901,de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 10:00:15,645 [23] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7d93820b-6cca-4bd8-b444-035e62a15901
2022-03-16 10:00:15,647 [17] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 10:00:15,647 [22] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac
2022-03-16 10:00:17,078 [17] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,079 [17] INFO UnknownState [UpdateSelf] - Cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89: Cluster2 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,080 [17] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,080 [17] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,127 [22] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,129 [22] INFO UnknownState [UpdateSelf] - Cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac: Cluster3 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,130 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,130 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,138 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,139 [23] INFO UnknownState [UpdateSelf] - Cluster: 7d93820b-6cca-4bd8-b444-035e62a15901: Cluster1 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,139 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,140 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,143 [4] INFO FederationViewModel [RenderFederation] - Federation rendering completed
2022-03-16 10:00:17,151 [22] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac
2022-03-16 10:00:17,152 [23] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7d93820b-6cca-4bd8-b444-035e62a15901
2022-03-16 10:00:17,157 [12] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 10:00:17,829 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,830 [23] INFO UnknownState [UpdateSelf] - Cluster: 7d93820b-6cca-4bd8-b444-035e62a15901: Cluster1 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,831 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,831 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,838 [22] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,839 [22] INFO UnknownState [UpdateSelf] - Cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac: Cluster3 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,839 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,839 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,855 [12] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:17,855 [12] INFO UnknownState [UpdateSelf] - Cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89: Cluster2 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:17,856 [12] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:17,856 [12] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:22,896 [22] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac
2022-03-16 10:00:22,905 [17] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: 7d93820b-6cca-4bd8-b444-035e62a15901
2022-03-16 10:00:22,907 [23] INFO SvtRestClient [GetClusterUpgradeStatus] - GET upgrade status for cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89
2022-03-16 10:00:23,688 [17] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:23,690 [17] INFO UnknownState [UpdateSelf] - Cluster: 7d93820b-6cca-4bd8-b444-035e62a15901: Cluster1 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:23,690 [17] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:23,691 [17] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster1_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:24,296 [23] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:24,297 [23] INFO UnknownState [UpdateSelf] - Cluster: de9c44e4-a5f4-4981-8223-f8558f95cf89: Cluster2 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:24,297 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:24,298 [23] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster2_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:24,320 [22] INFO SvtRestClient [SendHttpRequest] - Response: OK
2022-03-16 10:00:24,321 [22] INFO UnknownState [UpdateSelf] - Cluster: 7ca44011-b5bb-4a6b-8c83-4dcd41fcdaac: Cluster3 State: READY_FOR_UPLOAD Upgrade Percentage: 0 Detail: Additional: Recommended:
2022-03-16 10:00:24,322 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node01.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:24,322 [22] INFO ReadyForUpgradeState [UpdateStatus] - Host Address: Cluster3_Node02.mydomain.com State: READY_FOR_UPLOAD OmniStack: READY_FOR_UPLOAD Hypervisor: READY_FOR_UPLOAD Firmware: READY_FOR_UPLOAD Percentage: 0 Detail: Additional Info:
2022-03-16 10:00:27,736 [1] INFO SvtRestClient [ShutdownOrchestrator] - Terminating Orchestrator
2022-03-16 10:00:28,627 [1] INFO SvtRestClient [SendHttpRequest] - Response: Created
2022-03-16 10:00:28,752 [12] INFO FederationViewModel [ExecuteNavigation] - Validation failed so hiding spinner visibility
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2022 02:36 PM
11-22-2022 02:36 PM
Re: SimpliVity Upgrade Manager error
I've got the same error. Idont know why.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2022 05:20 AM
11-23-2022 05:20 AM
Re: SimpliVity Upgrade Manager error
Not sure if you are upgrading a Federation as well, but 2 things come to mind. 1) Is there a MVA in any of the clusters, and 2) There was a critical update to the SVTSP 2022_1021 in October.
The previous post was in early 2022.
Type: Firmware Version: 2022_1021 (21 Oct 2022) Upgrade Requirement: Critical
While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company
