-
Bug
-
Resolution: Done
-
Blocker
-
7.4.0.Beta
-
None
-
False
-
False
-
-
-
-
-
-
Undefined
-
For openjdk 11 image these steps leads to error
podman run -it registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-tech-preview-eap74-openjdk11-openshift-rhel8:7.4.0.Beta-3 podman exec -it $(podman ps -q) /opt/eap/bin/livenessProbe.sh true probe.eap.jolokia.EapProbe Traceback (most recent call last): File "/opt/eap/bin/probes/runner.py", line 87, in <module> runner.addProbe(probeClass()) File "/opt/eap/bin/probes/probe/eap/jolokia.py", line 37, in __init__ HealthCheckTest() File "/opt/eap/bin/probes/probe/jolokia.py", line 39, in __init__ self.__readConfig() File "/opt/eap/bin/probes/probe/jolokia.py", line 62, in __readConfig with open("/opt/jolokia/etc/jolokia.properties") as jolokiaProperties: FileNotFoundError: [Errno 2] No such file or directory: '/opt/jolokia/etc/jolokia.properties'
For openjdk 8 image it is fine.
podman run -it registry-proxy.engineering.redhat.com/rh-osbs/jboss-eap-7-tech-preview-eap74-openjdk8-openshift-rhel7:7.4.0.Beta-2 podman exec -it $(podman ps -q) /opt/eap/bin/livenessProbe.sh true probe.eap.jolokia.EapProbe { "probe.eap.jolokia.EapProbe": { "probe.eap.jolokia.ServerRunningModeTest": "NORMAL", "probe.eap.jolokia.DeploymentTest": "No deployments", "probe.eap.jolokia.BootErrorsTest": "No boot errors", "probe.eap.jolokia.ServerStatusTest": "running", "probe.eap.jolokia.HealthCheckTest": "Health Check not configured" } }
Setting as blocker because it is regression compared to previous image and jdk8 image. Note, that is not just that scenario not working, also jolokia URL not working at all.
https://api.eapqe-015-rk7f.eapqe.psi.redhat.com:6443/api/v1/namespaces/74-openjdk11-kikk/pods/https:tx-client-0:8778/proxy/jolokia/exec/jboss.as:core-service=module-loading/listResourceLoaderPaths(java.lang.String)/org.jboss.jts retrieved response { "kind": "Status", "apiVersion": "v1", "metadata": {}, "status": "Failure", "message": "error trying to reach service: dial tcp 10.128.4.241:8778: connect: connection refused", "code": 500 }
With proper look into log I see again /opt/jolokia/jolokia-opts: No such file or directory
+ /opt/eap/bin/standalone.sh -c standalone-openshift.xml -bmanagement 0.0.0.0 -Djboss.server.data.dir=/opt/eap/standalone/data -Dwildfly.statistics-enabled=true -b 10.128.3.218 -bprivate 10.128.3.218 -Djboss.node.name=tx-server-0 -Djboss.messaging.host=10.128.3.218 -Djboss.messaging.cluster.password=aaaaaa --start-mode=admin-only -Dorg.wildfly.internal.cli.boot.hook.script=/tmp/cli-script-1613730481.cli -Dorg.wildfly.internal.cli.boot.hook.marker.dir=/tmp/cli-boot-reload-marker-1613730483 -Dorg.wildfly.internal.cli.boot.hook.script.properties=/tmp/cli-script-property-1613730481.cli -Dorg.wildfly.internal.cli.boot.hook.script.output.file=/tmp/cli-script-output-1613730481.cli -Dorg.wildfly.internal.cli.boot.hook.script.error.file=/tmp/cli-script-error-1613730481.cli -Dorg.wildfly.internal.cli.boot.hook.script.warn.file=/tmp/cli-warning-1613730481.log
/opt/eap/bin/standalone.conf: line 93: /opt/jolokia/jolokia-opts: No such file or directory
- blocks
-
CLOUD-3918 EAP 7.4.0.Beta OpenShift Image Release
- Closed