Created attachment 1238716 [details]
an empty "Breakpoint suspended at" slideout is opened and cannot be closed
Description of problem:
In the openshift-jvm console on a Camel application, opening the Debug view makes the "Breakpoint suspended at" slideout open even if no breakpoint is suspended yet, and cannot be closed.
This slideout hovers above the camel route diagram, so it prevents selecting some camel route elements.
Version-Release number of selected component (if applicable):
Commit ID: 80441ef1187ce1807e5ce5ea994d869a2c272fcc
Steps to Reproduce:
1. Deploy a version of karaf2-camel-amq FIS quickstart,
oc create -f https://raw.githubusercontent.com/maschmid/karaf2-camel-amq/bz1393711/karaf2-camel-amq-template.json
oc process s2i-karaf2-camel-amq | oc create -f
and wait for the build and deployment
2. open the openshift console and find the s2i-karaf2-camel-amq-1-xxxx pod
3. open the "Java Console" on the pod
4. Open the camel context, 'Routes' folder
5. Switch to 'Debug'
6. Start debugging
An "Breakpoint suspended at" slideout is openend, covering part of the camel route diagram, this slideout cannot be closed.
(see attachment for screenshot)
Full camel route diagram should be visible, the "Breakpoint suspended at" slideout should only be opened when the actual breakpoint is suspended, and it should be able to close this slideout.
Looks the same in Firefox and Chrome
Fixed on hawtio/openshift-jvm v1.1.2
The slideout only shows up when we stop at a breakpoint and disappears when we continue execution.
Fix is merging into the console with
QE: since this bumps openshift-jvm to 1.1.2 this brings in a number of updated dependencies like angular, it would be good to get in a regression of the jvm console after this is in a 1.5 build
This has been merged into ocp and is in OCP v184.108.40.206 or newer.
verified with openshift v220.127.116.11+390ef18, attach the screen-shot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.