Build failed: mu -c mu.yml

[tiago-cruz-movile]

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: ```

[jimsmith]

@tiago-cruz-movile fargate isn't available in the region you are using, it's only in N Virginia.

[jimsmith]

this should be closed and docs updated to check region supporting AWS Fargate if it isn't documented :)