Merge branch 'monthlyupdate' into ocp422

Author: shimto-jacob-siby

src/mas/devops/data/catalogs/v9-260730-amd64.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:b40764ca34f56edd8e3f8d029aed9e9eb93d54ea1b63f6364f8f13f50f089771
+catalog_digest: sha256:8b78bc126d05663f881a44321fbda9a19076bb589a24f0c785fafef1fb56eab8
 
 ocp_compatibility:
 - "4.16"
@@ -75,7 +75,7 @@ mongo_extras_version_8: 8.0.23
 
 # Dependencies - Amlen
 # -----------------------------------------------------------------------------
-amlen_extras_version: 1.1.5              # Updated
+amlen_extras_version: 1.1.5              # No Update
 
 
 # Dependencies - UDS
@@ -92,13 +92,13 @@ appconnect_version: 6.2.0                    # Operator version 6.2.0 # sticking
 # Dependencies - Suite License Service
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-sls/releases
-sls_version: 3.13.0             # Updated
+sls_version: 3.13.0             # No Update
 
 
 # Dependencies - Truststore Manager
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases
-tsm_version: 1.7.7              # Updated
+tsm_version: 1.7.7              # No Update
 
 
 # Dependencies - Data Dictionary
@@ -202,33 +202,17 @@ aiservice_tenant_version:
 # ------------------------------------------------------------------------------
 editorial:
   whats_new:
