Error: Unable to access jarfile /perf_test/perf-test.jar

[albionb96]

So I don't know if I should open a bug report for this, but I thought I will start a discussion first.

I tried to start the latest client of the perf tool inside a pod in Kubernetes like below:

---
apiVersion: batch/v1
kind: Job
metadata:
  labels:
    app: perf-test
  name: perf-test
  namespace: message-broker
spec:
  backoffLimit: 6
  completionMode: NonIndexed
  completions: 1
  parallelism: 1
  suspend: false
  template:
    metadata:
      labels:
        batch.kubernetes.io/job-name: perf-test
        job-name: perf-test
    spec:
      containers:
      - name: rabbitmq-perf-test
        args:
        - --uri
        - amqp://user:pass@message-broker:5672
        - --quorum-queue
        - --rate
        - '1000'
        - --size
        - '1024'
        - --queue
        - queue-0
        - --producers
        - '1'
        - --consumers
        - '1'
        - --autoack
        - --metrics-prometheus
        - --queue-args
        - 'max-length-bytes=2000000000'
        image: pivotalrabbitmq/perf-test:2.19.0
        imagePullPolicy: Always
        resources: {}
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
      dnsPolicy: ClusterFirst
      restartPolicy: Never
      schedulerName: default-scheduler
      securityContext: {}
      terminationGracePeriodSeconds: 30
  ttlSecondsAfterFinished: 300

And I got the following error:

Error: Unable to access jarfile /perf_test/perf-test.jar

[mkuratczyk]

I've deployed your YAML without any changes and it works for me - obviously it can't connect anywhere, but perf-test itself starts just fine:

> kubectl logs perf-test-g2d9j
Main thread caught exception: java.net.UnknownHostException: message-broker: Name or service not known
10:57:29.708 [main] ERROR com.rabbitmq.perf.PerfTest - Main thread caught exception
java.net.UnknownHostException: message-broker: Name or service not known
        at java.base/java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
        at java.base/java.net.InetAddress$PlatformNameService.lookupAllHostAddr(InetAddress.java:933)
        at java.base/java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1529)
        at java.base/java.net.InetAddress$NameServiceAddresses.get(InetAddress.java:852)
        at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1519)
        at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1377)
        at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1305)
        at com.rabbitmq.client.DnsRecordIpAddressResolver.resolveIpAddresses(DnsRecordIpAddressResolver.java:83)
        at com.rabbitmq.client.DnsRecordIpAddressResolver.getAddresses(DnsRecordIpAddressResolver.java:73)
        at com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:58)
        at com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:160)
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:1216)
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:1173)
        at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:1071)
        at com.rabbitmq.perf.MulticastSet$ConnectionCreator.createConfigurationConnections(MulticastSet.java:889)
        at com.rabbitmq.perf.MulticastSet.createConfigurationConnections(MulticastSet.java:354)
        at com.rabbitmq.perf.MulticastSet.run(MulticastSet.java:205)
        at com.rabbitmq.perf.PerfTest.main(PerfTest.java:480)
        at com.rabbitmq.perf.PerfTest.main(PerfTest.java:604)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
        at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
        at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:65)
test stopped
id: test-105729-397, sending rate avg: 0 msg/s
id: test-105729-397, receiving rate avg: 0 msg/s
id: test-105729-397, consumer latency min/median/75th/95th/99th 0/0/0/0/0 µs

[albionb96]

As I assumed Openshift overrides the UID with a random UID.

and I think the problem is similar to these two Stackoverflow issues:
https://stackoverflow.com/questions/70109707/openshift-missing-permissions-to-create-a-file?noredirect=1#comment123962432_70109707
https://stackoverflow.com/questions/52476413/jhipster-on-openshift-unable-to-access-jarfile

I was able to solve the issue for now following these guides:
https://examples.openshift.pub/deploy/scc-anyuid/
https://cookbook.openshift.org/users-and-role-based-access-control/how-can-i-enable-an-image-to-run-as-a-set-user-id.html

[michaelklishin]

@acogoluegnes @albionb96 is there something specific that we should document? We already do that for OpenShift-specific aspects in our Kubernetes-related doc guides.

[acogoluegnes]

@albionb96 Do you think there's something we can do in the Dockerfile to avoid this problem with OpenShift?

[albionb96]

@acogoluegnes Openshift states that the user which is going to be used in the Dockerfile should be part of the root group, and also the files and folders which will be accessed should be owned from the the root group:

https://docs.openshift.com/container-platform/4.13/openshift_images/create-images.html#use-uid_create-images

Here are also some more examples:
https://developers.redhat.com/blog/2020/10/26/adapting-docker-and-kubernetes-containers-to-run-on-red-hat-openshift-container-platform

I would add the perf_tool user to the root group and give it a try

[acogoluegnes]

I don't have an OpenShift environment to test on. You can modify the Dockerfile of the PerfTest project, build the image, and test the changes:

docker build --build-arg https://github.com/rabbitmq/rabbitmq-perf-test/releases/download/v2.19.0/perf-test-2.19.0.jar .