Skip to content

Commit c8b2983

Browse files
[patch] updated doc
1 parent 473a4c1 commit c8b2983

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

‎src/mas/devops/data/catalogs/v9-260918-amd64.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -211,6 +211,6 @@ editorial:
211211
- IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
212212
- 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)
213213
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)
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)
215215

216216

‎src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,5 +78,5 @@ editorial:
7878
- IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
7979
- 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)
8080
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)
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)
8282

‎src/mas/devops/data/catalogs/v9-260918-s390x.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,5 +78,5 @@ editorial:
7878
- IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419)
7979
- 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)
8080
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)
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)
8282

0 commit comments

Comments
 (0)