datahub 0.13.3: include required jetty-jmx.xml file
This file has only been introduced recently, along with the entrypoint change.
Including it should fix the error we've been seeing when running datahub-gms 0.13.3:
2024/07/18 09:33:20 Waiting for: http://datahubsearch.svc.eqiad.wmnet:9200
2024/07/18 09:33:20 Waiting for: tcp://an-test-coord1001.eqiad.wmnet:3306
2024/07/18 09:33:20 Waiting for: tcp://kafka-test1006.eqiad.wmnet:9092
2024/07/18 09:33:20 Connected to tcp://kafka-test1006.eqiad.wmnet:9092
2024/07/18 09:33:20 Connected to tcp://an-test-coord1001.eqiad.wmnet:3306
2024/07/18 09:33:21 Received 200 from http://datahubsearch.svc.eqiad.wmnet:9200
2024-07-18 09:33:21.304:INFO::main: Logging initialized @300ms to org.eclipse.jetty.util.log.StdErrLog
WARNING: jetty-runner is deprecated.
See Jetty Documentation for startup options
https://www.eclipse.org/jetty/documentation/
2024-07-18 09:33:21.320:INFO:oejr.Runner:main: Runner
java.nio.file.NoSuchFileException: /datahub/datahub-gms/scripts/jetty-jmx.xml
at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:218)
at java.base/java.nio.file.Files.newByteChannel(Files.java:380)
at java.base/java.nio.file.Files.newByteChannel(Files.java:432)
at java.base/java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:422)
at java.base/java.nio.file.Files.newInputStream(Files.java:160)
at org.eclipse.jetty.util.resource.PathResource.getInputStream(PathResource.java:463)
at org.eclipse.jetty.xml.XmlConfiguration.<init>(XmlConfiguration.java:223)
at org.eclipse.jetty.xml.XmlConfiguration.<init>(XmlConfiguration.java:242)
at org.eclipse.jetty.runner.Runner.configure(Runner.java:330)
at org.eclipse.jetty.runner.Runner.main(Runner.java:563)
Usage: java [-Djetty.home=dir] -jar jetty-runner.jar [--help|--version] [ server opts] [[ context opts] context ...]
Server opts:
--version - display version and exit
--log file - request log filename (with optional 'yyyy_mm_dd' wildcard
--out file - info/warn/debug log filename (with optional 'yyyy_mm_dd' wildcard
--host name|ip - interface to listen on (default is all interfaces)
--port n - port to listen on (default 8080)
--stop-port n - port to listen for stop command (or -DSTOP.PORT=n)
--stop-key n - security string for stop command (required if --stop-port is present) (or -DSTOP.KEY=n)
[--jar file]*n - each tuple specifies an extra jar to be added to the classloader
[--lib dir]*n - each tuple specifies an extra directory of jars to be added to the classloader
[--classes dir]*n - each tuple specifies an extra directory of classes to be added to the classloader
--stats [unsecure|realm.properties] - enable stats gathering servlet context
[--config file]*n - each tuple specifies the name of a jetty xml config file to apply (in the order defined)
Context opts:
[[--path /path] context]*n - WAR file, web app dir or context xml file, optionally with a context path
2024/07/18 09:33:21 Command exited with error: exit status 1
All other pods were running correctly.
Bug: T363461
Closes T363461