search

aws / aws-toolkit-visual-studio

AWS Toolkit for Visual Studio - a plugin to interact with AWS
https://aws.amazon.com/visualstudio/
Apache License 2.0
107 stars 29 forks source link

AWS Elastic Beanstalk Environment > View Status doesnt work. #114

Closed nineismine closed 2 years ago

nineismine commented 4 years ago

When using Elastic BeanStalk following the steps in Julie Lerman's Pluralsight course, (creating a basic API and moving the web project to the cloud) errors are displayed when trying to view information about my Environment.

After following the steps in Julie's course under Chapter 4 section 5 "Publishing ASP.NET Core Applications to AWS Elastic Beanstalk" Everything finished up and the instance is running fine on my free tier account. But an error was generated after setup (sorry I didn't get a screenshot of the original one. )

After testing that my web app is running in the cloud, I went into the AWS Explorer in Visual Studio, and under Elastic Beanstalk I have:

AWS Elastic Beanstalk: -----------------NETCoreAPI ---------------------------NETCoreAPI-dev

Everything seems to be fine until I attempt to drill down into "NETCoreAPI-dev" which is where I believe I would find my Environment information in Visual Studio. When I double click on this item in the tree I have been met with two errors which are in the attached screenshots.

To Reproduce

Steps to reproduce the behavior example:

  1. Go to 'Publish to AWS Elastic BeanStalk'
  2. Fill out the information
  3. Let it finish publishing
  4. Go to 'AWS Elastic Beanstalk' (btw I love the imagery that pops up when I think about an elastic beanstalk! )
  5. Go to your Deployed app (note that everything seems to be functional here.. when I 'View Status' I get a window with ONLY "Events" and "Versions" and some information about the app
  6. Go to the node below this and double click or view status and then get one of the two attached errors. Note that I have only received the DataVisualization error one time and that was directly after restarting Visual studio and attempting to double click on the bottom most node to see my environment data. After the first time it now gives the other error "Set connectionId" consistently.

Expected behavior

The environment information should properly load.

Screenshots

image image

Computer (please complete the following information):

Here is a section of errors from my logs:

2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5.12xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5.24xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5.metal in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5d.12xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5d.24xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type c5d.metal in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type g2.8xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type g4dn.12xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type g4dn.2xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type g4dn.4xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type g4dn.xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type i2.2xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type i2.4xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type i2.8xlarge in available service metadata 2020-08-11 07:23:18,464 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type i2.xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type i3en.metal in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5.16xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5.8xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5.metal in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5a.16xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5a.8xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5d.16xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type m5d.8xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5.16xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5.8xlarge in available service metadata 2020-08-11 07:23:18,465 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5.metal in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5a.8xlarge in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5d.16xlarge in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5d.8xlarge in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type r5d.metal in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t2.nano in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.2xlarge in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.large in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.medium in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.micro in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.nano in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.small in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type t3.xlarge in available service metadata 2020-08-11 07:23:18,466 [1] ERROR Amazon.AWSToolkit.ElasticBeanstalk.WizardPages.PageUI.Deployment.AWSOptionsPage - Unable to find instance type z1d.metal in available service metadata

from today 2020-08-12 04:32:32,836 [1] ERROR Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities - Error configuring Lambda Tester on project. FileName: , FullName: , UniqueName: System.Exception: Unable to determine project FileName at Amazon.AWSToolkit.VisualStudio.Lambda.LambdaTesterUtilities.EnsureLambdaTesterConfigured(Project project, IAWSLambda lambdaPlugin)

awschristou commented 4 years ago

Thank you for reaching out @nineismine - this error is not related to your Elastic Beanstalk environment/application. There appears to be a dll issue between the toolkit and another Visual Studio extension (for example ReSharper). I haven't investigated this issue, so I'm unsure if temporarily disabling the other extension would allow the panel to display correctly as a workaround.

awschristou commented 2 years ago

A fix for this issue has been released in the 1.24.0.0 version of the Toolkit. It should now be possible to view the environment panel.