Details
-
Bug
-
Resolution: Done
-
Blocker
-
fuse-7.4-GA
-
None
-
CR1
-
%
-
Fuse 7.4 Sprint 49 - Blocker 2, Fuse 7.5 Sprint 50 - Dev #1
Description
The productized build of the komodo server image [1] does not start. The pod fails with the following message:
no main manifest attribute, in /deployments/runtime.jar
Extracting the runtime.jar from the image and comparing with the upstream komodo server image [2] shows that the MANIFEST.MF files differ between the two images, the prod image missing several attributes, most notably the Main-Class attribute mentioned in the error message above. Attaching both MANIFEST.MF files for comparison.
Also, the prod image has the built classes directly in the jar root, whereas the upstream build has them under the BOOT-INF directory. Not sure this is significant.
[1] brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/fuse-7-tech-preview/data-virtualization-server:1.4-1
[2] teiid/komodo-server:latest