You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4e08e4b
Browse filesBrowse the repository at this point in the historyBrowse files
- IBM Maximo Application Suite Core Platform [v9.2.6](https://www.ibm.com/support/pages/node/7288414), [v9.1.25](https://www.ibm.com/support/pages/node/7288415), [v9.0.31](https://www.ibm.com/support/pages/node/7288418)
211
-
- IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
212
-
- FIPS [fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026](https://www.ibm.com/support/pages/ibm-semeru-runtime-includes-restricted-security-profiles-used-maximo-application-suite-components-operating-fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026?view=full)
208
+
- IBM Maximo Application Suite Core Platform [v9.0.32](https://www.ibm.com/support/pages/node/7289766), [v9.1.26](https://www.ibm.com/support/pages/node/7289767) and [v9.2.7](https://www.ibm.com/support/pages/node/7289768)
209
+
- IBM Maximo Manage [v9.0.32](https://www.ibm.com/support/pages/node/7289352),[v9.1.25](https://www.ibm.com/support/pages/node/7289351) and [v9.2.4](https://www.ibm.com/support/pages/node/7289350)
210
+
- IBM Maximo IoT [v9.0.24](https://www.ibm.com/support/pages/node/7288633) ,[v9.1.15](https://www.ibm.com/support/pages/node/7288634) ,[v9.2.4](https://www.ibm.com/support/pages/node/7288635)
211
+
- IBM Maximo Monitor [v9.0.25](https://www.ibm.com/support/pages/node/7288828),[v9.1.15](https://www.ibm.com/support/pages/node/7288834) and [v9.2.4](https://www.ibm.com/support/pages/node/7288901)
212
+
- IBM Maximo Optimizer [v9.0.27](https://www.ibm.com/support/pages/node/7288402),[v9.1.16](https://www.ibm.com/support/pages/node/7288401), [v9.2.3](https://www.ibm.com/support/pages/node/7288400)
213
+
- IBM Maximo Assist/Collaborate [v9.0.21](https://www.ibm.com/support/pages/node/7288906), [v9.1.15](https://www.ibm.com/support/pages/node/7288908)
214
+
- IBM Maximo Visual Inspection [v9.0.24](https://www.ibm.com/support/pages/node/7289755) ,[v9.1.21](https://www.ibm.com/support/pages/node/7289756) , [v9.2.3](https://www.ibm.com/support/pages/node/7289757)
215
+
- IBM Maximo Real Estate and Facilities [v9.1.15](https://www.ibm.com/support/pages/node/7288833) and [v9.2.3](https://www.ibm.com/support/pages/node/7289065)
216
+
- IBM Maximo AI Service [v9.1.19](https://www.ibm.com/support/pages/node/7287754) and [v9.2.3](https://www.ibm.com/support/pages/node/7287755)
217
+
- IBM Suite License Service v3.13.2
218
+
- 'Mongo: 8.0.30'
213
219
known_issues:
214
-
- title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (<instance_id>-<workspace_id>-manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522)
215
-
216
-
220
+
- title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
- IBM Maximo Application Suite Core Platform [v9.2.6](https://www.ibm.com/support/pages/node/7288414), [v9.1.25](https://www.ibm.com/support/pages/node/7288415), [v9.0.31](https://www.ibm.com/support/pages/node/7288418)
78
-
- IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
79
-
- FIPS [fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026](https://www.ibm.com/support/pages/ibm-semeru-runtime-includes-restricted-security-profiles-used-maximo-application-suite-components-operating-fips-140-2-mode-applicable-semeru-fips-140-2-restricted-security-profile-reaches-its-sunset-date-21-september-2026?view=full)
75
+
- IBM Maximo Application Suite Core Platform [v9.0.32](https://www.ibm.com/support/pages/node/7289766), [v9.1.26](https://www.ibm.com/support/pages/node/7289767) and [v9.2.7](https://www.ibm.com/support/pages/node/7289768)
76
+
- IBM Maximo Manage [v9.0.32](https://www.ibm.com/support/pages/node/7289352),[v9.1.25](https://www.ibm.com/support/pages/node/7289351) and [v9.2.4](https://www.ibm.com/support/pages/node/7289350)
77
+
- IBM Suite License Service v3.13.2
78
+
- 'Mongo: 8.0.30'
80
79
known_issues:
81
-
- title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (<instance_id>-<workspace_id>-manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522)
82
-
80
+
- title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
0 commit comments