brentley/ecsdemo-frontend

THIS REPOSITORY IS DEPRECATED

Please go here for any updates and/or changes: https://github.com/aws-containers/ecsdemo-frontend

ecsdemo-frontend's Issues

Frontend Visual

Is this app the one shown in the videos? I was curious if i was missing something to enable the nifty dynamic graphic or if thats not open source

Error: mu-d1-pipeline-ecsdemo-frontend-deploy-acceptance

im getting an error when i try to build mu-d1-pipeline-ecsdemo-frontend-deploy-acceptance

its looking for a vpc that doesnt exist: vpc-b6e5e6cd

MessageError while executing command: mu -c mu.yml --assume-role arn:aws:iam::xxxxxxxxxxxx:role/mu-d1-pipeline-ecsdemo-frontend-mu-acpt-us-east-1 --disable-iam svc deploy acceptance. Reason: exit status 1

mu-d1-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) CREATE_IN_PROGRESS �[0m
�[31mAwaitFinalStatus ▶ ERROR �[0m mu-d1-service-ecsdemo-frontend-acceptance: ElbTargetGroup (AWS::ElasticLoadBalancingV2::TargetGroup) CREATE_FAILED The VPC ID 'vpc-b6e5e6cd' is not found (Service: AmazonElasticLoadBalancingV2; Status Code: 400; Error Code: ValidationError; Request ID: 9ebb2709-6470-11e8-ac90-2ddd3105d83c)
mu-d1-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) CREATE_IN_PROGRESS Resource creation Initiated�[0m
�[31mAwaitFinalStatus ▶ ERROR �[0m mu-d1-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) CREATE_FAILED Resource creation cancelled
mu-d1-service-ecsdemo-frontend-acceptance: mu-d1-service-ecsdemo-frontend-acceptance (AWS::CloudFormation::Stack) ROLLBACK_IN_PROGRESS The following resource(s) failed to create: [ServiceLogGroup, ElbTargetGroup]. . Rollback requested by user.�[0m
mu-d1-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) DELETE_IN_PROGRESS �[0m
�[31mfunc1 ▶ ERROR �[0m Ended in failed status ROLLBACK_COMPLETE
�[31mfunc1 ▶ ERROR �[0m

[Container] 2018/05/31 01:19:30 Command did not exit successfully mu -c mu.yml --assume-role arn:aws:iam::xxxxxxxxxxxx:role/mu-d1-pipeline-ecsdemo-frontend-mu-acpt-us-east-1 --disable-iam svc deploy acceptance exit status 1
[Container] 2018/05/31 01:19:30 Phase complete: BUILD Success: false
[Container] 2018/05/31 01:19:30 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: mu -c mu.yml --assume-role arn:aws:iam::xxxxxxxxxxxx:role/mu-d1-pipeline-ecsdemo-frontend-mu-acpt-us-east-1 --disable-iam svc deploy acceptance. Reason: exit status 1
[Container] 2018/05/31 01:19:30 Entering phase POST_BUILD

failed to create: [Pipeline, PipelineFailedEventRule, PipelineSucceededEventRule]

Facing an error as I tried to run this step (https://ecsworkshop.com/frontend/frontend/)

Current workaround/solution
Apparently, i use the https://github.com/ykbryan/ecsdemo-platform.git to clone the frontend repo and the way to fix it is to clone with SSH [email protected]:ykbryan/ecsdemo-platform.git or config the remote origin url to [email protected]:ykbryan/ecsdemo-platform.git

Command I ran in my cloud9 environment:

bryanchua:~/environment/ecsdemo-frontend (master) $ git remote set-url origin [email protected]:ykbryan/ecsdemo-platform.git

No more error, but I think there might be others who face the same issue - use HTTPS to clone instead.

Error displayed as IAM Policy Issue for the deploy to Acceptance stage of CodePipeline in frontend service

This is an FYI for those having the same issue as discussed in mu issue 416

I have been using the current GitHub repos and Mu 1.5.10

During the frontend deployment, when deploying the container to the acceptance environment, there is a consistent error which is demonstrated through an issue with the ECS EC2 and deploying the task.

There are suggestions that this could be a mu issue related to the deploy-cluster policy please see:
stelligent/mu#416

However there is an issue with the "new ARN and resource ID format" Opt in; please see: stelligent/mu#414

I have changed my setting to have opted out to the new ARN and resource id's and re run the platform and frontend deployments. This appears to be an answer for now, until the fix for 416 is promoted to a mu release.

Build failed: mu -c mu.yml

https://ecsworkshop.com/frontend/frontend.html

• BUILD | Failed | 55 secs
  Start time: 5 minutes ago
  End time: 4 minutes ago
  Message: Error while executing command: mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam svc deploy acceptance. Reason: exit status 1

• Logs:

[Container] 2018/02/27 18:27:29 Waiting for agent ping
[Container] 2018/02/27 18:27:29 Waiting for DOWNLOAD_SOURCE
[Container] 2018/02/27 18:27:32 Phase is DOWNLOAD_SOURCE
[Container] 2018/02/27 18:27:32 CODEBUILD_SRC_DIR=/codebuild/output/src833261745/src
[Container] 2018/02/27 18:27:32 YAML location is /codebuild/readonly/buildspec.yml
[Container] 2018/02/27 18:27:32 Processing environment variables
[Container] 2018/02/27 18:27:32 Moving to directory /codebuild/output/src833261745/src
[Container] 2018/02/27 18:27:32 Registering with agent
[Container] 2018/02/27 18:27:32 Phases found in YAML: 1
[Container] 2018/02/27 18:27:32 BUILD: 8 commands
[Container] 2018/02/27 18:27:32 Phase complete: DOWNLOAD_SOURCE Success: true
[Container] 2018/02/27 18:27:32 Phase context status code: Message: 
[Container] 2018/02/27 18:27:32 Entering phase INSTALL
[Container] 2018/02/27 18:27:32 Phase complete: INSTALL Success: true
[Container] 2018/02/27 18:27:32 Phase context status code: Message: 
[Container] 2018/02/27 18:27:32 Entering phase PRE_BUILD
[Container] 2018/02/27 18:27:32 Phase complete: PRE_BUILD Success: true
[Container] 2018/02/27 18:27:32 Phase context status code: Message: 
[Container] 2018/02/27 18:27:32 Entering phase BUILD
[Container] 2018/02/27 18:27:32 Running command curl -sL https://github.com/stelligent/mu/releases/download/v1.4.2/mu-linux-amd64 -o /usr/bin/mu

[Container] 2018/02/27 18:27:34 Running command chmod +rx /usr/bin/mu

[Container] 2018/02/27 18:27:34 Running command mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam env up acceptance
�[33mUnable to find environment named '[acceptance]' in configuration�[0m

[Container] 2018/02/27 18:27:35 Running command mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam db up acceptance
Skipping upsert of common IAM roles.�[0m
�[32mSkipping database since database.name is unset�[0m

[Container] 2018/02/27 18:27:35 Running command mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam svc deploy acceptance
Skipping upsert of common IAM roles.�[0m
Skipping upsert of service IAM roles.�[0m
�[32mUpsert repo for service 'ecsdemo-frontend'�[0m
No changes for stack 'mu-repo-ecsdemo-frontend'�[0m
�[32mDeploying service 'ecsdemo-frontend' to 'acceptance' from '529225399032.dkr.ecr.us-east-2.amazonaws.com/mu-ecsdemo-frontend:34b2981'�[0m
�[33m Stack 'mu-service-ecsdemo-frontend-acceptance' was in 'ROLLBACK_COMPLETE' status, deleting...�[0m
mu-service-ecsdemo-frontend-acceptance: mu-service-ecsdemo-frontend-acceptance (AWS::CloudFormation::Stack) DELETE_IN_PROGRESS User Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: mu-service-ecsdemo-frontend-acceptance (AWS::CloudFormation::Stack) CREATE_IN_PROGRESS User Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: ElbTargetGroup (AWS::ElasticLoadBalancingV2::TargetGroup) CREATE_IN_PROGRESS �[0m
mu-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) CREATE_IN_PROGRESS �[0m
mu-service-ecsdemo-frontend-acceptance: ElbTargetGroup (AWS::ElasticLoadBalancingV2::TargetGroup) CREATE_IN_PROGRESS Resource creation Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: ServiceLogGroup (AWS::Logs::LogGroup) CREATE_IN_PROGRESS Resource creation Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: ElbHttpPathListenerRule (AWS::ElasticLoadBalancingV2::ListenerRule) CREATE_IN_PROGRESS �[0m
mu-service-ecsdemo-frontend-acceptance: ElbHttpPathListenerRule (AWS::ElasticLoadBalancingV2::ListenerRule) CREATE_IN_PROGRESS Resource creation Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: MicroserviceTaskDefinition (AWS::ECS::TaskDefinition) CREATE_IN_PROGRESS �[0m
mu-service-ecsdemo-frontend-acceptance: MicroserviceTaskDefinition (AWS::ECS::TaskDefinition) CREATE_IN_PROGRESS Resource creation Initiated�[0m
mu-service-ecsdemo-frontend-acceptance: EcsService (AWS::ECS::Service) CREATE_IN_PROGRESS �[0m
�[31mAwaitFinalStatus ERROR �[0m mu-service-ecsdemo-frontend-acceptance: EcsService (AWS::ECS::Service) CREATE_FAILED FARGATE is not supported in this region.
mu-service-ecsdemo-frontend-acceptance: mu-service-ecsdemo-frontend-acceptance (AWS::CloudFormation::Stack) ROLLBACK_IN_PROGRESS The following resource(s) failed to create: [EcsService]. . Rollback requested by user.�[0m
�[31mfunc1 ERROR �[0m Ended in failed status ROLLBACK_COMPLETE 
�[31mfunc1 ERROR �[0m 

[Container] 2018/02/27 18:28:27 Command did not exit successfully mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam svc deploy acceptance exit status 1
[Container] 2018/02/27 18:28:27 Phase complete: BUILD Success: false
[Container] 2018/02/27 18:28:27 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: mu -c mu.yml --assume-role arn:aws:iam::529225399032:role/mu-pipeline-ecsdemo-frontend-mu-acpt-us-east-2 --disable-iam svc deploy acceptance. Reason: exit status 1
[Container] 2018/02/27 18:28:27 Entering phase POST_BUILD
[Container] 2018/02/27 18:28:27 Phase complete: POST_BUILD Success: true
[Container] 2018/02/27 18:28:27 Phase context status code: Message: 
[Container] 2018/02/27 18:28:27 Preparing to copy artifacts
[Container] 2018/02/27 18:28:27 Expanding base directory path: .
[Container] 2018/02/27 18:28:27 Assembling file list
[Container] 2018/02/27 18:28:27 Expanding .
[Container] 2018/02/27 18:28:27 Expanding artifact file paths for base directory .
[Container] 2018/02/27 18:28:27 Assembling file list
[Container] 2018/02/27 18:28:27 Expanding **/*
[Container] 2018/02/27 18:28:27 Found 117 file(s)
[Container] 2018/02/27 18:28:27 Phase complete: UPLOAD_ARTIFACTS Success: true
[Container] 2018/02/27 18:28:27 Phase context status code: Message: ```

Unable to start container sqlite3 gem

Replicated this issue on both Fargate and local machine when starting a container:

+ RAILS_ENV=production
+ rake assets:precompile
rake aborted!
LoadError: libsqlite3.so.0: cannot open shared object file: No such file or directory - /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3/sqlite3_native.so
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `require'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `rescue in <top (required)>'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:2:in `<top (required)>'
/usr/src/app/config/application.rb:7:in `<top (required)>'
/usr/src/app/Rakefile:4:in `<top (required)>'
/usr/local/bundle/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'

Caused by:
LoadError: cannot load such file -- sqlite3/2.5/sqlite3_native
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:4:in `require'
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:4:in `<top (required)>'
/usr/src/app/config/application.rb:7:in `<top (required)>'
/usr/src/app/Rakefile:4:in `<top (required)>'
/usr/local/bundle/gems/rake-12.3.1/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
+ exec rails s -e production -b 0.0.0.0
/usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `require': libsqlite3.so.0: cannot open shared object file: No such file or directory - /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3/sqlite3_native.so (LoadError)
	from /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:6:in `rescue in <top (required)>'
	from /usr/local/bundle/gems/sqlite3-1.3.13/lib/sqlite3.rb:2:in `<top (required)>'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:81:in `require'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:81:in `block (2 levels) in require'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:76:in `each'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:76:in `block in require'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:65:in `each'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler/runtime.rb:65:in `require'
	from /usr/local/lib/ruby/site_ruby/2.5.0/bundler.rb:114:in `require'
	from /usr/src/app/config/application.rb:7:in `<top (required)>'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:78:in `require'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:78:in `block in server'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:75:in `tap'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:75:in `server'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
	from /usr/local/bundle/gems/railties-4.2.10/lib/rails/commands.rb:17:in `<top (required)>'
	from /usr/src/app/bin/rails:9:in `require'
	from /usr/src/app/bin/rails:9:in `<top (required)>'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
	from /usr/local/bundle/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
	from /usr/local/bundle/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
	from /usr/local/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:65:in `require'
	from /usr/local/lib/ruby/site_ruby/2.5.0/rubygems/core_ext/kernel_require.rb:65:in `require'
	from /usr/src/app/bin/spring:13:in `<top (required)>'
	from bin/rails:3:in `load'
	from bin/rails:3:in `<main>'

I was able to temporarily solve the issue by using the base ruby2.5 image (without the -slim) and it works fine with:

FROM ruby:2.5

Not 100% sure on the best way forward yet, as I'm a fan of keeping images small, so would like to keep using slim, just raising this for visibility and in-case it helps someone.