search

awslabs / service-workbench-on-aws

A platform that provides researchers with one-click access to collaborative workspace environments operating across teams, universities, and datasets while enabling university IT stakeholders to manage, monitor, and control spending, apply security best practices, and comply with corporate governance.
Apache License 2.0
178 stars 119 forks source link

[Bug] Unable to launch Windows Instance #986

Open mamatha-anand opened 2 years ago

mamatha-anand commented 2 years ago

Describe the bug Error provisioning environment- Demo-Windows. ResourceType : AWS::EC2::Instance, StatusReason : Received FAILURE signal with UniqueId.

To Reproduce Steps to reproduce the behavior:

  1. Go to Workspaces
  2. Create a Research Workspace and choose EC2 Windows-v1
  3. CloudFormation Stack gets launched
  4. See error

Expected behavior The workspace should get launched successfully

Screenshots N/A

Versions (please complete the following information):

Additional context My environment configuration:

awsRegion: us-east-1 awsProfile: swb solutionName: sw envType: test isAppStreamEnabled: false

Instance is getting created. But after a while it gets terminated. The CloudFormation stack shows error as below: "Received FAILURE signal with UniqueId"

ssvegaraju commented 2 years ago

Hi @mamatha-anand, thanks for bringing up this issue! We've added this to our backlog.

tdmalone commented 2 years ago

Taking a stab in the dark here, but this particular issue might depend on the AMI used. @mamatha-anand maybe if you can add details of your AMI here (and also try with a different AMI if possible?) it might help others debug the issue.

mamatha-anand commented 2 years ago

Hi Tim,

I did try recreating the AMI, still it didn’t work.

Using the same steps, I was able to create EMR and Linux AMI. Provisioned a Linux workspace and was able to connect.

Facing challenges only with Windows AMI.

Regards,

Mamatha A

From: Tim Malone @.> Sent: 27 July 2022 17:11 To: awslabs/service-workbench-on-aws @.> Cc: mamatha-anand @.>; Mention @.> Subject: [EXTERNAL] Re: [awslabs/service-workbench-on-aws] [Bug] Unable to launch Windows Instance (Issue #986)

Taking a stab in the dark here, but this particular issue might depend on the AMI used. @mamatha-anand https://github.com/mamatha-anand maybe if you can add details of your AMI here (and also try with a different AMI if possible?) it might help others debug the issue.

— Reply to this email directly, view it on GitHub https://github.com/awslabs/service-workbench-on-aws/issues/986#issuecomment-1196618035 , or unsubscribe https://github.com/notifications/unsubscribe-auth/APJKTKJ66JNLWO4ZN4E2ES3VWEN5TANCNFSM5VPALRBQ . You are receiving this because you were mentioned. https://github.com/notifications/beacon/APJKTKNLTNGBMV7WCZSYGMLVWEN5TA5CNFSM5VPALRB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOI5JPCMY.gif Message ID: @. @.> >

-- DISCLAIMER AND CONFIDENTIALITY NOTICE This is an e-mail from Relevance Lab Pvt Ltd, Inc. This e-mail is intended only for the confidential and personal use of the recipient(s) named above and may contain confidential and privileged information. If you are not an intended recipient, you have received this e-mail in error. Any review, storage, printing, dissemination, distribution or copying of this e-mail and / or any attachments is strictly prohibited. If you have received this e-mail in error, please notify the sender immediately by return e-mail and permanently delete the copy you received. We regret any inconvenience this may have caused. Thank you.