Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 3.6.5.Final
Affects Version/s: None
Component/s: Usability & User Experience, Visual Appearance
Labels:
None

Steps to Reproduce:

Hide

1) Start HAL in standalone mode, via

podman run -p 9090:9090 quay.io/halconsole/hal-development

2) Start the WF image via

podman run -p 9990:9990 quay.io/halconsole/wildfly

3) Observe the behaviour in the browser on http://localhost:9090 & http://localhost:9090?connect=http://localhost:9990

Show
1) Start HAL in standalone mode, via podman run -p 9090:9090 quay.io/halconsole/hal-development 2) Start the WF image via podman run -p 9990:9990 quay.io/halconsole/wildfly 3) Observe the behaviour in the browser on http://localhost:9090 & http://localhost:9090?connect=http://localhost:9990
Git Pull Request:
https://github.com/hal/console/pull/743

When running HAL in standalone mode via docker container (https://quay.io/repository/halconsole/hal-development), the user is not being able to add the management interface (no "Add" button present in the table), see [1]. This is caused due to the JS library import error, present in the developer console [2]. If the user overrides adding the management interface by appending *?connect=http://localhost:9990* to the URL, further JS error will appear, see [3], preventing any successful user interaction with the web console.

This is a regression against 3.6.4.Final version