Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1668

Reload/Restart master dialog is not dismissed if an error occurs

XMLWordPrintable

    • Hide
      • Use a wildfly-core patched with WFCORE-4830 and WFCORE-4764.For Example this PR: https://github.com/wildfly/wildfly-core/pull/4058
        Build WildFly with the patched wildfly-core version
        $WFLY_HOME/bin/add-user.sh -u admin -p admin
        Start the default domain: $WFLY_HOME/bin/domain.sh
        Open the Web Console, navigate to runtime -> hosts -> master
        Restart the master DC
        As soon as the DC is restarting and the Restarting dialog disappears, click on reload again.
        The Reload dialog is shown immediately. The DC is still restarting so the latest operation is rejected and an error is shown in HAL, which is fine. However, the Restarting Dialog is not dismissed and never disappears, making the console unusable.
      Show
      Use a wildfly-core patched with WFCORE-4830 and WFCORE-4764 .For Example this PR: https://github.com/wildfly/wildfly-core/pull/4058 Build WildFly with the patched wildfly-core version $WFLY_HOME/bin/add-user.sh -u admin -p admin Start the default domain: $WFLY_HOME/bin/domain.sh Open the Web Console, navigate to runtime -> hosts -> master Restart the master DC As soon as the DC is restarting and the Restarting dialog disappears, click on reload again. The Reload dialog is shown immediately. The DC is still restarting so the latest operation is rejected and an error is shown in HAL, which is fine. However, the Restarting Dialog is not dismissed and never disappears, making the console unusable.

      See reproduction steps.

      The Restart/reload dialog is always shown independently if the reload/restart operation is rejected by the DC, making the console unusable because the dialog never disappears.

      A logical way to handle this could be to show the dialog only if an error does not occur when the Restart/reload operation returns, or always dismiss the dialog as soon as an error is returned by the host.

      The workaround is to refresh the console accessing to it again.

      This behavior does not compromise the servers/host lifecycle.

            hpehl@redhat.com Harald Pehl
            yborgess1@redhat.com Yeray Borges Santana
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: