Help us improve the AWS re:Post Knowledge Center by sharing your feedback in a brief survey. Your input can influence how we create and update our content to better support your AWS journey.
Workflow Stuck on "Set up compute" in CodeCatalyst for Over 8 Hours
Hi,
I am currently experiencing an issue with my workflow in AWS CodeCatalyst. The workflow gets stuck during a build action and does not proceed further. The last log entry I see is "Set up compute", after which there are no further logs. The issue has persisted for over 8 hours now. Timeout is set to 5 minutes.
Here are the details from the dashboard: Start time: About 15 hours ago Duration: 8 hours 3 seconds
And here are the configurations for the action where the workflow gets stuck: Compute type: EC2 Compute: Linux.Arm64.Large Operating system: Amazon Linux 2 Provisioning model: On-demand Machine type: 4 GB memory, 2 vCPUs Timeout: 5 minutes
Could you please assist me in identifying the cause of this issue and suggest possible solutions? I am eager to resolve this as soon as possible to ensure the smooth operation of my workflows.
Thank you for your assistance.
Robert
- Topics
- DevOpsDeveloper Tools
- Language
- English
- Newest
- Most votes
- Most comments
The issue has been resolved. After waiting 8 hours for the build job to timeout and switching to a larger Compute type, as recommended by Didier, I encountered a "CLIENT_ERROR: Unable to pull customer's container image" error message. Once I directed it to the correct container image, it functioned as expected.
Hi, not sure but maybe related to insufficient size of EC2 instance. Did you try with xlarge instead of large ? Didier
Seems to be a combination of bugs.
- UI bug, showing In progress, but the workflow actually stopped after 8 hours.
- Timeout bug, Timeout configured to 5 minutes, but timeouts after 8 hours.
Not possible to configure Linux.Arm64.XLarge from the visual editor, not sure if this is due to restrictions or limitations in the UI but I'll figure it out.
@Robert Dahlborg What do you mean when you said you "directed it to the correct container image" ? Just change the image to the correct link? I also got the error: CLIENT_ERROR: Unable to pull customer's container image" error message but I don't know how to debug Here's the content I use for the field Image: {myAccountNumber}.dkr.ecr.eu-central-1.amazonaws.com/{myImage} I also setup the permission for ECR and Trust policy as mentioned in https://docs.aws.amazon.com/codecatalyst/latest/userguide/build-action-ref.html#build.configuration.container.image So I have no idea why it couldn't pull the image. If I use a public DockerHub or public Aws ECE it worked fine. Do you have any idea how to debug it since I can't see anything in the build log's except the error message above
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your response. I'm unable to proceed with testing because I'm stuck in this state. It's not possible to rerun the workflow until I manage to stop the currently running workflow. The timeout isn't working, and I can't figure out how to kill it.