-  - title: New feature release
-    details:
-    - IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
-    - IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
-    - IBM Maximo Monitor/IoT [v9.2.0](https://www.ibm.com/support/pages/node/7277101)
-    - IBM Maximo Optimizer [v9.2.0](https://www.ibm.com/support/pages/node/7276586)
-    - IBM Maximo Predict [v9.2.0](https://www.ibm.com/support/pages/node/7275237)
-    - IBM Maximo Visual Inspection [v9.2.0](https://www.ibm.com/support/pages/node/7277289)
-    - IBM Maximo Real Estate and Facilities [v9.2.0](https://www.ibm.com/support/pages/node/7275247)
-    - IBM Maximo AI Service [v9.2.0](https://www.ibm.com/support/pages/node/7276603)
-    - IBM Maximo AI Service Tenant v9.2
-    - IBM Maximo Location Service for Esri v9.2
   - title: '**Security updates and bug fixes**'
     details:
-    - IBM Maximo Application Suite Core Platform [v9.0.27](https://www.ibm.com/support/pages/node/7277381) and [v9.1.19](https://www.ibm.com/support/pages/node/7277382)
-    - IBM Maximo Manage [v9.0.27](https://www.ibm.com/support/pages/node/7276396) and [v9.1.19](https://www.ibm.com/support/pages/node/7276393)
-    - IBM Maximo IoT [v9.0.21](https://www.ibm.com/support/pages/node/7277130) and [v9.1.12](https://www.ibm.com/support/pages/node/7277131)
-    - IBM Maximo Monitor [v9.0.22](https://www.ibm.com/support/pages/node/7277099) and [v9.1.12](https://www.ibm.com/support/pages/node/7277100)
-    - IBM Maximo Optimizer [v9.0.24](https://www.ibm.com/support/pages/node/7276568) and [v9.1.13](https://www.ibm.com/support/pages/node/7276570)
-    - IBM Maximo Assist/Collaborate [v9.0.18](https://www.ibm.com/support/pages/node/7273929), [v9.1.12](https://www.ibm.com/support/pages/node/7273930)
-    - IBM Maximo Predict [v9.0.16](https://www.ibm.com/support/pages/node/7276914) and [v9.1.9](https://www.ibm.com/support/pages/node/7276913)
-    - IBM Maximo Visual Inspection [v9.0.21](https://www.ibm.com/support/pages/node/7277291) and [v9.1.18](https://www.ibm.com/support/pages/node/7277891)
-    - IBM Maximo Real Estate and Facilities [v9.1.12](https://www.ibm.com/support/pages/node/7276768)
-    - IBM Maximo AI Service [v9.1.16](https://www.ibm.com/support/pages/node/7276604)
-    - IBM Truststore Manager v1.7
-    - IBM Suite License Service v3.13
-    - Amlen v1.1
+    - IBM Maximo Application Suite Core Platform [v9.0.28](https://www.ibm.com/support/pages/node/7281592), [v9.1.20](https://www.ibm.com/support/pages/node/7281593) and [v9.2.1](https://www.ibm.com/support/pages/node/7281594)
+    - IBM Maximo Manage [v9.0.28](https://www.ibm.com/support/pages/node/7281106),[v9.1.20](https://www.ibm.com/support/pages/node/7281105) and [v9.2.1](https://www.ibm.com/support/pages/node/7276395)
+    - IBM Maximo IoT [v9.0.22](https://www.ibm.com/support/pages/node/7281365) ,[v9.1.13](https://www.ibm.com/support/pages/node/7281366)
+    - IBM Maximo Monitor [v9.0.23](https://www.ibm.com/support/pages/node/7280601),[v9.1.13](https://www.ibm.com/support/pages/node/7280594) and [v9.2.1](https://www.ibm.com/support/pages/node/7280603)
+    - IBM Maximo Optimizer [v9.0.25](https://www.ibm.com/support/pages/node/7276568),[v9.1.14](https://www.ibm.com/support/pages/node/7280908), [v9.2.1](https://www.ibm.com/support/pages/node/7280906)
+    - IBM Maximo Assist/Collaborate [v9.0.19](https://www.ibm.com/support/pages/node/7281391), [v9.1.13](https://www.ibm.com/support/pages/node/7281392)
+    - IBM Maximo Predict [v9.0.17](https://www.ibm.com/support/pages/node/7280608), [v9.1.10](https://www.ibm.com/support/pages/node/7280609) and [v9.2.1](https://www.ibm.com/support/pages/node/7280611)
+    - IBM Maximo Visual Inspection [v9.0.22](https://www.ibm.com/support/pages/node/7281598),[v9.1.19](https://www.ibm.com/support/pages/node/7281597) and [v9.2.1](https://www.ibm.com/support/pages/node/7281599)
+    - IBM Maximo Real Estate and Facilities [v9.1.13](https://www.ibm.com/support/pages/node/7281077) and [v9.2.1](https://www.ibm.com/support/pages/node/7281367)
+    - IBM Maximo AI Service [v9.1.17](https://www.ibm.com/support/pages/node/7280919) and [v9.2.1](https://www.ibm.com/support/pages/node/7280920)
   known_issues:
-    - title: A known issue exists in the June 25, 2026 release affecting IBM Maximo Visual Inspection. Customers with MVI installed and using custom cluster issuer should avoid upgrading to the June release. Installation of MVI 9.2.x should be deferred until the July 2026 patch.
-    - title: A know issue exists in the June 25 2026 release when a customer has environment setup with mas core+manage+Optimizer with out AIP as a addon. Then under manage work space two pods will appear aipoptimization-uninstall and it will be in error status. Even though these pods are in error status it does not have any functional impact on manage or optimizer. The fix has been identified and will be delivered in upcoming July 9.2 patch.
+    - title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-{instanceId}-manage patch manageworkspace {instanceId}-{workspaceId} --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-{instanceId}-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the {instanceId}-{workspaceId}- prefix from the returned PVC name.

src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:a414ca5c7c5ab647fb5478cc48f2da20a95226763d0d9b6f4830fc6a57d8c983
+catalog_digest: sha256:5944d34f9584733c806b0acc77e3490c8b64b640159b6944425136f976eb6427
 
 ocp_compatibility:
 - "4.16"
@@ -32,13 +32,13 @@ uds_extras_version: 1.5.0                    # No Update
 # Dependencies - Suite License Service
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-sls/releases
-sls_version: 3.13.0             # Updated
+sls_version: 3.13.0             # No Update
 
 
 # Dependencies - Truststore Manager
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases
-tsm_version: 1.7.7              # Updated
+tsm_version: 1.7.7              # No Update
 
 
 # Dependencies - MongoDB
@@ -72,16 +72,9 @@ mas_manage_version:
 # ------------------------------------------------------------------------------
 editorial:
   whats_new:
-  - title: New feature release
-    details:
-    - IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
-    - IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
   - title: '**Security updates and bug fixes**'
     details:
-    - IBM Maximo Application Suite Core Platform [v9.0.27](https://www.ibm.com/support/pages/node/7277381) and [v9.1.19](https://www.ibm.com/support/pages/node/7277382)
-    - IBM Maximo Manage [v9.0.27](https://www.ibm.com/support/pages/node/7276396) and [v9.1.19](https://www.ibm.com/support/pages/node/7276393)
-    - IBM Truststore Manager v1.7
-    - IBM Suite License Service v3.13
+    - IBM Maximo Application Suite Core Platform [v9.0.28](https://www.ibm.com/support/pages/node/7281592), [v9.1.20](https://www.ibm.com/support/pages/node/7281593) and [v9.2.1](https://www.ibm.com/support/pages/node/7281594)
+    - IBM Maximo Manage [v9.0.28](https://www.ibm.com/support/pages/node/7281106),[v9.1.20](https://www.ibm.com/support/pages/node/7281105) and [v9.2.1](https://www.ibm.com/support/pages/node/7276395)
   known_issues:
-    - title: A known issue exists in the June 25, 2026 release affecting IBM Maximo Visual Inspection. Customers with MVI installed and using custom cluster issuer should avoid upgrading to the June release. Installation of MVI 9.2.x should be deferred until the July 2026 patch.
-    - title: A know issue exists in the June 25 2026 release when a customer has environment setup with mas core+manage+Optimizer with out AIP as a addon. Then under manage work space two pods will appear aipoptimization-uninstall and it will be in error status. Even though these pods are in error status it does not have any functional impact on manage or optimizer. The fix has been identified and will be delivered in upcoming July 9.2 patch.
+    - title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-{instanceId}-manage patch manageworkspace {instanceId}-{workspaceId} --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-{instanceId}-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the {instanceId}-{workspaceId}- prefix from the returned PVC name.

src/mas/devops/data/catalogs/v9-260730-s390x.yaml

@@ -5,7 +5,7 @@
 # catalog itself, but not everything in the catalog supports this yet (including MAS)
 # so we need to use the CASE bundle mirror process still.
 
-catalog_digest: sha256:ae636f5ac30ea171daeca26d8ba7871042f33826c0a50982716589160dbd30bb
+catalog_digest: sha256:84311732b6078cb9857ef557bcd4db64949a6c1d8ce351c6a4aac59ac08637cb
 
 ocp_compatibility:
 - "4.16"
@@ -32,13 +32,13 @@ uds_extras_version: 1.5.0                    # No Update
 # Dependencies - Suite License Service
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-sls/releases
-sls_version: 3.13.0             # Updated
+sls_version: 3.13.0             # No Update
 
 
 # Dependencies - Truststore Manager
 # -----------------------------------------------------------------------------
 # https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases
-tsm_version: 1.7.7              # Updated
+tsm_version: 1.7.7              # No Update
 
 
 # Dependencies - MongoDB
@@ -72,16 +72,9 @@ mas_manage_version:
 # ------------------------------------------------------------------------------
 editorial:
   whats_new:
-  - title: New feature release
-    details:
-    - IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
-    - IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
   - title: '**Security updates and bug fixes**'
     details:
-    - IBM Maximo Application Suite Core Platform [v9.0.27](https://www.ibm.com/support/pages/node/7277381) and [v9.1.19](https://www.ibm.com/support/pages/node/7277382)
-    - IBM Maximo Manage [v9.0.27](https://www.ibm.com/support/pages/node/7276396) and [v9.1.19](https://www.ibm.com/support/pages/node/7276393)
-    - IBM Truststore Manager v1.7
-    - IBM Suite License Service v3.13
+    - IBM Maximo Application Suite Core Platform [v9.0.28](https://www.ibm.com/support/pages/node/7281592), [v9.1.20](https://www.ibm.com/support/pages/node/7281593) and [v9.2.1](https://www.ibm.com/support/pages/node/7281594)
+    - IBM Maximo Manage [v9.0.28](https://www.ibm.com/support/pages/node/7281106),[v9.1.20](https://www.ibm.com/support/pages/node/7281105) and [v9.2.1](https://www.ibm.com/support/pages/node/7276395)
   known_issues:
-    - title: A known issue exists in the June 25, 2026 release affecting IBM Maximo Visual Inspection. Customers with MVI installed and using custom cluster issuer should avoid upgrading to the June release. Installation of MVI 9.2.x should be deferred until the July 2026 patch.
-    - title: A know issue exists in the June 25 2026 release when a customer has environment setup with mas core+manage+Optimizer with out AIP as a addon. Then under manage work space two pods will appear aipoptimization-uninstall and it will be in error status. Even though these pods are in error status it does not have any functional impact on manage or optimizer. The fix has been identified and will be delivered in upcoming July 9.2 patch.
+    - title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-{instanceId}-manage patch manageworkspace {instanceId}-{workspaceId} --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-{instanceId}-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the {instanceId}-{workspaceId}- prefix from the returned PVC name.