Skip to content

Commit e0f3eff

Browse files
[patch] added mvi know issue for the sep ga
1 parent 363be06 commit e0f3eff

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -217,4 +217,4 @@ editorial:
217217
- IBM Suite License Service v3.13.2
218218
- Mongo: 8.0.30
219219
known_issues:
220-
- title:
220+
- title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,4 +77,4 @@ editorial:
7777
- IBM Suite License Service v3.13.2
7878
- Mongo: 8.0.30
7979
known_issues:
80-
- title:
80+
- title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,5 +77,5 @@ editorial:
7777
- IBM Suite License Service v3.13
7878
- Mongo: 8.0.30
7979
known_issues:
80-
- title:
80+
- title: During an upgrade from MVI 9.0.x to 9.1.x, the vision-auth pod may fail to start due to an SSL hostname verification error when connecting to Valkey. Restart the Valkey and Auth deployments in the MVI namespace to resolve the issue.
8181

0 commit comments

Comments
 (0)