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

MSK Cluster gets continuously "You can't get bootstrap broker nodes for a cluster in FAILED state." #28

Open
jimdevops19 opened this issue May 22, 2024 · 0 comments

Comments

@jimdevops19
Copy link

Hello, when I call the module with bypassing the required values as follows:

module "msk-cluster" {
  source  = "angelabad/msk-cluster/aws"
  version = "0.5.1"

  cluster_name    = var.name
  instance_type   = var.broker_type
  number_of_nodes = var.number_of_nodes
  kafka_version   = var.kafka_version

  enhanced_monitoring      = "PER_BROKER"
  prometheus_jmx_exporter  = false
  prometheus_node_exporter = false

  s3_logs_bucket = var.s3_logs_bucket
  s3_logs_prefix = "my-env"

  encryption_in_transit_client_broker           = "TLS"
  encryption_in_transit_in_cluster              = true
  client_authentication_unauthenticated_enabled = true

  volume_size       = 100
  tags              = var.tags
  server_properties = var.server_properties
}

I always receive this error, when I attempt to create a new MSK:

│ Error: reading MSK Cluster (my-aws-arn-hidden) bootstrap brokers: BadRequestException: You can't get bootstrap broker nodes for a cluster in FAILED state.
│ {
│   RespMetadata: {
│     StatusCode: 400,
│     RequestID: "<request-id>"
│   },
│   Message_: "You can't get bootstrap broker nodes for a cluster in FAILED state."
│ }
│ 
│   with module.msk_data_platform_events.module.msk-cluster.aws_msk_cluster.this,
│   on **.terraform/modules/msk_data_platform_events.msk-cluster/main.tf** line 108, in resource "aws_msk_cluster" "this":
│  108: resource "aws_msk_cluster" "this" {

Some additional things I discovered:

  • When things go wrong, due to these lines mentioned in the exception, destruction also does not work. Probably since I "try to get bootstrap broekr nodes for a cluster in Failed state"

  • Sometimes manual destruction of the MSK (From AWS UI) was making a hacky fix to the issue and I would get an MSK with Active state and the problem was solved.

So how could I reach a situation that I would be able to go through destruction without getting this error too ?
Is there anything I could check for really being able to create the MSK and reach the expected state ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant