Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-3529

Failure to resolve FlowManager DNS is not reported as connection failure

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Morphic 1.0.1
    • Component/s: None
    • Labels:
      None

      Description

      When giving demos at Microsoft, Gregg ran into a problem where the CloudBased FlowManager's DNS could not be resolved, and this was reported in the UI as a generic "Oops" message, with the recommendation to restart the machine.
      In the logs, the failure was listed as:

      13:37:17.545:  UserLogonRequest fails with the error: {
         "code": "ENOTFOUND",
         "errno": "ENOTFOUND",
         "syscall": "getaddrinfo",
         "hostname": "flowmanager.prd.gpii.net",
         "host": "flowmanager.prd.gpii.net",
         "port": 443,
         "isError": true
      }
      

      This should be reported as the "NoConnection" error listed in the UserErrors spreadsheet at https://docs.google.com/spreadsheets/d/1ybyf9xoYoArjswWBhhBWECrrJdTPspI6FAuzjtcNmsM/edit#gid=0 rather than the generic "KeyInFail" message.
      We should also report any other connection-level failure, e.g. ECONNRESET, ETIMEDOUT, etc in this way.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cli@ocad.ca Cindy Qi Li
                Reporter:
                amb26 Antranig Basman
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: