Airavata
  1. Airavata
  2. AIRAVATA-721

Xbaya attempt connection at a down Airavata Server

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: 0.6
    • Fix Version/s: 0.8
    • Component/s: XBaya
    • Labels:
      None
    • Environment:

      Description

      I was working on my workflow on Airavata, I had some problems after submitting at Ranger.
      I had to restart the Xbaya and Airavata-server in order to continue.

      I only restart the Xbaya and forgot to start the Airavata Server.
      On Xbaya I went to Xbaya => import => Workflow from Registry. I just left the standard Airavata Registry setting and hit the ok button.

      No error message appeared on my Xbaya screen. I didn't know what to do. I repeated the process above to import my workflow from Registry.

      I just noticed that at every attempt a new Application Service was added on the left menu Component List.
      That's when I realized my Airavata-server was down.

        Activity

        Pedro da Silveira created issue -
        Saminda Wijeratne made changes -
        Field Original Value New Value
        Fix Version/s 0.7 [ 12323148 ]
        Fix Version/s 0.6 [ 12322484 ]
        Hide
        Saminda Wijeratne added a comment -

        Hi Pedro,
        We will be differing this issue for 0.7. We have fixed the issue on repeated addition of "Application Service" in the Component list (we saw the issue and fixed it on the same day you've put the issue rev. 1432270). We did not however test is with your scenario (when the server is down). We will test and update this jira with that scenario as well.

        Show
        Saminda Wijeratne added a comment - Hi Pedro, We will be differing this issue for 0.7. We have fixed the issue on repeated addition of "Application Service" in the Component list (we saw the issue and fixed it on the same day you've put the issue rev. 1432270). We did not however test is with your scenario (when the server is down). We will test and update this jira with that scenario as well.
        Hide
        Chathuri Wimalasena added a comment -

        Hi Pedro,

        I checked with the latest trunk ( r 1437457 ) and now the "Application Service" in the Component list is not repeated when the server is down.

        Regards,
        Chathuri

        Show
        Chathuri Wimalasena added a comment - Hi Pedro, I checked with the latest trunk ( r 1437457 ) and now the "Application Service" in the Component list is not repeated when the server is down. Regards, Chathuri
        Hide
        Pedro da Silveira added a comment -

        Hi Saminda,

        No problem. I think this is a minor issue.
        It just confuses the user because he/she does not know what to do, since there aren't any error message message on screen.

        Show
        Pedro da Silveira added a comment - Hi Saminda, No problem. I think this is a minor issue. It just confuses the user because he/she does not know what to do, since there aren't any error message message on screen.
        Hide
        Pedro da Silveira added a comment -

        Hi Chathuri,

        You are right. At least on the revision 1437790 the Component list is not repeated. Although, it still lacks an warn message on screen to alert the user the Airavata-Server is down or not responding.

        Show
        Pedro da Silveira added a comment - Hi Chathuri, You are right. At least on the revision 1437790 the Component list is not repeated. Although, it still lacks an warn message on screen to alert the user the Airavata-Server is down or not responding.
        Hide
        Saminda Wijeratne added a comment -

        you have a very good point pedro... It seems we are ignoring a critical error message when the server is not present... We are already working coming up with a API level solution to fix this for XBaya & API clients... Please feel free to append any other usablity issues relating to this which you find in XBaya.

        Show
        Saminda Wijeratne added a comment - you have a very good point pedro... It seems we are ignoring a critical error message when the server is not present... We are already working coming up with a API level solution to fix this for XBaya & API clients... Please feel free to append any other usablity issues relating to this which you find in XBaya.
        Lahiru Gunathilake made changes -
        Fix Version/s 0.8 [ 12323883 ]
        Fix Version/s 0.7 [ 12323148 ]
        Hide
        Suresh Marru added a comment -

        This error seems to be before XBaya was migrated to use REST API of registry. If this issue still persists in latest (0.8) release testing, we need to re-open this and work on it for 0.9

        Show
        Suresh Marru added a comment - This error seems to be before XBaya was migrated to use REST API of registry. If this issue still persists in latest (0.8) release testing, we need to re-open this and work on it for 0.9
        Suresh Marru made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Suresh Marru [ smarru ]
        Resolution Won't Fix [ 2 ]

          People

          • Assignee:
            Suresh Marru
            Reporter:
            Pedro da Silveira
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development