`dataall-pipeline-main` CodePipeline timed out about aws-dataall HOT 5 CLOSED

the dataall-<env>-dbmigration-stage step in the pipeline trigger the codebuild project (dataall-datamesh-dbmigration) in the deployment account to run an alembic migration (in case you have changed the DB schema in backend/dataall/db/models)

the timeout can be related to a networking issue , Are you using the same account for tooling and deployment ? are you using an existing VPC ? and can you check the logs of the triggered codebuild project - dataall-datamesh-dbmigration - in the deployment account ?

from aws-dataall.

Same account for tooling and deployment. Fresh account, so whatever VPC is setup by the installer is what is used. We did not specify an existing VPC.

I noticed that the alembic pip install is not pinned to a specific version - and the version of alembic changed recently (1.8.x major release). Not sure if this would cause an issue. Should this pip install be pinned to 1.7.x?

we pasted some of the logs above from the code build project. Should we paste the full log? Or what else should we check?

can this step be skipped? We have a demo coming up later this week - and we don’t have a UI or anything to show.

@AmineIzanami please advise on how we can move forward with the demo.

thanks!

from aws-dataall.

If by fresh account, you mean a fresh AWS Account, you are probably facing a soft limit for the number of concurrent build projects that you can run at once, it is adjustable. You can visit "Service Quotas" Service in your AWS account and request to unlock that soft limit; I believe that should fix your issue.

from aws-dataall.

I opened a support ticket and asked for a quota increase for AWS CodeBuild Concurrently running builds. This solved the issue. Thanks @AmineIzanami !

from aws-dataall.

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

from aws-dataall.