- Newest
- Most votes
- Most comments
This is probably because of
Later on the same resource https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-projects-templates-sm.html, there is a proposal to use third party template.
Please check here: https://docs.aws.amazon.com/sagemaker/latest/dg/sagemaker-projects-walkthrough-3rdgit.html
I think this is not the core reason, since I tried the template highlighted in the red square and I got the same error...
I checked the log in CloudWatch and found this:
[GitRepositorySeedCodeBootStrapper.main()] ERROR GitRepositorySeedCodeBootStrapper - Seedcode checkin failed: https://codestar-connections.us-east-1.amazonaws.com/git-http/{my_aws_id}/us-east-1/b9d4f7f3-8626-48c5-96ea-6fc57f12a721/{my_github_id}/abalone-model-deploy.git: git-upload-pack not permitted on 'https://codestar-connections.us-east-1.amazonaws.com/git-http/{my_aws_id}/us-east-1/b9d4f7f3-8626-48c5-96ea-6fc57f12a721/{my_github_id}/abalone-model-deploy.git/'
But I don't know how to solve this.
I checked the log in CloudWatch and found this:
[GitRepositorySeedCodeBootStrapper.main()] ERROR GitRepositorySeedCodeBootStrapper - Seedcode checkin failed: https://codestar-connections.us-east-1.amazonaws.com/git-http/{my_aws_id}/us-east-1/b9d4f7f3-8626-48c5-96ea-6fc57f12a721/{my_github_id}/abalone-model-deploy.git: git-upload-pack not permitted on 'https://codestar-connections.us-east-1.amazonaws.com/git-http/{my_aws_id}/us-east-1/b9d4f7f3-8626-48c5-96ea-6fc57f12a721/{my_github_id}/abalone-model-deploy.git/'
But I don't know how to solve this.
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- asked 3 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
It looks like it's the AWS CodeBuild project the stack ran, to try and check seed code in to your repository, that failed. If the created CodeBuild project still exists, I'd suggest looking in the failed build logs for more details. If it's already been deleted (by the CloudFormation stack rolling back), you could check under the /aws/codebuild group in CloudWatch to try and dig out the relevant logs. Hopefully those CodeBuild logs could shed some more light on what specifically went wrong in the process?