Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-42033

[Backup Service] Allow access running task nerd data from the UI

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Cheshire-Cat
    • 7.0.0
    • tools

    Description

      Description:

      A one-off task which fails gets stuck in the Running Tasks list. This is fine as the task will get orphan collected later and moved into the task history when the orphan detection happens.

      However, the reason the backup failed is not visible to the user until is moved to the task history which may involve the user having to wait by up 30 minutes. 

      How to reproduce it:

      1. Make a one-off task fail e.g. by un-sharing the shared directory.

      What happens:

      The screenshot shows the user cannot see the reason why the task failed.

      The reason the backup failed is present in the http response.

      What is the improvement:

       

      The user can obtain information on why the backup failed. Perhaps one way to go about this is to allow the user to move a failed backup to the task history manually. An alternate approach is to allow the user to hover on the red text "failed" and see the error message.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            If the status is failed it should not be left in the running section that is a bug. I assume the reason why it fails is that we cannot move it to the history as the storage location is inaccessible, so we enter in the canandrum of what to do whit the task. I have opened MB-42048 for the backend changes needed to fix that and I'll leave this one for the UI improvement.

            carlos.gonzalez Carlos Gonzalez Betancort (Inactive) added a comment - - edited If the status is failed it should not be left in the running section that is a bug. I assume the reason why it fails is that we cannot move it to the history as the storage location is inaccessible, so we enter in the canandrum of what to do whit the task. I have opened MB-42048 for the backend changes needed to fix that and I'll leave this one for the UI improvement.

            running tasks should be exapndable now so the user should be able to see the same amount of info that in the REST API

            carlos.gonzalez Carlos Gonzalez Betancort (Inactive) added a comment - running tasks should be exapndable now so the user should be able to see the same amount of info that in the REST API

            Build couchbase-server-7.0.0-3406 contains cbbs commit 64cbbaf with commit message:
            MB-42033 Allow expanding the running task in the UI

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-3406 contains cbbs commit 64cbbaf with commit message: MB-42033 Allow expanding the running task in the UI

            People

              asad.zaidi Asad Zaidi (Inactive)
              asad.zaidi Asad Zaidi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty