From 715e7d5f646f269e35273b5aadb5df4c600bff5c Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 25 Jun 2026 18:29:27 +0530 Subject: [PATCH 01/30] [minor] Support July Catalog Update --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3d21da13..9abd019e 100644 --- a/README.md +++ b/README.md @@ -88,4 +88,4 @@ mas-devops-create-initial-users-for-saas \ Example of initial_users secret: ```json {"john.smith1@example.com":"primary,john1,smith1","john.smith2@example.com":"primary,john2,smith2","john.smith3@example.com":"secondary,john3,smith3"} -``` \ No newline at end of file +``` From 26299194183e8e355fbb13f46726229ef2b84293 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Fri, 26 Jun 2026 11:54:55 +0530 Subject: [PATCH 02/30] [patch] update assert catalogTag --- test/src/test_data.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/src/test_data.py b/test/src/test_data.py index c7a7345e..40d59026 100644 --- a/test/src/test_data.py +++ b/test/src/test_data.py @@ -32,7 +32,7 @@ def test_list_catalogs(): def test_get_newest_catalog_tag(): catalogTag = getNewestCatalogTag("amd64") # Reminder: update this test when adding a new catalog each month! - assert catalogTag == "v9-260625-amd64" + assert catalogTag == "v9-260730-amd64" def test_get_newest_catalog_tag_fail(): From fe9842c416fcd9b18dda996cb23d8d27ae49ff47 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Fri, 26 Jun 2026 12:10:37 +0530 Subject: [PATCH 03/30] [patch] Support July Catalog Update (#411) --- .../devops/data/catalogs/v9-260730-amd64.yaml | 235 ++++++++++++++++++ .../data/catalogs/v9-260730-ppc64le.yaml | 86 +++++++ .../devops/data/catalogs/v9-260730-s390x.yaml | 86 +++++++ 3 files changed, 407 insertions(+) create mode 100644 src/mas/devops/data/catalogs/v9-260730-amd64.yaml create mode 100644 src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml create mode 100644 src/mas/devops/data/catalogs/v9-260730-s390x.yaml diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml new file mode 100644 index 00000000..a94784af --- /dev/null +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -0,0 +1,235 @@ +--- +# Case bundle configuration for IBM Maximo Operator Catalog 260730 (AMD64) +# ----------------------------------------------------------------------------- +# In the future this won't be necessary as we'll be able to mirror from the +# 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:3a9f89efcdefc8b0bba4deaf2efea2b17835880ba17215274637a93b30f126b0 + +ocp_compatibility: +- "4.16" +- "4.17" +- "4.18" +- "4.19" +- "4.20" +- "4.21" + +# Dependencies - Cloud Pak for Data +# ----------------------------------------------------------------------------- +cpd_product_version_default: 5.2.0 # No Update + +ibm_licensing_version: 4.2.17 # Operator version 4.2.14 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-licensing) +common_svcs_version: 4.13.0 # Operator version 4.13.0 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-cp-common-services) +#common_svcs_version_1: 4.11.0 # Additional version 4.11.0 +cp4d_platform_version: 5.2.0+20250709.170324 # Operator version 5.2.0 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-cp-datacore/) +ibm_zen_version: 6.2.0+20250530.152516.232 # For CPD5 ibm-zen has to be explicitily mirrored +wsl_version: 11.0.0+20250521.202913.73 # used for wsl and wsl_runtimes unless wsl_runtimes_version also specified +wsl_runtimes_version: 11.0.0+20250515.090949.21 # cpd 5.1.3 uses version 10.3.0 of wsl runtimes but only 10.2.0 for wsl itself +wml_version: 11.0.0+20250530.193146.282 # Operator version 5.2.0 +spark_version: 11.0.0+20250604.163055.2097 # Operator version 5.2.0 +cognos_version: 28.0.0+20250515.175459.10054 # Operator version 25.0.0 + +postgress_version: 5.16.0+20250827.110911.2626 # ibm-cpd-cloud-native-postgresql-operator 5.2.0 cp4d +ccs_build: 11.0.0+20250605.130237.468 # cpd 5.2.0 using ccs build +ccs_extras_version: 11.0.0 # Extra Images for CCS used for PCD 5.2.0 Hotfix + +elasticsearch_version: 1.1.2667 # Operator version 1.1.2667 # used in cpd 5.1.3 only +opensearch_version: 1.1.2494 # Operator version 1.1.2494 + +# I have added this as a guess as to the actual version used, we are currently using the wsl_version, but that does not exist for datarefinery +# See: https://ibm-mas.slack.com/archives/C02PUHKQB5L/p1770849370378689 +datarefinery_version: 11.0.0+20250513.203727.232 + + +# Dependencies - Db2u +# ----------------------------------------------------------------------------- +db2u_version: 7.6.0+20260224.123157.19264 # Operator version 120104.0.0 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-db2uoperator) +db2u_extras_version: 1.0.6 # No Update +db2u_filter: db2 + +db2_channel_default: v120104.0 # Default Channel version for db2u-operator + + +# Dependencies - CouchDb +# ----------------------------------------------------------------------------- +# Note: This is required for Assist 9.0 (https://github.com/IBM/cloud-pak/blob/master/repo/case/ibm-couchdb/index.yaml) +couchdb_version: 1.0.13 # Operator version 2.2.1 (1.0.13) sticking with 1.0.13 + + +# Dependencies - Minio +# ----------------------------------------------------------------------------- +minio_version: RELEASE.2025-06-13T11-33-47Z +minio_extras_version: 1.0.0 + +# Dependencies - MongoDB +# ----------------------------------------------------------------------------- +mongo_extras_version_default: 8.0.20 +mongo_extras_version_4: 4.4.21 +mongo_extras_version_5: 5.0.23 +mongo_extras_version_6: 6.0.12 +mongo_extras_version_7: 7.0.23 +mongo_extras_version_8: 8.0.20 + + +# Dependencies - Amlen +# ----------------------------------------------------------------------------- +amlen_extras_version: 1.1.5 # Updated + + +# Dependencies - UDS +# ----------------------------------------------------------------------------- +uds_version: 2.0.12 # Operator version 2.0.12 # sticking to 2.0.12 version # Please do Not Change +uds_extras_version: 1.5.0 + + +# Dependencies - App Connect +# ----------------------------------------------------------------------------- +appconnect_version: 6.2.0 # Operator version 6.2.0 # sticking to 6.2.0 version # Please do Not Change + + +# Dependencies - Suite License Service +# ----------------------------------------------------------------------------- +# https://github.ibm.com/maximoappsuite/ibm-sls/releases +sls_version: 3.13.0 # Updated + + +# Dependencies - Truststore Manager +# ----------------------------------------------------------------------------- +# https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases +tsm_version: 1.7.7 # Updated + + +# Dependencies - Data Dictionary +# ----------------------------------------------------------------------------- +# https://github.ibm.com/maximoappsuite/ibm-data-dictionary/releases +dd_version: 1.1.23 # No Update + +# Dependencies - Opendata hub +# ----------------------------------------------------------------------------- +# https://github.com/opendatahub-io/opendatahub-operator/releases +odh_version: 2.32.0 + +# Extra Images for Redis (Collaborate) +# ------------------------------------------------------------------------------ +redis_extras_version: 2.1.40 # No Update + + +# Maximo Application Suite +# ----------------------------------------------------------------------------- +mas_core_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: 8.10.37 # No Update + 8.11.x: 8.11.34 # No Update +mas_assist_version: + 9.2.x: 9.2.0 # Not Supported + 9.1.x: 9.1.12 # Updated + 9.0.x: 9.0.18 # Updated + 8.10.x: 8.7.8 # No Update + 8.11.x: 8.8.7 # No Update +mas_hputilities_version: + 9.2.x: 9.2.0 # Not Supported + 9.1.x: "" # Not Supported + 9.0.x: "" # Not Supported + 8.10.x: 8.6.7 # No Update + 8.11.x: "" # Not Supported +mas_iot_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.12 # Updated + 9.0.x: 9.0.21 # Updated + 8.10.x: 8.7.33 # No Update + 8.11.x: 8.8.30 # No Update +mas_manage_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: 8.6.38 # No Update + 8.11.x: 8.7.32 # No Update +mas_monitor_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.12 # Updated + 9.0.x: 9.0.22 # Updated + 8.10.x: 8.10.30 # No Update + 8.11.x: 8.11.28 # No Update +mas_optimizer_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.13 # Updated + 9.0.x: 9.0.24 # Updated + 8.10.x: 8.4.28 # Updated + 8.11.x: 8.5.28 # Updated +mas_predict_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.9 # Updated + 9.0.x: 9.0.16 # Updated + 8.10.x: 8.8.15 # No Update + 8.11.x: 8.9.17 # No Update +mas_visualinspection_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.18 # Updated + 9.0.x: 9.0.21 # Updated + 8.10.x: 8.8.4 # No Update + 8.11.x: 8.9.21 # No Update +mas_facilities_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.12 # Updated + 9.0.x: "" # Not Supported + 8.10.x: "" # Not Supported + 8.11.x: "" # Not Supported + + +# Maximo AI Service +# ------------------------------------------------------------------------------ +aiservice_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.16 # Updated + +aiservice_tenant_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + + +# Editorial +# ------------------------------------------------------------------------------ +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 + 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. diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml new file mode 100644 index 00000000..98f47fb3 --- /dev/null +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -0,0 +1,86 @@ +--- +# Case bundle configuration for IBM Maximo Operator Catalog 260730 (PPC) +# ----------------------------------------------------------------------------- +# In the future this won't be necessary as we'll be able to mirror from the +# 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:d82533f5f713fe4f9ec265009ce7d32f6094671c936a31565f98a512916205f2 + +ocp_compatibility: +- "4.16" +- "4.17" +- "4.18" +- "4.19" +- "4.20" +- "4.21" + +# Dependencies - Db2u +# ----------------------------------------------------------------------------- +db2u_version: 7.6.0+20260224.123157.19264 # Operator version 120104.0.0 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-db2uoperator) + +db2_channel_default: v120104.0 # Default Channel version for db2u-operator + + +# Dependencies - UDS +# ----------------------------------------------------------------------------- +uds_version: 2.0.12 # Operator version 2.0.12 # sticking to 2.0.12 version # Please do Not Change +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 + + +# Dependencies - Truststore Manager +# ----------------------------------------------------------------------------- +# https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases +tsm_version: 1.7.7 # Updated + + +# Dependencies - MongoDB +# ----------------------------------------------------------------------------- +mongo_extras_version_default: 8.0.20 +mongo_extras_version_4: 4.4.21 +mongo_extras_version_5: 5.0.23 +mongo_extras_version_6: 6.0.12 +mongo_extras_version_7: 7.0.12 +mongo_extras_version_8: 8.0.20 + +# Maximo Application Suite +# ----------------------------------------------------------------------------- +mas_core_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: "" # Not Supported + 8.11.x: "" # Not Supported +mas_manage_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: "" # Not Supported + 8.11.x: "" # Not Supported + + +# Editorial +# ------------------------------------------------------------------------------ +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://supportcontent.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 + 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. diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml new file mode 100644 index 00000000..330777ca --- /dev/null +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -0,0 +1,86 @@ +--- +# Case bundle configuration for IBM Maximo Operator Catalog 260730 (Z) +# ----------------------------------------------------------------------------- +# In the future this won't be necessary as we'll be able to mirror from the +# 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:d7c156afa72073c9b47773e1113a06a841d538c5c0e8878bc39bf8bd62dd5aa4 + +ocp_compatibility: +- "4.16" +- "4.17" +- "4.18" +- "4.19" +- "4.20" +- "4.21" + +# Dependencies - Db2u +# ----------------------------------------------------------------------------- +db2u_version: 7.6.0+20260224.123157.19264 # Operator version 120104.0.0 (https://github.com/IBM/cloud-pak/tree/master/repo/case/ibm-db2uoperator) + +db2_channel_default: v120104.0 # Default Channel version for db2u-operator + + +# Dependencies - UDS +# ----------------------------------------------------------------------------- +uds_version: 2.0.12 # Operator version 2.0.12 # sticking to 2.0.12 version # Please do Not Change +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 + + +# Dependencies - Truststore Manager +# ----------------------------------------------------------------------------- +# https://github.ibm.com/maximoappsuite/ibm-truststore-mgr/releases +tsm_version: 1.7.7 # Updated + + +# Dependencies - MongoDB +# ----------------------------------------------------------------------------- +mongo_extras_version_default: 8.0.20 +mongo_extras_version_4: 4.4.21 +mongo_extras_version_5: 5.0.23 +mongo_extras_version_6: 6.0.12 +mongo_extras_version_7: 7.0.12 +mongo_extras_version_8: 8.0.20 + +# Maximo Application Suite +# ----------------------------------------------------------------------------- +mas_core_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: "" # Not Supported + 8.11.x: "" # Not Supported +mas_manage_version: + 9.2.x: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # Updated + 9.1.x: 9.1.19 # Updated + 9.0.x: 9.0.27 # Updated + 8.10.x: "" # Not Supported + 8.11.x: "" # Not Supported + + +# Editorial +# ------------------------------------------------------------------------------ +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://supportcontent.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 + 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. From ef87ba83930c29d548218374b23a3614579b38cc Mon Sep 17 00:00:00 2001 From: jainyjoseph Date: Fri, 26 Jun 2026 13:59:12 +0530 Subject: [PATCH 04/30] [patch] Extending mongo 8.0.23 support (#412) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 4 ++-- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 4 ++-- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index a94784af..88026e85 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -64,12 +64,12 @@ minio_extras_version: 1.0.0 # Dependencies - MongoDB # ----------------------------------------------------------------------------- -mongo_extras_version_default: 8.0.20 +mongo_extras_version_default: 8.0.23 mongo_extras_version_4: 4.4.21 mongo_extras_version_5: 5.0.23 mongo_extras_version_6: 6.0.12 mongo_extras_version_7: 7.0.23 -mongo_extras_version_8: 8.0.20 +mongo_extras_version_8: 8.0.23 # Dependencies - Amlen diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 98f47fb3..77e56d9a 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -42,12 +42,12 @@ tsm_version: 1.7.7 # Updated # Dependencies - MongoDB # ----------------------------------------------------------------------------- -mongo_extras_version_default: 8.0.20 +mongo_extras_version_default: 8.0.23 mongo_extras_version_4: 4.4.21 mongo_extras_version_5: 5.0.23 mongo_extras_version_6: 6.0.12 mongo_extras_version_7: 7.0.12 -mongo_extras_version_8: 8.0.20 +mongo_extras_version_8: 8.0.23 # Maximo Application Suite # ----------------------------------------------------------------------------- diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 330777ca..d5a45649 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -42,12 +42,12 @@ tsm_version: 1.7.7 # Updated # Dependencies - MongoDB # ----------------------------------------------------------------------------- -mongo_extras_version_default: 8.0.20 +mongo_extras_version_default: 8.0.23 mongo_extras_version_4: 4.4.21 mongo_extras_version_5: 5.0.23 mongo_extras_version_6: 6.0.12 mongo_extras_version_7: 7.0.12 -mongo_extras_version_8: 8.0.20 +mongo_extras_version_8: 8.0.23 # Maximo Application Suite # ----------------------------------------------------------------------------- From fce82703a9ce1dc4ddd1622e5e15bcf2e8c9421f Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 29 Jun 2026 15:39:03 +0530 Subject: [PATCH 05/30] [patch] Remove 9.2.x entries from catalog YAML --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 88026e85..a12bd174 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -125,13 +125,11 @@ mas_core_version: 8.10.x: 8.10.37 # No Update 8.11.x: 8.11.34 # No Update mas_assist_version: - 9.2.x: 9.2.0 # Not Supported 9.1.x: 9.1.12 # Updated 9.0.x: 9.0.18 # Updated 8.10.x: 8.7.8 # No Update 8.11.x: 8.8.7 # No Update mas_hputilities_version: - 9.2.x: 9.2.0 # Not Supported 9.1.x: "" # Not Supported 9.0.x: "" # Not Supported 8.10.x: 8.6.7 # No Update From 22f3897a5eb788a59236d2dd809ed702e8d2f7fb Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 29 Jun 2026 15:54:01 +0530 Subject: [PATCH 06/30] [patch] Remove 9.2.x entries from catalog --- src/mas/devops/data/catalogs/v9-260625-amd64.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260625-amd64.yaml b/src/mas/devops/data/catalogs/v9-260625-amd64.yaml index b4f62c7e..e8e8b15d 100644 --- a/src/mas/devops/data/catalogs/v9-260625-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260625-amd64.yaml @@ -125,13 +125,11 @@ mas_core_version: 8.10.x: 8.10.37 # No Update 8.11.x: 8.11.34 # No Update mas_assist_version: - 9.2.x: 9.2.0 # Not Supported 9.1.x: 9.1.12 # Updated 9.0.x: 9.0.18 # Updated 8.10.x: 8.7.8 # No Update 8.11.x: 8.8.7 # No Update mas_hputilities_version: - 9.2.x: 9.2.0 # Not Supported 9.1.x: "" # Not Supported 9.0.x: "" # Not Supported 8.10.x: 8.6.7 # No Update From 6d7f80d99d21ad3ec45c4f696049c482cd972a61 Mon Sep 17 00:00:00 2001 From: Ian Boden <82514609+IanBoden@users.noreply.github.com> Date: Mon, 6 Jul 2026 14:48:44 +0100 Subject: [PATCH 07/30] [patch] merge from stable (#418) Co-authored-by: Divyesh-Khokhar Co-authored-by: Raahithyaj Co-authored-by: amitpandey0217 --- .secrets.baseline | 4 ++-- src/mas/devops/db2.py | 4 ++++ .../templates/pipelinerun-install.yml.j2 | 23 +++++++++++++++++++ test/src/test_db2.py | 6 +++++ 4 files changed, 35 insertions(+), 2 deletions(-) diff --git a/.secrets.baseline b/.secrets.baseline index dfa6a6f7..046b9045 100644 --- a/.secrets.baseline +++ b/.secrets.baseline @@ -3,7 +3,7 @@ "files": "^.secrets.baseline$", "lines": null }, - "generated_at": "2026-06-19T12:37:02Z", + "generated_at": "2026-07-03T11:02:31Z", "plugins_used": [ { "name": "AWSKeyDetector" @@ -178,7 +178,7 @@ "hashed_secret": "a4b48a81cdab1e1a5dd37907d6c85ca1c61ddc7c", "is_secret": false, "is_verified": false, - "line_number": 241, + "line_number": 247, "type": "Secret Keyword", "verified_result": null } diff --git a/src/mas/devops/db2.py b/src/mas/devops/db2.py index f7f89b7c..6148bff6 100644 --- a/src/mas/devops/db2.py +++ b/src/mas/devops/db2.py @@ -189,6 +189,10 @@ def cr_pod_v_matches(cr_k: str, cr_v: str, pod_v: str) -> bool: # db2 appends something like "/NODE0000/LOGSTREAM0000/" to the cr_v in these cases return pod_v.startswith(cr_v) + # special case for ENCRLIB — DB2 resolves the symlink and stores the full absolute path, so just check if the library name is present + if cr_k == "ENCRLIB": + return cr_v in pod_v + # Look for e.g. 8192 AUTOMATIC -> AUTOMATIC(8192) matches = re.search(r"(\d+)\s*AUTOMATIC", cr_v, re.IGNORECASE) if matches is not None: diff --git a/src/mas/devops/templates/pipelinerun-install.yml.j2 b/src/mas/devops/templates/pipelinerun-install.yml.j2 index 5ebb7805..668e7c71 100644 --- a/src/mas/devops/templates/pipelinerun-install.yml.j2 +++ b/src/mas/devops/templates/pipelinerun-install.yml.j2 @@ -1005,6 +1005,29 @@ spec: value: "{{ aiservice_certificate_issuer }}" {%- endif %} + # AI Service - Database Configuration + # ------------------------------------------------------------------------- +{%- if install_db2 is defined %} + - name: install_db2 + value: "{{ install_db2 }}" +{%- endif %} +{%- if aiservice_db_jdbc_url is defined and aiservice_db_jdbc_url != "" %} + - name: aiservice_db_jdbc_url + value: "{{ aiservice_db_jdbc_url }}" +{%- endif %} +{%- if aiservice_db_username is defined and aiservice_db_username != "" %} + - name: aiservice_db_username + value: "{{ aiservice_db_username }}" +{%- endif %} +{%- if aiservice_db_password is defined and aiservice_db_password != "" %} + - name: aiservice_db_password + value: "{{ aiservice_db_password }}" +{%- endif %} +{%- if aiservice_db_ca_cert is defined and aiservice_db_ca_cert != "" %} + - name: aiservice_db_ca_cert + value: "{{ aiservice_db_ca_cert }}" +{%- endif %} + {%- endif %} workspaces: diff --git a/test/src/test_db2.py b/test/src/test_db2.py index c6feaa43..5f26c803 100644 --- a/test/src/test_db2.py +++ b/test/src/test_db2.py @@ -49,6 +49,12 @@ ("X", "otherSTRING", "OTHERstring", False), ("X", "other string", "other string", True), ("X", "22", "22", True), + # ENCRLIB — short filename in CR, full absolute path in pod → should pass + ("ENCRLIB", "libdb2compr_encr.so", "/opt/ibm/db2/V11.5.0.0/lib64/libdb2compr_encr.so.1", True), + # ENCRLIB — future DB2 version path → should still pass + ("ENCRLIB", "libdb2compr_encr.so", "/opt/ibm/db2/V11.5.10.0/lib64/libdb2compr_encr.so.1", True), + # ENCRLIB — completely wrong library → should fail + ("ENCRLIB", "libdb2compr_encr.so", "/opt/ibm/db2/V11.5.0.0/lib64/somewronglibrary.so", False), ], ) def test_cr_pod_v_matches(cr_k, cr_v, pod_v, expected): From cff9af6e7a0aaeea3078efb968f4f8d92bc0adc1 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Tue, 7 Jul 2026 18:03:45 +0530 Subject: [PATCH 08/30] [patch] Support July Catalog Update (#420) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index a12bd174..430f3316 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:3a9f89efcdefc8b0bba4deaf2efea2b17835880ba17215274637a93b30f126b0 +catalog_digest: sha256:d9ba3d2fd94d4b0b8fb1fa8eb5740a3122b137264b7da5c49818f7d9df966508 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 77e56d9a..ff84a42e 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:d82533f5f713fe4f9ec265009ce7d32f6094671c936a31565f98a512916205f2 +catalog_digest: sha256:40d3ec2da2fcb7a4444b4e481ad54a8a0ef2f902bb520dbf22c231a6944da265 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index d5a45649..4c460901 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:d7c156afa72073c9b47773e1113a06a841d538c5c0e8878bc39bf8bd62dd5aa4 +catalog_digest: sha256:7d57ef678d387fd43344cee3d17e88207569f26071318fd74fac6e1bcff957a0 ocp_compatibility: - "4.16" From cfe07f05ea2da07538db29602f3cb0758193ba83 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Sat, 11 Jul 2026 19:08:23 +0530 Subject: [PATCH 09/30] [patch] Support July Catalog Update (#423) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 430f3316..91bb03c4 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:d9ba3d2fd94d4b0b8fb1fa8eb5740a3122b137264b7da5c49818f7d9df966508 +catalog_digest: sha256:3055d67dcab3c6a59f7b0b6dd67fa718718f82daa0016719af821e10ffa22f2f ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index ff84a42e..4ca30c33 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:40d3ec2da2fcb7a4444b4e481ad54a8a0ef2f902bb520dbf22c231a6944da265 +catalog_digest: sha256:588922096642abb34873b6bec9a9cebaed0cb42623c15b56dd54c2dc621ed6bd ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 4c460901..84400d18 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:7d57ef678d387fd43344cee3d17e88207569f26071318fd74fac6e1bcff957a0 +catalog_digest: sha256:b20802a384c8a4aae47949a51b7dffbae5ed585e261f06b59c6ad7ef1a88f231 ocp_compatibility: - "4.16" From 78b57f8c1334408382d711bb64e93e21edddc8bd Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 16 Jul 2026 15:42:23 +0530 Subject: [PATCH 10/30] [patch] Support July Catalog Update (#428) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 91bb03c4..dac177a3 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:3055d67dcab3c6a59f7b0b6dd67fa718718f82daa0016719af821e10ffa22f2f +catalog_digest: sha256:c26bef1f488e0f04bbc0d433cc966e41195a114ea128ab825f74802f6cc8edba ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 4ca30c33..13a44e34 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:588922096642abb34873b6bec9a9cebaed0cb42623c15b56dd54c2dc621ed6bd +catalog_digest: sha256:eb377e7549abd533b67991d2d728f9603f184efc400d5014c001695008a8541a ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 84400d18..7644991b 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:b20802a384c8a4aae47949a51b7dffbae5ed585e261f06b59c6ad7ef1a88f231 +catalog_digest: sha256:8706e0b7c1da7254d77f9e645d4cb6a0aa998904d3c6f08f1809ce5aa3cf75dd ocp_compatibility: - "4.16" From d3a9a1d3e0f829a18eb52d19c097de99f5bcfb76 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Tue, 21 Jul 2026 16:51:44 +0530 Subject: [PATCH 11/30] [patch] Support July Catalog Update (#429) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index dac177a3..e25037e9 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:c26bef1f488e0f04bbc0d433cc966e41195a114ea128ab825f74802f6cc8edba +catalog_digest: sha256:b89f1439b6fcf0f8a92ec2204259712c280ae3ef3322345c7f188b03c92cb543 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 1ddfd8cc..4ebfedaa 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:eb377e7549abd533b67991d2d728f9603f184efc400d5014c001695008a8541a +catalog_digest: sha256:579d79a2ef89c2f2b314f480fc21a1bd0d1947177419fd89f3a1e0482e41c166 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index edae2b15..06b958e8 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:8706e0b7c1da7254d77f9e645d4cb6a0aa998904d3c6f08f1809ce5aa3cf75dd +catalog_digest: sha256:4b0bb697c643c0ebcd4c4d146db33aad67f37ec9329bdcbed48258753413570d ocp_compatibility: - "4.16" From 22ff008c4f5321bf877856c4f6ffd13e9a5f539e Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Wed, 22 Jul 2026 19:34:53 +0530 Subject: [PATCH 12/30] [patch] Support July Catalog Update (#430) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 4 ++-- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index e25037e9..8afc2942 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:b89f1439b6fcf0f8a92ec2204259712c280ae3ef3322345c7f188b03c92cb543 +catalog_digest: sha256:694c446a7ff4ca0f1c588d2b1f28711234aa21f7e928b5eb086abccc54e477ea ocp_compatibility: - "4.16" @@ -177,7 +177,7 @@ mas_visualinspection_version: 8.10.x: 8.8.4 # No Update 8.11.x: 8.9.21 # No Update mas_facilities_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.12 # Updated 9.0.x: "" # Not Supported diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 4ebfedaa..7add946d 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:579d79a2ef89c2f2b314f480fc21a1bd0d1947177419fd89f3a1e0482e41c166 +catalog_digest: sha256:298ab7081752923799d4ddb63f1a9d5b8e23b43900970719d896c32ac7552c69 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 06b958e8..e518d5c6 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:4b0bb697c643c0ebcd4c4d146db33aad67f37ec9329bdcbed48258753413570d +catalog_digest: sha256:4286a995285364b4befdb991d72ce0d4bd31a8107f245c25a8e8556b1ee99665 ocp_compatibility: - "4.16" From 69c5b9733a1c2fa8fd08d0a38df559b56ea7d923 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Wed, 22 Jul 2026 19:52:09 +0530 Subject: [PATCH 13/30] [patch] Support July Catalog Update (#431) --- .../devops/data/catalogs/v9-260730-amd64.yaml | 34 +++++++++---------- .../data/catalogs/v9-260730-ppc64le.yaml | 10 +++--- .../devops/data/catalogs/v9-260730-s390x.yaml | 10 +++--- 3 files changed, 27 insertions(+), 27 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 8afc2942..71b447c6 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:694c446a7ff4ca0f1c588d2b1f28711234aa21f7e928b5eb086abccc54e477ea +catalog_digest: sha256:81c1a61a26fa0b6bcfb77729f253e3497d481871918909d83fd238d8a6363f98 ocp_compatibility: - "4.16" @@ -118,15 +118,15 @@ redis_extras_version: 2.1.40 # No Update # Maximo Application Suite # ----------------------------------------------------------------------------- mas_core_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: 8.10.37 # No Update 8.11.x: 8.11.34 # No Update mas_assist_version: - 9.1.x: 9.1.12 # Updated - 9.0.x: 9.0.18 # Updated + 9.1.x: 9.1.13 # Updated + 9.0.x: 9.0.19 # Updated 8.10.x: 8.7.8 # No Update 8.11.x: 8.8.7 # No Update mas_hputilities_version: @@ -135,45 +135,45 @@ mas_hputilities_version: 8.10.x: 8.6.7 # No Update 8.11.x: "" # Not Supported mas_iot_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.12 # Updated 9.0.x: 9.0.21 # Updated 8.10.x: 8.7.33 # No Update 8.11.x: 8.8.30 # No Update mas_manage_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: 8.6.38 # No Update 8.11.x: 8.7.32 # No Update mas_monitor_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.12 # Updated - 9.0.x: 9.0.22 # Updated + 9.1.x: 9.1.13 # Updated + 9.0.x: 9.0.23 # Updated 8.10.x: 8.10.30 # No Update 8.11.x: 8.11.28 # No Update mas_optimizer_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.13 # Updated - 9.0.x: 9.0.24 # Updated + 9.0.x: 9.0.25 # Updated 8.10.x: 8.4.28 # Updated 8.11.x: 8.5.28 # Updated mas_predict_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.9 # Updated 9.0.x: 9.0.16 # Updated 8.10.x: 8.8.15 # No Update 8.11.x: 8.9.17 # No Update mas_visualinspection_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.18 # Updated - 9.0.x: 9.0.21 # Updated + 9.0.x: 9.0.22 # Updated 8.10.x: 8.8.4 # No Update 8.11.x: 8.9.21 # No Update mas_facilities_version: @@ -190,7 +190,7 @@ mas_facilities_version: aiservice_version: 9.2.x: 9.2.0 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.16 # Updated + 9.1.x: 9.1.17 # Updated aiservice_tenant_version: 9.2.x: 9.2.0 # Updated diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 7add946d..fb7e8871 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:298ab7081752923799d4ddb63f1a9d5b8e23b43900970719d896c32ac7552c69 +catalog_digest: sha256:80ddd13d474837fd09a9a8c9e5db194edd33a037dec8d12dae7a4d005fbad0c1 ocp_compatibility: - "4.16" @@ -52,17 +52,17 @@ mongo_extras_version_8: 8.0.23 # Maximo Application Suite # ----------------------------------------------------------------------------- mas_core_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index e518d5c6..66860175 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:4286a995285364b4befdb991d72ce0d4bd31a8107f245c25a8e8556b1ee99665 +catalog_digest: sha256:7027a69d9c7cdd54657762fb8a30d3a5625b6eede69bc380a83b156ca660bc8d ocp_compatibility: - "4.16" @@ -52,17 +52,17 @@ mongo_extras_version_8: 8.0.23 # Maximo Application Suite # ----------------------------------------------------------------------------- mas_core_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.19 # Updated - 9.0.x: 9.0.27 # Updated + 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported From 18f9ef50533dd8d5c83d954b8ae765aa63470e4d Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 23 Jul 2026 13:54:51 +0530 Subject: [PATCH 14/30] [patch] Support July Catalog Update (#432) --- .../devops/data/catalogs/v9-260730-amd64.yaml | 22 +++++++++---------- .../data/catalogs/v9-260730-ppc64le.yaml | 6 ++--- .../devops/data/catalogs/v9-260730-s390x.yaml | 6 ++--- 3 files changed, 17 insertions(+), 17 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 71b447c6..a54ed78e 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:81c1a61a26fa0b6bcfb77729f253e3497d481871918909d83fd238d8a6363f98 +catalog_digest: sha256:4f32c77bee644e6eb4b62f81540714f0c6454ea2c85408de124c4aa8913dc271 ocp_compatibility: - "4.16" @@ -120,7 +120,7 @@ redis_extras_version: 2.1.40 # No Update mas_core_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: 8.10.37 # No Update 8.11.x: 8.11.34 # No Update @@ -137,14 +137,14 @@ mas_hputilities_version: mas_iot_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.12 # Updated - 9.0.x: 9.0.21 # Updated + 9.1.x: 9.1.13 # Updated + 9.0.x: 9.0.22 # Updated 8.10.x: 8.7.33 # No Update 8.11.x: 8.8.30 # No Update mas_manage_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: 8.6.38 # No Update 8.11.x: 8.7.32 # No Update @@ -158,28 +158,28 @@ mas_monitor_version: mas_optimizer_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.13 # Updated + 9.1.x: 9.1.14 # Updated 9.0.x: 9.0.25 # Updated 8.10.x: 8.4.28 # Updated 8.11.x: 8.5.28 # Updated mas_predict_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.9 # Updated - 9.0.x: 9.0.16 # Updated + 9.1.x: 9.1.10 # Updated + 9.0.x: 9.0.17 # Updated 8.10.x: 8.8.15 # No Update 8.11.x: 8.9.17 # No Update mas_visualinspection_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.18 # Updated + 9.1.x: 9.1.19 # Updated 9.0.x: 9.0.22 # Updated 8.10.x: 8.8.4 # No Update 8.11.x: 8.9.21 # No Update mas_facilities_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.12 # Updated + 9.1.x: 9.1.13 # Updated 9.0.x: "" # Not Supported 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported @@ -188,7 +188,7 @@ mas_facilities_version: # Maximo AI Service # ------------------------------------------------------------------------------ aiservice_version: - 9.2.x: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated 9.1.x: 9.1.17 # Updated diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index fb7e8871..32a4a95e 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:80ddd13d474837fd09a9a8c9e5db194edd33a037dec8d12dae7a4d005fbad0c1 +catalog_digest: sha256:6fbcc161c974a1b5e21136a84c084d07053a877b7c098a53146bda0e71c9ff6d ocp_compatibility: - "4.16" @@ -54,14 +54,14 @@ mongo_extras_version_8: 8.0.23 mas_core_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 66860175..71671c13 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:7027a69d9c7cdd54657762fb8a30d3a5625b6eede69bc380a83b156ca660bc8d +catalog_digest: sha256:6d5cefc8a3e09e32b3895c47fb1987d9068e5cf5b690a41b649d133eab7041a4 ocp_compatibility: - "4.16" @@ -54,14 +54,14 @@ mongo_extras_version_8: 8.0.23 mas_core_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: 9.2.x: 9.2.1 # Updated 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.19 # Updated + 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported From 55cbea8c77305ec99d3dbb58493aad3f375b7044 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 23 Jul 2026 14:06:47 +0530 Subject: [PATCH 15/30] [patch] updated apps and status --- .../devops/data/catalogs/v9-260730-amd64.yaml | 28 +++++++++---------- .../data/catalogs/v9-260730-ppc64le.yaml | 4 +-- .../devops/data/catalogs/v9-260730-s390x.yaml | 4 +-- 3 files changed, 18 insertions(+), 18 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index a54ed78e..feb1de6a 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -119,7 +119,7 @@ redis_extras_version: 2.1.40 # No Update # ----------------------------------------------------------------------------- mas_core_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: 8.10.37 # No Update @@ -136,49 +136,49 @@ mas_hputilities_version: 8.11.x: "" # Not Supported mas_iot_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.13 # Updated 9.0.x: 9.0.22 # Updated 8.10.x: 8.7.33 # No Update 8.11.x: 8.8.30 # No Update mas_manage_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: 8.6.38 # No Update 8.11.x: 8.7.32 # No Update mas_monitor_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.13 # Updated 9.0.x: 9.0.23 # Updated 8.10.x: 8.10.30 # No Update 8.11.x: 8.11.28 # No Update mas_optimizer_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.14 # Updated 9.0.x: 9.0.25 # Updated - 8.10.x: 8.4.28 # Updated - 8.11.x: 8.5.28 # Updated + 8.10.x: 8.4.28 # No Update + 8.11.x: 8.5.28 # No Update mas_predict_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated - 9.1.x: 9.1.10 # Updated + 9.2.x-feature: 9.2.0 # No Update + 9.1.x: 9.1.10 # Updated 9.0.x: 9.0.17 # Updated 8.10.x: 8.8.15 # No Update 8.11.x: 8.9.17 # No Update mas_visualinspection_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.19 # Updated 9.0.x: 9.0.22 # Updated 8.10.x: 8.8.4 # No Update 8.11.x: 8.9.21 # No Update mas_facilities_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.13 # Updated 9.0.x: "" # Not Supported 8.10.x: "" # Not Supported @@ -189,12 +189,12 @@ mas_facilities_version: # ------------------------------------------------------------------------------ aiservice_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.17 # Updated aiservice_tenant_version: - 9.2.x: 9.2.0 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x: 9.2.1 # Updated + 9.2.x-feature: 9.2.0 # No Update # Editorial diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 32a4a95e..41555396 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -53,14 +53,14 @@ mongo_extras_version_8: 8.0.23 # ----------------------------------------------------------------------------- mas_core_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 71671c13..3b092343 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -53,14 +53,14 @@ mongo_extras_version_8: 8.0.23 # ----------------------------------------------------------------------------- mas_core_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported 8.11.x: "" # Not Supported mas_manage_version: 9.2.x: 9.2.1 # Updated - 9.2.x-feature: 9.2.0 # Updated + 9.2.x-feature: 9.2.0 # No Update 9.1.x: 9.1.20 # Updated 9.0.x: 9.0.28 # Updated 8.10.x: "" # Not Supported From 07f6dcadb8085f28071adb4730afb4ab1f2e75e5 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Fri, 24 Jul 2026 09:22:51 +0530 Subject: [PATCH 16/30] [patch] Support July Catalog Update (#433) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index feb1de6a..8f62b7b1 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:4f32c77bee644e6eb4b62f81540714f0c6454ea2c85408de124c4aa8913dc271 +catalog_digest: sha256:b40764ca34f56edd8e3f8d029aed9e9eb93d54ea1b63f6364f8f13f50f089771 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 41555396..6dea4a53 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:6fbcc161c974a1b5e21136a84c084d07053a877b7c098a53146bda0e71c9ff6d +catalog_digest: sha256:a414ca5c7c5ab647fb5478cc48f2da20a95226763d0d9b6f4830fc6a57d8c983 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 3b092343..79ad3b0d 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:6d5cefc8a3e09e32b3895c47fb1987d9068e5cf5b690a41b649d133eab7041a4 +catalog_digest: sha256:ae636f5ac30ea171daeca26d8ba7871042f33826c0a50982716589160dbd30bb ocp_compatibility: - "4.16" From 0765207b6c9c36767b7c851d2d2e8f42e240ec57 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Sat, 25 Jul 2026 12:30:02 +0530 Subject: [PATCH 17/30] [patch] Always create pipeline-db2-license secret in prepareUpdateSecrets regardless of Slack config The prepareUpdateSecrets() function in tekton.py was introduced in PR #425 ("day2 fix for devops slack secret issue") which added an early return when slack_token or slack_channel are not provided. This inadvertently placed the pipeline-db2-license secret creation after the early return, meaning the secret was never created for users who do not have Slack configured. The PipelineRun template (pipelinerun-update.yml.j2) unconditionally binds the shared-db2 workspace to secretName: pipeline-db2-license. When the secret does not exist, the update-db2 task pod is stuck in Init:0/2 with repeated FailedMount errors, blocking the entire mas-update pipeline run. Fix: move pipeline-db2-license secret creation before the Slack guard so it is always created regardless of whether Slack credentials are provided. --- src/mas/devops/tekton.py | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-) diff --git a/src/mas/devops/tekton.py b/src/mas/devops/tekton.py index 4d81a14d..7204c5d6 100644 --- a/src/mas/devops/tekton.py +++ b/src/mas/devops/tekton.py @@ -983,16 +983,33 @@ def prepareUpdateSecrets( namespaceAPI = dynClient.resources.get(api_version="v1", kind="Namespace") namespaceAPI.get(name=namespace) except NotFoundError: - logger.warning(f"Namespace {namespace} does not exist, skipping slack secret creation") + logger.warning(f"Namespace {namespace} does not exist, skipping secret creation") return - # Only create secret if both slack_token and slack_channel are provided + secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") + + # Always create pipeline-db2-license secret — required by the PipelineRun workspace + # binding regardless of whether a license file was provided or Slack is configured + try: + secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) + except NotFoundError: + pass + + if db2LicenseFile is None: + db2LicenseFile = { + "apiVersion": "v1", + "kind": "Secret", + "type": "Opaque", + "metadata": {"name": "pipeline-db2-license"}, + } + secretsAPI.create(body=db2LicenseFile, namespace=namespace) + logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") + + # Only create mas-devops-slack secret if both slack_token and slack_channel are provided if not slack_token or not slack_channel: logger.debug("Slack token or channel not provided, skipping slack secret creation") return - secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") - # Delete existing secret if it exists try: secretsAPI.delete(name="mas-devops-slack", namespace=namespace) @@ -1019,21 +1036,6 @@ def prepareUpdateSecrets( secretsAPI.create(body=mas_devops_secret, namespace=namespace) logger.info(f"Created mas-devops-slack secret in namespace {namespace}") - try: - secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) - except NotFoundError: - pass - - if db2LicenseFile is None: - db2LicenseFile = { - "apiVersion": "v1", - "kind": "Secret", - "type": "Opaque", - "metadata": {"name": "pipeline-db2-license"}, - } - secretsAPI.create(body=db2LicenseFile, namespace=namespace) - logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") - def testCLI() -> None: pass From a5a3708909c63faa32e8d1924a61fca37c8f21a1 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 27 Jul 2026 21:21:35 +0530 Subject: [PATCH 18/30] Revert "[patch] Always create pipeline-db2-license secret in prepareUpdateSecrets regardless of Slack config" This reverts commit 0765207b6c9c36767b7c851d2d2e8f42e240ec57. --- src/mas/devops/tekton.py | 40 +++++++++++++++++++--------------------- 1 file changed, 19 insertions(+), 21 deletions(-) diff --git a/src/mas/devops/tekton.py b/src/mas/devops/tekton.py index 7204c5d6..4d81a14d 100644 --- a/src/mas/devops/tekton.py +++ b/src/mas/devops/tekton.py @@ -983,33 +983,16 @@ def prepareUpdateSecrets( namespaceAPI = dynClient.resources.get(api_version="v1", kind="Namespace") namespaceAPI.get(name=namespace) except NotFoundError: - logger.warning(f"Namespace {namespace} does not exist, skipping secret creation") + logger.warning(f"Namespace {namespace} does not exist, skipping slack secret creation") return - secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") - - # Always create pipeline-db2-license secret — required by the PipelineRun workspace - # binding regardless of whether a license file was provided or Slack is configured - try: - secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) - except NotFoundError: - pass - - if db2LicenseFile is None: - db2LicenseFile = { - "apiVersion": "v1", - "kind": "Secret", - "type": "Opaque", - "metadata": {"name": "pipeline-db2-license"}, - } - secretsAPI.create(body=db2LicenseFile, namespace=namespace) - logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") - - # Only create mas-devops-slack secret if both slack_token and slack_channel are provided + # Only create secret if both slack_token and slack_channel are provided if not slack_token or not slack_channel: logger.debug("Slack token or channel not provided, skipping slack secret creation") return + secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") + # Delete existing secret if it exists try: secretsAPI.delete(name="mas-devops-slack", namespace=namespace) @@ -1036,6 +1019,21 @@ def prepareUpdateSecrets( secretsAPI.create(body=mas_devops_secret, namespace=namespace) logger.info(f"Created mas-devops-slack secret in namespace {namespace}") + try: + secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) + except NotFoundError: + pass + + if db2LicenseFile is None: + db2LicenseFile = { + "apiVersion": "v1", + "kind": "Secret", + "type": "Opaque", + "metadata": {"name": "pipeline-db2-license"}, + } + secretsAPI.create(body=db2LicenseFile, namespace=namespace) + logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") + def testCLI() -> None: pass From ab5f90cb144b45e3a6fd834ebca45f2ae12c6cf4 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 27 Jul 2026 21:27:16 +0530 Subject: [PATCH 19/30] [patch] exclude openshift integration tests from standard CI run Add `-m "not openshift"` to pytest invocation in python-package.yml to prevent OLM integration tests from running in environments without the IBM operator catalog installed. Tests in test_olm.py require a live OpenShift cluster with ibm-sls available in openshift-marketplace. The `openshift` marker was already defined in pyproject.toml but was not being applied during CI. --- .github/workflows/python-package.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/python-package.yml b/.github/workflows/python-package.yml index edb21ef4..e3104427 100644 --- a/.github/workflows/python-package.yml +++ b/.github/workflows/python-package.yml @@ -46,7 +46,7 @@ jobs: cat ${GITHUB_WORKSPACE}/src/mas/devops/__init__.py python -m pip install --upgrade pip pip install .[dev] - python -m pytest + python -m pytest -m "not openshift" - name: Lint with flake8 run: | From b839fd591be8e4d18a36c1794df5a89ef343c303 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 27 Jul 2026 21:28:35 +0530 Subject: [PATCH 20/30] Revert "[patch] exclude openshift integration tests from standard CI run" This reverts commit ab5f90cb144b45e3a6fd834ebca45f2ae12c6cf4. --- .github/workflows/python-package.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/python-package.yml b/.github/workflows/python-package.yml index e3104427..edb21ef4 100644 --- a/.github/workflows/python-package.yml +++ b/.github/workflows/python-package.yml @@ -46,7 +46,7 @@ jobs: cat ${GITHUB_WORKSPACE}/src/mas/devops/__init__.py python -m pip install --upgrade pip pip install .[dev] - python -m pytest -m "not openshift" + python -m pytest - name: Lint with flake8 run: | From 3bba884bddfb7ce9d802fbfd2fba5e1939d1911d Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 27 Jul 2026 21:30:31 +0530 Subject: [PATCH 21/30] Reapply "[patch] exclude openshift integration tests from standard CI run" This reverts commit b839fd591be8e4d18a36c1794df5a89ef343c303. --- .github/workflows/python-package.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/python-package.yml b/.github/workflows/python-package.yml index edb21ef4..e3104427 100644 --- a/.github/workflows/python-package.yml +++ b/.github/workflows/python-package.yml @@ -46,7 +46,7 @@ jobs: cat ${GITHUB_WORKSPACE}/src/mas/devops/__init__.py python -m pip install --upgrade pip pip install .[dev] - python -m pytest + python -m pytest -m "not openshift" - name: Lint with flake8 run: | From 115a40e02c79ccd0df960d180ad935f223bae4b3 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Mon, 27 Jul 2026 22:00:09 +0530 Subject: [PATCH 22/30] Reapply "[patch] Always create pipeline-db2-license secret in prepareUpdateSecrets regardless of Slack config" This reverts commit a5a3708909c63faa32e8d1924a61fca37c8f21a1. --- src/mas/devops/tekton.py | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-) diff --git a/src/mas/devops/tekton.py b/src/mas/devops/tekton.py index 4d81a14d..7204c5d6 100644 --- a/src/mas/devops/tekton.py +++ b/src/mas/devops/tekton.py @@ -983,16 +983,33 @@ def prepareUpdateSecrets( namespaceAPI = dynClient.resources.get(api_version="v1", kind="Namespace") namespaceAPI.get(name=namespace) except NotFoundError: - logger.warning(f"Namespace {namespace} does not exist, skipping slack secret creation") + logger.warning(f"Namespace {namespace} does not exist, skipping secret creation") return - # Only create secret if both slack_token and slack_channel are provided + secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") + + # Always create pipeline-db2-license secret — required by the PipelineRun workspace + # binding regardless of whether a license file was provided or Slack is configured + try: + secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) + except NotFoundError: + pass + + if db2LicenseFile is None: + db2LicenseFile = { + "apiVersion": "v1", + "kind": "Secret", + "type": "Opaque", + "metadata": {"name": "pipeline-db2-license"}, + } + secretsAPI.create(body=db2LicenseFile, namespace=namespace) + logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") + + # Only create mas-devops-slack secret if both slack_token and slack_channel are provided if not slack_token or not slack_channel: logger.debug("Slack token or channel not provided, skipping slack secret creation") return - secretsAPI = dynClient.resources.get(api_version="v1", kind="Secret") - # Delete existing secret if it exists try: secretsAPI.delete(name="mas-devops-slack", namespace=namespace) @@ -1019,21 +1036,6 @@ def prepareUpdateSecrets( secretsAPI.create(body=mas_devops_secret, namespace=namespace) logger.info(f"Created mas-devops-slack secret in namespace {namespace}") - try: - secretsAPI.delete(name="pipeline-db2-license", namespace=namespace) - except NotFoundError: - pass - - if db2LicenseFile is None: - db2LicenseFile = { - "apiVersion": "v1", - "kind": "Secret", - "type": "Opaque", - "metadata": {"name": "pipeline-db2-license"}, - } - secretsAPI.create(body=db2LicenseFile, namespace=namespace) - logger.info(f"Created pipeline-db2-license secret in namespace {namespace}") - def testCLI() -> None: pass From a72352137bebabebc698adad8018a001ae2286d1 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Tue, 28 Jul 2026 10:55:33 +0530 Subject: [PATCH 23/30] Revert "Reapply "[patch] exclude openshift integration tests from standard CI run"" This reverts commit 3bba884bddfb7ce9d802fbfd2fba5e1939d1911d. --- .github/workflows/python-package.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/python-package.yml b/.github/workflows/python-package.yml index e3104427..edb21ef4 100644 --- a/.github/workflows/python-package.yml +++ b/.github/workflows/python-package.yml @@ -46,7 +46,7 @@ jobs: cat ${GITHUB_WORKSPACE}/src/mas/devops/__init__.py python -m pip install --upgrade pip pip install .[dev] - python -m pytest -m "not openshift" + python -m pytest - name: Lint with flake8 run: | From 521facc457b905c9b011025ad43a7a542fd63b55 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Tue, 28 Jul 2026 10:59:49 +0530 Subject: [PATCH 24/30] [patch] rebuild python --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 9abd019e..7ddcfcb7 100644 --- a/README.md +++ b/README.md @@ -89,3 +89,4 @@ Example of initial_users secret: ```json {"john.smith1@example.com":"primary,john1,smith1","john.smith2@example.com":"primary,john2,smith2","john.smith3@example.com":"secondary,john3,smith3"} ``` + From c7c5311df8686d7196158560934aca2f4474c1b5 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Tue, 28 Jul 2026 18:16:02 +0530 Subject: [PATCH 25/30] [patch] Support July Catalog Update (#437) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 8f62b7b1..517005df 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:b2ccc566eaceb98d3e4fd7a28ed1281fdf36f11d33bd28e939b4698df40f3cdc ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 6dea4a53..0332437e 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:91169165e01fe22e3049913a7c8eb120e2e028286ac02d002997b93224872599 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 79ad3b0d..e5a26e6c 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:9aff0c6c1ed729cb28c62056cf9609e21268c2408fe245caab9d941a298cd1df ocp_compatibility: - "4.16" From 67eda92b3c6758d1da99fd4e3fb0ca7d9606a7ce Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Wed, 29 Jul 2026 12:34:10 +0530 Subject: [PATCH 26/30] [doc] update doc --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 6 +++--- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 4 ++-- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 4 ++-- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 517005df..42f4bbfc 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -74,7 +74,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 @@ -91,13 +91,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 diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 0332437e..7ffaa229 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -31,13 +31,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 diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index e5a26e6c..710511a1 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -31,13 +31,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 From 91c8cdbe975fb6b6c559cb84b30ff98ced47ffc8 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Wed, 29 Jul 2026 12:37:52 +0530 Subject: [PATCH 27/30] [patch] update known issues --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 3 +-- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 3 +-- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 3 +-- 3 files changed, 3 insertions(+), 6 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 42f4bbfc..2524ab35 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -229,5 +229,4 @@ editorial: - IBM Suite License Service v3.13 - Amlen v1.1 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 7ffaa229..67337c3a 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -82,5 +82,4 @@ editorial: - IBM Truststore Manager v1.7 - IBM Suite License Service v3.13 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 710511a1..79691070 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -82,5 +82,4 @@ editorial: - IBM Truststore Manager v1.7 - IBM Suite License Service v3.13 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file From e16f079ca900b88f2016582e432a5b1f80e5ea01 Mon Sep 17 00:00:00 2001 From: Abhishekkushawaha <159771922+Abhishekkushawaha@users.noreply.github.com> Date: Wed, 29 Jul 2026 21:49:27 +0530 Subject: [PATCH 28/30] [patch] updated doc whats new in this release (#438) --- .../devops/data/catalogs/v9-260730-amd64.yaml | 35 ++++++------------- .../data/catalogs/v9-260730-ppc64le.yaml | 6 ++-- .../devops/data/catalogs/v9-260730-s390x.yaml | 6 ++-- 3 files changed, 14 insertions(+), 33 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 2524ab35..23cc71f3 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -201,32 +201,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 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 67337c3a..37083ea2 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -73,13 +73,11 @@ 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 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) - 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 known_issues: - 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 79691070..88e932da 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -73,13 +73,11 @@ 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 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) - 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 known_issues: - 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file From aee91314560f0305643fac432e2ea21b5359d2b8 Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 30 Jul 2026 11:19:40 +0530 Subject: [PATCH 29/30] [patch] Support July Catalog Update (#439) --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 2 +- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 23cc71f3..c0a24fd7 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/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:b2ccc566eaceb98d3e4fd7a28ed1281fdf36f11d33bd28e939b4698df40f3cdc +catalog_digest: sha256:8b78bc126d05663f881a44321fbda9a19076bb589a24f0c785fafef1fb56eab8 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 37083ea2..08d849b8 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/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:91169165e01fe22e3049913a7c8eb120e2e028286ac02d002997b93224872599 +catalog_digest: sha256:5944d34f9584733c806b0acc77e3490c8b64b640159b6944425136f976eb6427 ocp_compatibility: - "4.16" diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 88e932da..c325b58f 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/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:9aff0c6c1ed729cb28c62056cf9609e21268c2408fe245caab9d941a298cd1df +catalog_digest: sha256:84311732b6078cb9857ef557bcd4db64949a6c1d8ce351c6a4aac59ac08637cb ocp_compatibility: - "4.16" From 9dda1b85f6b1e490e0c44e3bf3f5af9da711facc Mon Sep 17 00:00:00 2001 From: Parveen Kumar Date: Thu, 30 Jul 2026 11:26:03 +0530 Subject: [PATCH 30/30] [patch] update whats new details --- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 6 +----- src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 6 +----- 2 files changed, 2 insertions(+), 10 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 08d849b8..47d5555d 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -71,13 +71,9 @@ mas_manage_version: # ------------------------------------------------------------------------------ editorial: whats_new: - - title: New feature release + - title: '**Security updates and bug fixes**' details: - 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) - - 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) known_issues: - 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index c325b58f..6739688b 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -71,13 +71,9 @@ mas_manage_version: # ------------------------------------------------------------------------------ editorial: whats_new: - - title: New feature release + - title: '**Security updates and bug fixes**' details: - 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) - - 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) known_issues: - 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--manage patch manageworkspace - --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas--manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the -- prefix from the returned PVC name. \ No newline at end of file