-
Bug
-
Resolution: Done
-
Blocker
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
CLI is disconnected from DC if HC is reboot. I think that this needs to be fixed (so blocker priority), but I don't think that this blocks the precheck. So I created JBEAP jira.
Steps to reproduce:
- start first domain with host-primary.xml
- start second domain with host-secondary.xml
- connect to first domain (DC), update second domain and restart second domain with "--perform-installation"
- CLI is disconnected, although it is connected to first domain that is still running. But even if first domain would be updated, CLI should try to reconnect (same behaviour like on standalone server)
[domain@192.168.0.1:9990 /] shutdown --perform-installation --host=secondary The JBoss CLI session will be closed automatically to allow the server be updated. Once the server has been restarted, you can relaunch the JBoss CLI session. [station@fedora bin]$
- is cloned by
-
WFCORE-6384 CLI is disconnected from DC if HC is reboot
- Closed