OpenShift Java Console fails to open with v3.5.34 or higher

Description

OpenShift Java Console fails to open when you mvn fabric8:deploy the following quickstart (master branch), which uses version 3.5.34 of fabric8-maven-plugin: https://github.com/fabric8-quickstarts/spring-boot-camel-xml However, when you downgrade the plugin to 3.5.33 the console works fine.

Is it a regression, possibly related to https://issues.jboss.org/browse/OSFUSE-700 ?

Info

• f-m-p version : >= 3.5.34
• Maven version (mvn -v) :

Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-25T04:49:05+09:00)

• Kubernetes / OpenShift setup and version :

$ oc version
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth

Server https://localhost:8443
openshift v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657

• If it’s a bug, how to reproduce : See above

[rhuss]

I can confirm the issue. The reason seems that in the base image used in 3.5.34 in jolokia.properties --> protocol=https is missing:

3.5.34 properties

host=*
port=8778
discoveryEnabled=false
user=jolokia
password=x6fXoCMrgiJwa1Ix4XcBpQnTvQKm2f
useSslClientAuthentication=true
extraClientCheck=true
caCert=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt
clientPrincipal=cn=system:master-proxy

3.5.33 properties

host=*
port=8778
discoveryEnabled=false
user=jolokia
password=whqN3jJyNCXtWaGIJzDxfndUqqrqoU
useSslClientAuthentication=true
extraClientCheck=true
protocol=https
caCert=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt
clientPrincipal=cn=system:master-proxy

going to find out now, what changed in the base images …

[rohanKanojia]

Closed via #1336