Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to provision Aurora-mysql RDSInstance - InvalidParameterValue: The parameter AllocatedStorage must be provided and must not be null #842

Closed
kiich opened this issue Sep 24, 2021 · 8 comments · Fixed by #852
Labels
bug Something isn't working

Comments

@kiich
Copy link

kiich commented Sep 24, 2021

What happened?

Followed the documentation and examples found in the repo to provision RDSInstance using the yaml below:

apiVersion: database.aws.crossplane.io/v1beta1
kind: RDSInstance
metadata:
  name: myaurora
spec:
  deletionPolicy: Delete
  forProvider:
    dbSubnetGroupName: "dbsubnet"
    region: us-west-2
    deletionProtection: false
    masterUsername: admin
    publiclyAccessible: false
    dbInstanceClass: db.t2.medium
    dbName: myaurora
    engine: aurora-mysql
    tags:
      - key: Team
        value: "My Team"
  providerConfigRef:
    name: crossplane-provider-config
  writeConnectionSecretToRef:
    name: rds-conn-string
    namespace: default

As you can see, i omitted the allocatedStorage setting because the documentation says it is not applicable.
However when i apply the above via crossplane, i am getting:

    message: "create failed: cannot create RDS instance: InvalidParameterValue: The
      parameter AllocatedStorage must be provided and must not be null.\n\tstatus
      code: 400, request id: aaaaa"

I can't seem to find any example code to do the above for aurora-mysql so either i am missing something or doing it the wrong way?

I have seen some posts about creating the Aurora in the AW console manually and then creating a replicate in Crossplane - but that's not what I am aiming to do.

How can we reproduce it?

Apply the yaml above

  • Cloud provider or hardware configuration - AWS
  • Kubernetes version (use kubectl version) - v1.19.13-eks-8df270
  • Kubernetes distribution (e.g. Tectonic, GKE, OpenShift) - EKS
  • OS (e.g. from /etc/os-release) - Amazon Linux
@kiich kiich added the bug Something isn't working label Sep 24, 2021
@eloo
Copy link

eloo commented Sep 28, 2021

Hi, i'm running into the same issue.
According to another issue this is related that its not registered to a dbcluster.

Maybe the best would be to provide a working example how a aurora mysql cluster should be created.
Currently its pretty hard to figure this out because its also not well documented.

Best regards
eloo

@muvaf
Copy link
Member

muvaf commented Sep 28, 2021

I don't know the specific details but I do remember this problem from another issue as @eloo mentioned. I found aws/aws-sdk-go#3222 that is closely related.

But at that time, we didn't have the cluster resource. Now, you can use DBCluster resource to provision an Aurora cluster and join nodes using either DBInstance or RDSInstance. Similar to instructions here.

@eloo
Copy link

eloo commented Sep 28, 2021

@muvaf
Thanks for the hint.
But i guess then we are going to run into this issue #844

@kiich
Copy link
Author

kiich commented Sep 28, 2021

Ah i see @muvaf - thanks for the clarification! The documentation (or the lack of example of it) seemed to indicate I could use RDSInstance to create a RDS instance on its own so I was not aware I had to use the DBCluster AND then join via RDSInstance. I shall try this.

@eloo
Copy link

eloo commented Sep 30, 2021

@kiich had you already time to test it?
did it work for you? because in my case its also not working :(

@haarchri
Copy link
Member

haarchri commented Oct 1, 2021

please check: #852

image

@kiich
Copy link
Author

kiich commented Oct 4, 2021

@eloo I haven't had a chance to but the comment made by @haarchri looks like it might do the trick which I am hoping to try!

@eloo
Copy link

eloo commented Oct 5, 2021

@kiich
yes i can confirm that the new crds seems to work as expected.
i have tested it yesterday with the master branch of the provider and i was able to assign instances to the cluster
👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants