- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Arbiter Version / Incompatible with Omnistack
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
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
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
08-02-2023 04:10 AM - last edited on 08-02-2023 11:02 PM by support_s
08-02-2023 04:10 AM - last edited on 08-02-2023 11:02 PM by support_s
Hey,
we upgraded to Omnistack 4.2.0.97 (latest). We also upgraded the Arbiter (4.2.0.12 in the package and the matrix).
Upgrades went well, but the svt-software-commit exits with "ERROR [121]: The arbiter version is incompatible with this software.".
See also:
svtcli@omnicube-ip41-104:~$ svt-software-status-show
.-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
| Upgrade Status: Overall and Omnicube details |
+------------+----------------------------+-----------------+---------------------------+------------------+------------------------+-----------+-----------------------+-----------------------+-------------------------+
| Datacenter | Cluster | Upgrade Status | OmniStack host VC Name | Version | Can Rollback or Commit | State | Current Feature Level | Cluster Feature Level | Potential Feature Level |
+------------+----------------------------+-----------------+---------------------------+------------------+------------------------+-----------+-----------------------+-----------------------+-------------------------+
| SIT-DL | SIT-DL-01-S-CLUSTER.SERVER | Ready to commit | OmniStackVC-10-240-41-102 | Release 4.2.0.97 | Yes | Completed | 1363 | 1363 | 1480 |
| | | | OmniStackVC-10-240-41-104 | Release 4.2.0.97 | Yes | Completed | 1363 | 1363 | 1480 |
| | | | OmniStackVC-10-240-41-202 | Release 4.2.0.97 | Yes | Completed | 1363 | 1363 | 1480 |
'------------+----------------------------+-----------------+---------------------------+------------------+------------------------+-----------+-----------------------+-----------------------+-------------------------'
Really, using all of the latest packages and stuff and then...this? even the matrix claims, this versions are the ones, which should be used.
What can we do?
PS:
The HPE Site seems to be running like a snail today. What is going on here? Every click lasts seconds....
Solved! Go to Solution.
- Tags:
- Virtual Connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-02-2023 10:12 PM
08-02-2023 10:12 PM
SolutionHey Community,
in the meantime we talked to the support and got the following response, which i'd like to share:
There is indeed a feature level mismatch for the Arbiter. Most likely something bad has happened during the update. 4.2.0.12 is the correct version of the Arbiter for OVC 4.2.0.97.
Could you, please try the following:
Uninstall the old Arbiter and install a new one on version 4.2.0.97 (the one included in the deploy package).
Repoint the cluster to the new Arbiter by running these command from one of the OVCs CLI:
sudo su
source /vat/tmp/build/bin/appsetup
dsv-arbiter-instance-set --address (IP of the arbiter)
Then it should be possible to execute:
svt-software-commit
For us this solved the issued.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-03-2023 10:03 PM
08-03-2023 10:03 PM
Betreff: Arbiter Version / Incompatible with Omnistack
Hello @TRZ-2018,
That's awesome!
We are glad to know the issue has been resolved and we appreciate you for keeping us updated.
Sunitha G
I'm an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]