From 473a4c1c0a45a8912447e737b8899958aee0eb03 Mon Sep 17 00:00:00 2001 From: Abhishek Kushawaha Date: Sun, 20 Sep 2026 10:02:22 +0530 Subject: [PATCH 1/2] [patch] updated whats new in this interim release --- src/mas/devops/data/catalogs/v9-260918-amd64.yaml | 6 ++++-- src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml | 8 +++++--- src/mas/devops/data/catalogs/v9-260918-s390x.yaml | 8 +++++--- 3 files changed, 14 insertions(+), 8 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260918-amd64.yaml b/src/mas/devops/data/catalogs/v9-260918-amd64.yaml index 4580601d..6572b705 100644 --- a/src/mas/devops/data/catalogs/v9-260918-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-amd64.yaml @@ -207,8 +207,10 @@ editorial: whats_new: - title: '**Security updates and bug fixes**' details: - - 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) - - IBM Maximo Manage [v9.2.3/v9.1.24/v9.0.31] (https://www.ibm.com/support/pages/node/7288419) + - 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) + - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) - 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) + known_issues: + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml index f3b913a5..82104316 100644 --- a/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml @@ -74,7 +74,9 @@ editorial: whats_new: - title: '**Security updates and bug fixes**' details: - - 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) - - IBM Maximo Manage [v9.2.3/v9.1.24/v9.0.31] (https://www.ibm.com/support/pages/node/7288419) - - 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) + - 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) + - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) + - 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) + known_issues: + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260918-s390x.yaml b/src/mas/devops/data/catalogs/v9-260918-s390x.yaml index a70b7310..0e2a696e 100644 --- a/src/mas/devops/data/catalogs/v9-260918-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-s390x.yaml @@ -74,7 +74,9 @@ editorial: whats_new: - title: '**Security updates and bug fixes**' details: - - 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) - - IBM Maximo Manage [v9.2.3/v9.1.24/v9.0.31] (https://www.ibm.com/support/pages/node/7288419) - - 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) + - 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) + - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) + - 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) + known_issues: + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file From c8b298349ae763de54f1e7d5eb5ee2dc77331eb2 Mon Sep 17 00:00:00 2001 From: Abhishek Kushawaha Date: Sun, 20 Sep 2026 10:06:13 +0530 Subject: [PATCH 2/2] [patch] updated doc --- src/mas/devops/data/catalogs/v9-260918-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260918-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260918-amd64.yaml b/src/mas/devops/data/catalogs/v9-260918-amd64.yaml index 6572b705..b02a27aa 100644 --- a/src/mas/devops/data/catalogs/v9-260918-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-amd64.yaml @@ -211,6 +211,6 @@ editorial: - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) - 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) known_issues: - - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml index 82104316..e4736cb3 100644 --- a/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-ppc64le.yaml @@ -78,5 +78,5 @@ editorial: - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) - 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) known_issues: - - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260918-s390x.yaml b/src/mas/devops/data/catalogs/v9-260918-s390x.yaml index 0e2a696e..d3db5355 100644 --- a/src/mas/devops/data/catalogs/v9-260918-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260918-s390x.yaml @@ -78,5 +78,5 @@ editorial: - IBM Maximo Manage [v9.2.3,v9.1.24,v9.0.31](https://www.ibm.com/support/pages/node/7288419) - 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) known_issues: - - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [workaround](https://www.ibm.com/support/pages/node/7288522) + - title: On or after 21 September 2026, on a FIPS-enabled cluster, the maxinst pod (--manage-maxinst) fails to start or crashes during the database initialisation/upgrade phase [Workaround](https://www.ibm.com/support/pages/node/7288522) \ No newline at end of file