bug: [PRO] Creating Aurora RDS cluster using Pulumi doesn't use mysql:latest image #10928
Closed
1 task done
Assignees
Labels
area: integration/pulumi
Issues related to Pulumi
aws:rds
Amazon Relational Database Service
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Comments
hugo-abhishek
added
status: triage needed
|
Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide. |
Anze1508
added
aws:rds
|
Hi @hugo-abhishek, For parity with Aurora, we are mapping the version of the mysql engine based on the aurora version configured. As you can see on RDS documentation, Furthermore, since the returned engine is I am curious as if there is a reason for wanting to map |
|
Hi @cloutierMat, as mentioned above this version of oracle has issue for chown on broken symlink, this causes subsequent restarts to fail.
The issue was fixed in this PR and it doesn't seem like the image localstack is using has a fix for this. This is the sha for 8.0.28-oracle Upon inspecting the above image, I can confirm above version doesn't contain the fix, and hence the ask for using the latest image (I believe we are fine with any version having this fix) |
|
Thank you @hugo-abhishek for the added context. We will be looking into a fix for this and hopefully be able to pin a version with the appropriate fix while keeping mysql version on par with RDS version compatibility. In the meantime, I can offer this workaround. You can manually pull the desired image and tag it |
|
Thanks @cloutierMat for the alternate solution. |
|
Hi @hugo-abhishek, This issue has now been fixed and will be available in the next latest image. We are no longer using the I will mark this issue as closed but do not hesitate to contact us again if there are any further issues. |
|
Thanks @cloutierMat |
|
@cloutierMat There is still an issue we are facing. Now it is using the correct image but we are still not able to create rds clusters using aurora mysql. And Localstack Error stack trace: |
|
This log seems relevant Can you please try and clear the volume folder? |
|
Thanks @cloutierMat. Working after deleting the old data folder. |
|
Awesome! I love to hear that! Thank you for your feedback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
I am using Pulumi script to create aurora mysql AWS::RDS::Cluster using
localstack-pro:latestimage. With the older images (localstack-pro:3.4.0) of localstack we noticedmysql:latestimages were being used, however, with the latest one's it is usingmysql:8.0.28-oracleimage.I am attaching a minimum reproducible code below using Pulumi:
`import pulumi_aws as aws
aws.rds.Cluster("default",
cluster_identifier="aurora-cluster-demo",
engine=aws.rds.EngineType.AURORA_MYSQL,
engine_version="8.0.mysql_aurora.3.04.1",
availability_zones=[
"us-west-2a",
"us-west-2b",
],
database_name="mydb",
master_username="foo",
master_password="bar",
backup_retention_period=5,
preferred_backup_window="07:00-09:00"
)`
Expected Behavior
The later versions of localstack should be using
mysql:latestimage.How are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstackcommand, arguments, ordocker-compose.yml)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Environment
Anything else?
The text was updated successfully, but these errors were encountered: