search

Azure / Synapse-workspace-deployment

MIT License
27 stars 34 forks source link

Unhandled Promise Rejection Warning #89

Open rtevosk opened 1 year ago

rtevosk commented 1 year ago

Please note the use of Azure US Government cloud. Near the end of the deployment we see warnings and errors related to unhandled promise rejections.

Our configuration:

        TargetWorkspaceName: '<<REDACTED>>'
        TemplateFile: '<<REDACTED>>'
        ParametersFile: '<<REDACTED>>'
        OverrideArmParameters: '<<REDACTED>>'
        Environment: 'Azure US Government'
        resourceGroup: '<<REDACTED>>'
        clientId: <<REDACTED>>
        clientSecret: <<REDACTED>>
        subscriptionId: <<REDACTED>>
        tenantId: <<REDACTED>>
        DeleteArtifactsNotInTemplate: 'true'
        managedIdentity: 'false'
        operation: 'deploy'

Deployment Log:

Attempting to delete artifacts from workspace, that were not in the template.
Getting Artifacts from workspace: syn-synapse-***-prod.
Able to fetch service principal token: 200; status message: OK
Able to fetch service principal token: 200; status message: OK
Able to fetch service principal token: 200; status message: OK
(node:2676) UnhandledPromiseRejectionWarning: Error: connect ETIMEDOUT 52.126.195.80:443
    at TCPConnectWrap.afterConnect [as on***plete] (net.js:1144:16)
(node:2676) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2676) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
##[debug]Node Action run ***pleted with exit code 0
##[debug]Finishing: Run actions/Synapse-workspace-deployment@V1.7.0~~~

Upon investigation of the IP address referenced in the log above the following certificate issue is encountered in a web browser:

This server could not prove that it is 52.126.195.80; its security certificate is from graph.aadg.microsoftonline.us. This may be caused by a misconfiguration or an attacker intercepting your connection.