# After Change ClusterServiceVersion yaml, I am getting Init error **URL:** \ **Category:** Percona Operator for MySQL\ **Created:** [November 21, 2023, 1:30am UTC](https://forums.percona.com/t/after-change-clusterserviceversion-yaml-i-am-getting-init-error/26672 "2023-11-21T01:30:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Ahmet\_Oruc](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ahmet_oruc/32/12357_2.png) [@Ahmet\_Oruc](https://forums.percona.com/u/Ahmet_Oruc)\ **Post date:** [November 21, 2023, 1:30am UTC](https://forums.percona.com/t/after-change-clusterserviceversion-yaml-i-am-getting-init-error/26672/1 "2023-11-21T01:30:43Z")
## Description: [Detailed description of the issue or question] I changed to the cluster configuration, after that the cluster1-pxc-2 pod stucked in pxc-init ## Steps to Reproduce: [Step-by-step instructions on how to reproduce the issue, including any specific settings or configurations] I reverted to the change, however, the init process has not changed. ## Version: [Insert the version number of the software] 1.13.0 ## Logs: [If applicable, include any relevant log files or error messages] ++ id -u 2++ id -g 3+ install -o 2 -g 2 -m 0755 -D /pxc-entrypoint.sh /var/lib/mysql/pxc-entrypoint.sh 4install: cannot remove ‘/var/lib/mysql/pxc-entrypoint.sh’: Permission denied ## Expected Result: [What the user expected to see or happen before the issue occurred] ## Actual Result: [What actually happened when the user encountered the issue] ## Additional Information: [Include any additional information that could be helpful to diagnose the issue, such as browser or device information] Operator Yaml is below: apiVersion: [pxc.percona.com/v1](http://pxc.percona.com/v1) kind: PerconaXtraDBCluster metadata: finalizers: - delete-pxc-pods-in-order name: cluster1 namespace: s-devops spec: proxysql: affinity: antiAffinityTopologyKey: [kubernetes.io/hostname](http://kubernetes.io/hostname) enabled: false gracePeriod: 30 image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:df845ab993fd1229567f62338c69e27ce65d1aeec66455f576f55ecce50eda9f](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:df845ab993fd1229567f62338c69e27ce65d1aeec66455f576f55ecce50eda9f) podDisruptionBudget: maxUnavailable: 1 resources: requests: cpu: 600m memory: 1G size: 3 volumeSpec: persistentVolumeClaim: resources: requests: storage: 2G upgradeOptions: apply: disabled schedule: 0 4 \* \* \* versionServiceEndpoint: ‘[https://check.percona.com](https://check.percona.com)’ backup: image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:1687127a1f86ff48b2623f6be7176ff693631e870f3920d137d5fba31c923a68](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:1687127a1f86ff48b2623f6be7176ff693631e870f3920d137d5fba31c923a68) pitr: enabled: false storageName: STORAGE-NAME-HERE timeBetweenUploads: 60 schedule: - keep: 365 name: daily-s3-backup schedule: 0 1 \* \* \* storageName: s3-us-west storages: azure-blob: azure: container: test credentialsSecret: azure-secret type: azure fs-pvc: type: filesystem volume: persistentVolumeClaim: accessModes: - ReadWriteOnce resources: requests: storage: 10G s3-us-west: s3: bucket: shbdn-devops-percona-mysqlbackup-daily credentialsSecret: cluster1-s3-credentials endpointUrl: ‘[https://storage.googleapis.com/](https://storage.googleapis.com/)’ region: europe-west1 type: s3 crVersion: 1.13.0 logcollector: enabled: true image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:4465f029d19fb9c86d0aaa64e1b8a1695efd2665ae2b4820546434d57f433a65](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:4465f029d19fb9c86d0aaa64e1b8a1695efd2665ae2b4820546434d57f433a65) resources: requests: cpu: 200m memory: 100M allowUnsafeConfigurations: false pmm: enabled: false image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:a18f0c877c6f01408dc3a25caddc0a54c73c21bbd931942bd775c45e67a03876](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:a18f0c877c6f01408dc3a25caddc0a54c73c21bbd931942bd775c45e67a03876) resources: requests: cpu: 300m memory: 150M serverHost: monitoring-service haproxy: affinity: antiAffinityTopologyKey: [kubernetes.io/hostname](http://kubernetes.io/hostname) enabled: true gracePeriod: 30 image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:c36bab0d21d0530cdad2d53f111bda75022bec6d6adc5fbd63238462ada43c75](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:c36bab0d21d0530cdad2d53f111bda75022bec6d6adc5fbd63238462ada43c75) podDisruptionBudget: maxUnavailable: 1 resources: requests: cpu: 600m memory: 1G size: 3 pxc: size: 3 autoRecovery: true expose: enabled: true type: NodePort resources: requests: cpu: 600m memory: 1G affinity: antiAffinityTopologyKey: [kubernetes.io/hostname](http://kubernetes.io/hostname) volumeSpec: persistentVolumeClaim: resources: requests: storage: 6G gracePeriod: 600 image: \>- [registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:e33af88c3b48aef890af9e77901234d9458d9d1d7666b7d41c86a686f6ad7ccb](http://registry.connect.redhat.com/percona/percona-xtradb-cluster-operator-containers@sha256:e33af88c3b48aef890af9e77901234d9458d9d1d7666b7d41c86a686f6ad7ccb) replicationChannels: - isSource: true name: cluster1\_to\_cluster2 podDisruptionBudget: maxUnavailable: 1 updateStrategy: SmartUpdate ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [November 21, 2023, 1:18pm UTC](https://forums.percona.com/t/after-change-clusterserviceversion-yaml-i-am-getting-init-error/26672/2 "2023-11-21T13:18:56Z")
hey! @Ahmet_Oruc what is the storage class that you use? ---
**Author:** ![Ahmet\_Oruc](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ahmet_oruc/32/12357_2.png) [@Ahmet\_Oruc](https://forums.percona.com/u/Ahmet_Oruc)\ **Post date:** [November 21, 2023, 2:01pm UTC](https://forums.percona.com/t/after-change-clusterserviceversion-yaml-i-am-getting-init-error/26672/3 "2023-11-21T14:01:01Z")
My default storage is ocs-storagecluster-ceph-rbd which is Openshift ODF for fs-pvc. And another backup environment is Google Cloud Bucket. Both of them are not running. By the way, I was taking SSL errors when XtraBackup Pod was connected to the third Mysql pod which is cluster1-pxc-2. After changing the SSL parameter to allowUnsafeConfigurations–\>true, the cluster1-pxc-2 got stuck in the init phase. The logs are below: 2++ id -g 3+ install -o 2 -g 2 -m 0755 -D /pxc-entrypoint.sh /var/lib/mysql/pxc-entrypoint.sh 4install: cannot remove ‘/var/lib/mysql/pxc-entrypoint.sh’: Permission denied