Skip to content

Commit e16f079

Browse files
[patch] updated doc whats new in this release (#438)
1 parent 91c8cdb commit e16f079

3 files changed

Lines changed: 14 additions & 33 deletions

File tree

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

Lines changed: 10 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -201,32 +201,17 @@ aiservice_tenant_version:
201201
# ------------------------------------------------------------------------------
202202
editorial:
203203
whats_new:
204-
- title: New feature release
205-
details:
206-
- IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
207-
- IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
208-
- IBM Maximo Monitor/IoT [v9.2.0](https://www.ibm.com/support/pages/node/7277101)
209-
- IBM Maximo Optimizer [v9.2.0](https://www.ibm.com/support/pages/node/7276586)
210-
- IBM Maximo Predict [v9.2.0](https://www.ibm.com/support/pages/node/7275237)
211-
- IBM Maximo Visual Inspection [v9.2.0](https://www.ibm.com/support/pages/node/7277289)
212-
- IBM Maximo Real Estate and Facilities [v9.2.0](https://www.ibm.com/support/pages/node/7275247)
213-
- IBM Maximo AI Service [v9.2.0](https://www.ibm.com/support/pages/node/7276603)
214-
- IBM Maximo AI Service Tenant v9.2
215-
- IBM Maximo Location Service for Esri v9.2
216204
- title: '**Security updates and bug fixes**'
217205
details:
218-
- 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)
219-
- 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)
220-
- 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)
221-
- 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)
222-
- 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)
223-
- 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)
224-
- 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)
225-
- 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)
226-
- IBM Maximo Real Estate and Facilities [v9.1.12](https://www.ibm.com/support/pages/node/7276768)
227-
- IBM Maximo AI Service [v9.1.16](https://www.ibm.com/support/pages/node/7276604)
228-
- IBM Truststore Manager v1.7
229-
- IBM Suite License Service v3.13
230-
- Amlen v1.1
206+
- 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)
207+
- 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)
208+
- 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)
209+
- 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)
210+
- 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)
211+
- 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)
212+
- 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)
213+
- 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)
214+
- 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)
215+
- 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)
231216
known_issues:
232217
- title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-<instanceId>-manage patch manageworkspace <instanceId>-<workspaceId> --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-<instanceId>-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the <instanceId>-<workspaceId>- prefix from the returned PVC name.

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,11 @@ editorial:
7373
whats_new:
7474
- title: New feature release
7575
details:
76-
- IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
77-
- IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
76+
- 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)
77+
- 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)
7878
- title: '**Security updates and bug fixes**'
7979
details:
8080
- 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)
8181
- 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)
82-
- IBM Truststore Manager v1.7
83-
- IBM Suite License Service v3.13
8482
known_issues:
8583
- title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-<instanceId>-manage patch manageworkspace <instanceId>-<workspaceId> --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-<instanceId>-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the <instanceId>-<workspaceId>- prefix from the returned PVC name.

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

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,11 @@ editorial:
7373
whats_new:
7474
- title: New feature release
7575
details:
76-
- IBM Maximo Application Suite Core Platform [v9.2.0](https://www.ibm.com/support/pages/node/7277376)
77-
- IBM Maximo Manage [v9.2.0](https://www.ibm.com/support/pages/node/7276377)
76+
- 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)
77+
- 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)
7878
- title: '**Security updates and bug fixes**'
7979
details:
8080
- 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)
8181
- 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)
82-
- IBM Truststore Manager v1.7
83-
- IBM Suite License Service v3.13
8482
known_issues:
8583
- title: A known issue exists in the 9.0.x release affecting IBM Maximo Manage customers upgrading from 8.7.x to 9.0.x with the Civil component and Image Stitching deployed; the Image Stitching CR will not recover post-upgrade without manual intervention. To recover, patch the ManageWorkspace CR with kubectl -n mas-<instanceId>-manage patch manageworkspace <instanceId>-<workspaceId> --type merge -p '{"spec":{"components":{"civil":{"imagestitchingpvcname":"imagestitching-pvc-in"}}}}', replacing imagestitching-pvc-in with the value obtained by running kubectl -n mas-<instanceId>-manage get pvc -l app.kubernetes.io/component=imagestitching-api and stripping the <instanceId>-<workspaceId>- prefix from the returned PVC name.

0 commit comments

Comments
 (0)