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

not able to spin up mysql #1037

Open
rgmekala opened this issue Jan 22, 2025 · 0 comments
Open

not able to spin up mysql #1037

rgmekala opened this issue Jan 22, 2025 · 0 comments

Comments

@rgmekala
Copy link

rmekala@MacBook-Pro-35 Rama-Work % kubectl -n everest get pods                            
NAME                                               READY   STATUS             RESTARTS     AGE
c1-cfg-0                                           2/2     Running            0            28m
c1-mongos-0                                        1/1     Running            0            27m
c1-rs0-0                                           2/2     Running            0            28m
c1-rs1-0                                           2/2     Running            0            28m
mysql-c1-haproxy-0                                 1/2     Running            0            2m47s
mysql-c1-pxc-0                                     0/1     CrashLoopBackOff   1 (8s ago)   2m47s
percona-postgresql-operator-6d458c7cc9-dfh4n       1/1     Running            0            74m
percona-server-mongodb-operator-6fcbb8cdb4-jq482   1/1     Running            0            74m
percona-xtradb-cluster-operator-6ccbf6547c-ftf52   1/1     Running            0            74m
rmekala@MacBook-Pro-35 Rama-Work % kubectl -n everest get events|grep mysql-c1|grep -i err
42s         Warning   Unhealthy               pod/mysql-c1-haproxy-0                              Readiness probe failed: ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 2
53s         Warning   Unhealthy               pod/mysql-c1-haproxy-0                              Liveness probe failed: ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 2
26s         Warning   Unhealthy               pod/mysql-c1-pxc-0                                  Readiness probe failed: ERROR 2003 (HY000): Can't connect to MySQL server on '10.244.0.53:33062' (111)...
2m54s       Warning   FailedCreate            statefulset/mysql-c1-pxc                            create Pod mysql-c1-pxc-0 in StatefulSet mysql-c1-pxc failed error: Pod "mysql-c1-pxc-0" is invalid: [spec.containers[0].env[2].valueFrom.secretKeyRef.name: Invalid value: "": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.containers[0].env[3].valueFrom.secretKeyRef.name: Invalid value: "": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.containers[0].env[4].valueFrom.secretKeyRef.name: Invalid value: "": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*'), spec.containers[0].env[6].valueFrom.secretKeyRef.name: Invalid value: "": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')]
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