MySQL Bugs: #108458: Sidecar container fails during initialization

Bug #108458	Sidecar container fails during initialization
Submitted:	11 Sep 2022 15:58	Modified:	15 Oct 2022 9:32
Reporter:	Alisher Urunov	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Operator	Severity:	S3 (Non-critical)
Version:	2.0.6	OS:	Other
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	operator

Description:
When initializing InnoDBCluster sidecar container fails for one of the pods with the following error:
Handler 'on_pod_create' failed temporarily: Sidecar of global-cluster-0 is not yet configured
POD CREATED: pod=global-cluster-0 ContainersReady=False Ready=False gate[configured]=None

Due to this other pods remain in pending status and no router pods are created.

I do have, however, a sidecar from Istio injected into the deployments, they are however configured as per suggestion from Istio with peer authentication policies and destination rules.

How to repeat:
resource "helm_release" "mysql-operator" {
  name       = "mysql-operator"
  repository = "https://mysql.github.io/mysql-operator/"
  chart      = "mysql-operator"
  namespace  = "mysql-operator"
  version    = "2.0.6"

  depends_on = [
    kubernetes_namespace.mysql-operator-ns,
    kubernetes_namespace.database-ns
  ]
}

resource "kubernetes_manifest" "innodbcluster_mycluster" {
  manifest = {
    "apiVersion" = "mysql.oracle.com/v2"
    "kind"       = "InnoDBCluster"
    "metadata"   = {
      "name"      = "global-cluster"
      "namespace" = "database"
    }
    "spec" = {
      // Support for lower versions is disabled
      "version" = "8.0.30"
      "baseServerId"    = 1000
      "imagePullPolicy" = "IfNotPresent"
      "instances"       = 3
      "router"          = {
        "instances" = 1
        // Support for lower versions is disabled
        "version" = "8.0.30"
      }
      "datadirVolumeClaimTemplate" = {
        "accessModes" = [
          "ReadWriteOnce",
        ]
        "resources" = {
          "requests" = {
            "storage" = "10Gi"
          }
        }
      }
      "mycnf" = <<-EOT
      [mysqld]
      max_connections=162
      EOT
      "secretName"         = "global-database-cluster-secret"
      "serviceAccountName" = "global-database-sa"
      "tlsUseSelfSigned"   = true
    }
  }
}

Hi,

We replaced 8.0.30 release yesterday so might be useful to retest this today.

Can you upload full log files?

thanks

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

hi,
I have same problem with above post.
mysql operator version: 8.0.31-2.0.7
v1.25.4         
CentOS Linux 7 (Core)3.10.0-1160.el7.x86_64   
containerd://1.6.8

after apply mysqlcluster yaml file, this error keep showing and mysql sidecar pod cannot running. always pending..