-
Bug
-
Resolution: Done
-
Critical
-
fuse-7.12-GA
-
None
-
False
-
None
-
False
-
%
-
-
Todo
-
-
https://github.com/jboss-fuse/fuse-java-openshift/pull/27, https://github.com/jboss-fuse/fuse-java-openshift/pull/28, https://github.com/jboss-fuse/fuse-java-openshift/pull/29, https://github.com/jboss-fuse/fuse-java-openshift/pull/30, https://github.com/jboss-fuse/fuse-java-openshift/pull/31, https://github.com/jboss-fuse/fuse-java-openshift/pull/32, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/28, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/29, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/30, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/31, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/32, https://github.com/jboss-fuse/fuse-karaf-openshift/pull/33, https://github.com/jboss-fuse/fuse-eap-openshift/pull/43, https://github.com/jboss-fuse/fuse-eap-openshift/pull/44, https://github.com/jboss-fuse/fuse-eap-openshift/pull/45, https://github.com/jboss-fuse/fuse-eap-openshift/pull/46, https://github.com/jboss-fuse/fuse-eap-openshift/pull/47, https://github.com/jboss-fuse/fuse-eap-openshift/pull/48, https://github.com/jboss-fuse/karaf/pull/601, https://github.com/jboss-fuse/karaf/pull/602, https://github.com/jboss-fuse/docker-maven-plugin/pull/17, https://github.com/jboss-fuse/docker-maven-plugin/pull/18, https://github.com/jboss-fuse/arquillian-cube/pull/21, https://github.com/jboss-fuse/arquillian-cube/pull/22, https://github.com/jboss-fuse/camel/pull/2271, https://github.com/jboss-fuse/camel/pull/2272, https://github.com/jboss-fuse/hawtio/pull/592, https://github.com/jboss-fuse/hawtio/pull/593, https://github.com/jboss-fuse/redhat-fuse/pull/338, https://github.com/jboss-fuse/redhat-fuse/pull/339
-
-
-
Critical
-
Very Likely
After the Fuse Console deployment is installed by the operator, its certificate has to be renewed each year, as it cannot access the pods, as described in this KB article [1]
Initially, it was associated with a Openshift bug [2], it is also discused on this jira report [3], but the Openshift Engineering team denied it was something
on the platform itself, and closed the ticket
So, after reviewing this issue, we decided to have a look, from the Fuse Console side, as the certificate that is duplicated is generated by the Operator itself,
and this is not responsability of the Openshift team.
This note [4] should also be considered
[1] https://access.redhat.com/solutions/5751001
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1920974
[3] https://issues.redhat.com/browse/OCPBUGS-14666
[4] https://access.redhat.com/solutions/6961450
- account is impacted by
-
ENTMQBR-8609 Incorporate the fix of ENTESB-21742 to AMQ Broker Image
- Closed
- relates to
-
ENTESB-17779 Fuse console client auth fails when multiple cert authorities are present in jolokia caCert file
- Closed
- links to