Loading...
Loading...
Under certain conditions, the SimpliVity plug-in can exhibit issues such as SimpliVity actions not available following an upgrade to OmniStack 5.0.0. The issue is related to the svt-cert-service failing to start due to an incorrect postgres configuration.SimpliVity nodes deployed on version 3.7.9 (or earlier) and then upgraded to later versions are exposed to this issue due to an incorrect PostgreSQL configuration parameter.SimpliVity nodes deployed on Omnistack version 3.7.10 or later will not experience the issue.
All SimpliVity platforms.
If this issue has already occurred, contactSimpliVity Supportfor assistance.The issue has been resolved inOmniStack 5.1.0U1. Upgrading to OmniStack 5.0.0 is no longer advised.If an upgrade to 5.0.0 is planned and this issue has not occurred, run the following command on all Omnistack Virtual Controllers in the Federation:#sudo su#grep -q "password_encryption" /etc/postgresql/10/svtfs/postgresql.conf && sed -i 's/^.*password_encryption.*$/password_encryption = md5/g' /etc/postgresql/10/svtfs/postgresql.conf || echo "password_encryption = md5" >> /etc/postgresql/10/svtfs/postgresql.confEnter the commands on all nodes immediately before upgrading the OVC to version 5.0.0.Be aware that the changes will not persist following a reboot.Note: The workaround steps above can be safely run regardless of whether the node was deployed with Omnistack 3.7.9 or a later version. If you are unsure of the version used during deployment, it is better to run the workaround before upgrading to Omnistack 5.0.0.Revision HistoryDocument VersionRelease DateDetails2September 27, 2024Updated Resolution.1August 5, 2024Original Document Release.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.