You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Deploying the latest nightly build v3 images to GKE results in the images failing to start. I see the same issue on the discovery, api and gateway services.
A quick google shows this error may happen with a mismatch in java versions compiled vs runtime.
Steps to Reproduce
Download latest nightly build for v3 containerized build
Deploy images to k8s
Inspect logs for pods.
Expected behavior
Pods should start.
Screenshots
Logs
Defaulted container "api-catalog" out of: api-catalog, init-zowe (init)
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:337) Zowe version: v2.1.0
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:338) build and hash: v2.x/staging#185 (a6f8a6ef4c2dc8decc8ad245e6148c858957aa34)
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:354) starting Zowe instance api_catalog_d6484df49_9bcjv with /home/zowe/instance/zowe.yaml ...
WARNING: /cloud-gateway/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
WARNING: /discovery/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
WARNING: /gateway/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
2024-08-14 20:06:46 ZWELS:1 zowe INFO (zwe-internal-start-prepare,global_validate:106) process global validations ...
2024-08-14 20:06:46 ZWELS:1 zowe INFO (zwe-internal-start-prepare,global_validate:145) global validations are successful
2024-08-14 20:06:47 ZWELS:1 zowe INFO (zwe-internal-start-prepare,configure_components:197) process component configurations ...
2024-08-14 20:06:50 ZWELS:1 zowe INFO (zwe-internal-start-prepare:387) Zowe runtime environment prepared
2024-08-14 20:06:53 ZWELS:1 zowe INFO (zwe-internal-start-component:63) starting component api-catalog ...
jar file: /home/zowe/runtime/components/api-catalog/bin/api-catalog-services-lite.jar
pid=2557
Unrecognized option: --add-opens=java.base/java.lang=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Details
Version and build number:
Tried a few images from jfrog
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:3.0.21-SNAPSHOT-ubuntu.v3-x-x
and
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:3.0.21-SNAPSHOT-ubuntu-amd64.v3-x-x-871
same error.
Additional context
Add any other context about the problem here.
Willingness to help
Willing to test out a new build.
Describe the bug
Deploying the latest nightly build v3 images to GKE results in the images failing to start. I see the same issue on the discovery, api and gateway services.
Unrecognized option: --add-opens=java.base/java.lang=ALL-UNNAMED
A quick google shows this error may happen with a mismatch in java versions compiled vs runtime.
Steps to Reproduce
Expected behavior
Pods should start.
Screenshots
Logs
Defaulted container "api-catalog" out of: api-catalog, init-zowe (init)
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:337) Zowe version: v2.1.0
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:338) build and hash: v2.x/staging#185 (a6f8a6ef4c2dc8decc8ad245e6148c858957aa34)
2024-08-14 20:06:41 ZWELS:1 zowe INFO (zwe-internal-start-prepare:354) starting Zowe instance api_catalog_d6484df49_9bcjv with /home/zowe/instance/zowe.yaml ...
WARNING: /cloud-gateway/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
WARNING: /discovery/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
WARNING: /gateway/.configs-api_catalog_d6484df49_9bcjv.json doesn't exist
2024-08-14 20:06:46 ZWELS:1 zowe INFO (zwe-internal-start-prepare,global_validate:106) process global validations ...
2024-08-14 20:06:46 ZWELS:1 zowe INFO (zwe-internal-start-prepare,global_validate:145) global validations are successful
2024-08-14 20:06:47 ZWELS:1 zowe INFO (zwe-internal-start-prepare,configure_components:197) process component configurations ...
2024-08-14 20:06:50 ZWELS:1 zowe INFO (zwe-internal-start-prepare:387) Zowe runtime environment prepared
2024-08-14 20:06:53 ZWELS:1 zowe INFO (zwe-internal-start-component:63) starting component api-catalog ...
jar file: /home/zowe/runtime/components/api-catalog/bin/api-catalog-services-lite.jar
pid=2557
Unrecognized option: --add-opens=java.base/java.lang=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Details
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:3.0.21-SNAPSHOT-ubuntu.v3-x-x
and
image: zowe-docker-snapshot.jfrog.io/ompzowe/api-catalog-services:3.0.21-SNAPSHOT-ubuntu-amd64.v3-x-x-871
same error.
Additional context
Add any other context about the problem here.
Willingness to help
Willing to test out a new build.
https://github.com/zowe/api-layer/wiki/Issue-management
The text was updated successfully, but these errors were encountered: