More helpful logs when service "Create Failed"
- Dominant language
- No language data
- Stars
- 301
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
**Tell us about your request**
When creating a new service, create fails without any errors in deployment logs. The last visible logs are
```
02-14-2022 10:18:10 PM [Build] Successfully tagged application-image:latest
02-14-2022 10:18:10 PM [Build] Successfully built 2a53f3e899cb
```
Which suggests that build succeeded. Seems like there should always be an error logged in deployment log anytime a Service Create fails.
**Describe alternatives you've considered**
Tried looking through forums and past posts, all of them suggest checking logs, but event logs and/or deployment logs show no errors explaining why it failed.
**Additional context**
ARN: arn:aws:apprunner:us-west-2:520917683465:service/arpeggi-web-beta2/600285cea79a48fbb137786c78d31b52
Another ARN: arn:aws:apprunner:us-west-2:520917683465:service/arpeggi-web-beta/ea870ffb4d0a44979811a77ac1bf96f5
Current Service Quota: 10.
Existing Services: 3.
Repro steps (reproducible 5/5 tries):
- "Create Service"
- "Source code repository"
- Connect github repo + branch (we have another Service correctly set up and running from the exact same github branch)
- Deployment settings: Manual or Automatic (I've tried both)
- Configure settings to be exact same as existing Service
- Default settings (AWS managed key, etc)
- Wait for "Create service in progress..." to complete, always get "Create Failed"
- Event log is always:
```
02-14-2022 10:08:30 PM [AppRunner] Starting source code build.
02-14-2022 10:08:29 PM [AppRunner] Successfully pulled source code.
02-14-2022 10:07:41 PM [AppRunner] Service status is set to OPERATION_IN_PROGRESS.
02-14-2022 10:07:41 PM [AppRunner] Service creation started.
```
Deployment Log for "Create Service" contains no errors:
https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#logsV2:log-groups/log-group/$252Faws$252Fapprunner$252Farpeggi-web-beta2$252F600285cea79a48fbb137786c78d31b52$252Fservice/log-events/deployment$252F1ecf04a9c05c4bf1a7410d61a652aff6
Contributor guide
Research direction
Start with the Create Service flow and the event and deployment logs described in the reproduction steps. Reproduce the failure using the listed settings and compare the final visible build output with the Create Failed status. Done means a failed service creation includes an actionable error in the deployment or event log.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100