aws-controllers-k8s/community

SQS resource MissingParameter error

omri-shilton opened this issue · 6 comments

omri-shilton commented

Describe the bug
when creating a SQS resource im getting this error in the status message
MissingParameter: The request must contain the parameter Attribute.Name.\n\tstatus code: 400, request id: db047e34-c891-50a8-8b3a-210f137c5f41

Steps to reproduce
create an sqs resource

Expected outcome
not getting this error

Environment

  • Kubernetes version
  • Using EKS (yes/no), if so version?
  • AWS service targeted (S3, RDS, etc.) SQS
a-hilaly commented

Hi @omri-shilton can you please provide an SQS manifest sample?

omri-shilton commented 
apiVersion: sqs.services.k8s.aws/v1alpha1
kind: Queue
metadata:
  annotations:
  finalizers:
    - finalizers.sqs.services.k8s.aws/Queue
  labels:
    argocd.argoproj.io/instance: stg-edr-schedulers
      manager: controller
      operation: Update
      subresource: status
      time: '2024-08-27T07:49:27Z'
  name: edr-schedulers-edr-send-email
  namespace: webapps
  resourceVersion: '264471203'
status:
  ackResourceMetadata:
    arn: arn:aws:sqs:eu-west-2:1234567899:edr-send-email
    ownerAccountID: '12312312312'
    region: eu-west-2
  conditions:
    - message: "MissingParameter: The request must contain the parameter Attribute.Name.\n\tstatus code: 400, request id: 37b786c0-a6f9-514f-b7ec-d98721beeb5a"
      status: 'True'
      type: ACK.Recoverable
    - lastTransitionTime: '2024-08-27T07:49:27Z'
      message: >-
        Unable to determine if desired resource state matches latest observed
        state
      reason: "MissingParameter: The request must contain the parameter Attribute.Name.\n\tstatus code: 400, request id: 37b786c0-a6f9-514f-b7ec-d98721beeb5a"
      status: Unknown
      type: ACK.ResourceSynced
  queueURL: https://sqs.eu-west-2.amazonaws.com/123123123/edr-send-email
spec:
  queueName: edr-send-email
driv commented

I'm getting the same issue with image: public.ecr.aws/aws-controllers-k8s/sqs-controller:1.0.16

driv commented

Should an issue be opened in https://github.com/aws-controllers-k8s/sqs-controller ?

NVM, I see that there are no issues in that project.

a-hilaly commented

I was able to reproduce locally... working on patch for this.

a-hilaly commented

This is now fixed in sqs-controller v1.1.0