From 878492496d91d34b27dd06ac07f59c53e6707e30 Mon Sep 17 00:00:00 2001 From: Raj Bhavsar Date: Mon, 27 Jul 2026 17:40:20 +0530 Subject: [PATCH 1/3] [patch] MASCORE-15768: technote to add known issue for Civil Image Stitching PVC migration failure. --- src/mas/devops/data/catalogs/v9-260730-amd64.yaml | 1 + src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 1 + src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 1 + 3 files changed, 3 insertions(+) diff --git a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml index 8f62b7b1..8102be3e 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -231,3 +231,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index 6dea4a53..df0ad251 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -84,3 +84,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index 79ad3b0d..c8302f7c 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -84,3 +84,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. From 58dd2ecef2f3f51f4a4f1814963b23311a8a5c23 Mon Sep 17 00:00:00 2001 From: Raj Bhavsar Date: Mon, 27 Jul 2026 21:06:21 +0530 Subject: [PATCH 2/3] [patch] MASCORE-15768: update image stitching PVC recovery instructions --- 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 8102be3e..a4243413 100644 --- a/src/mas/devops/data/catalogs/v9-260730-amd64.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-amd64.yaml @@ -231,4 +231,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. + - 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. diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index df0ad251..b7b45873 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -84,4 +84,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. + - 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. diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index c8302f7c..a25ee8a1 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -84,4 +84,4 @@ editorial: 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 enters a permanent failure state post-upgrade due to a missing PVC migration. To recover, patch the CR spec with the existing PVC name: kubectl -n mas--manage patch imagestitching imagestitching --type merge -p '{"spec":{"settings":{"pvc":{"pvcname":"--imagestitching-pvc-in"}}}}'. + - 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. From 67a24d256f858f0100408ba534cc27b68da43665 Mon Sep 17 00:00:00 2001 From: Raj Bhavsar Date: Tue, 28 Jul 2026 11:11:52 +0530 Subject: [PATCH 3/3] [patch] MASCORE-15768: remove civil image stitching known issue from v9-260730 catalogs for ppc64le and s390x files. --- src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml | 1 - src/mas/devops/data/catalogs/v9-260730-s390x.yaml | 1 - 2 files changed, 2 deletions(-) diff --git a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml index b7b45873..6dea4a53 100644 --- a/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-ppc64le.yaml @@ -84,4 +84,3 @@ editorial: 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. diff --git a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml index a25ee8a1..79ad3b0d 100644 --- a/src/mas/devops/data/catalogs/v9-260730-s390x.yaml +++ b/src/mas/devops/data/catalogs/v9-260730-s390x.yaml @@ -84,4 +84,3 @@ editorial: 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.