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

Two error dialog messages when DC is starting and user executes lifecycle operations on slave servers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor Minor
    • 3.2.6.Final
    • None
    • None
    • None
    • Hide
      • Use a wildfly-core patched with WFCORE-4830 and WFCORE-4764. One available can be found here: https://github.com/yersan/wildfly-core/tree/WFCORE-4830-WFCORE-4764
      • 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
      • Reload the master restarting its servers
      • As soon as the DC is reloading and the reloading dialog disappears, open the server-three view button contextual menu and click on 'start' meanwhile the DC is starting.
      • The DC rejects the operation displaying an expected error with the message "WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available", however, an additional error without any message is also displayed. This second growl is unexpected.
      Show
      Use a wildfly-core patched with WFCORE-4830 and WFCORE-4764 . One available can be found here: https://github.com/yersan/wildfly-core/tree/WFCORE-4830-WFCORE-4764 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 Reload the master restarting its servers As soon as the DC is reloading and the reloading dialog disappears, open the server-three view button contextual menu and click on 'start' meanwhile the DC is starting. The DC rejects the operation displaying an expected error with the message "WFLYCTL0379: System boot is in process; execution of remote management operations is not currently available", however, an additional error without any message is also displayed. This second growl is unexpected.

      When the DC is starting, any lifecycle operation on a server that belongs to a slave shows two error dialogs, one with a description and the other without any explanation.

      This is more a user experience issue. Only one message dialog should be displayed under this scenario.

      In order to correctly test this scenario, ensure that these two issues are merged: WFCORE-4830 and WFCORE-4764

        1. Screenshot 2020-02-10 at 10.52.24.png
          Screenshot 2020-02-10 at 10.52.24.png
          447 kB

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

              Created:
              Updated:
              Resolved: