-
Notifications
You must be signed in to change notification settings - Fork 529
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
[Bug][K8s] Helm upgrade inlong failed #4826
Comments
hello @genshengyang , could you please change docker/kubernetes/templates/mysql-pvc.yaml, to make storageClassName located before accessModes, then try again? |
@lucaspeng12138 the Error above disappear, but the new error has occurred. |
@genshengyang could you show describe information about inlong-mysql-0? |
@genshengyang and describe PersistentVolumeClaim inlong-mysql-data too, thx |
@genshengyang I think this means user "u-cgshvjautw" have no right to access namespace "default". Could you check the rights? |
@lucaspeng12138 thx, it mentions lack of resources, I will try later |
@genshengyang OK. I will submit a pr to fix mysql-pvc.yaml. Please notice me if there is any progress. Thanks a lot. |
@lucaspeng12138 ================================================================= Name: inlong-mysql-0 Warning FailedScheduling 6m2s default-scheduler running "VolumeBinding" filter plugin for pod "inlong-mysql-0": pod has unbound immediate PersistentVolumeClaims ====================================================================== Name: inlong-mysql-data Normal ExternalProvisioning 7m53s persistentvolume-controller waiting for a volume to be created, either by external provisioner "nasplugin.csi.alibabacloud.com" or manually created by system administrator |
@genshengyang I think mysql-pvc is running normally. Is there a PersistentVolume for PersistentVolumeClaim? If exist, may be there are some thing wrong with config. Please use kubectl get pv show access right. |
@lucaspeng12138 |
What happened
helm upgrade inlong failed when volumes.persistence in values.yaml is set to true and volumes.persistence.storageClassName is set to "tke-cfs-storage".
kubectl create namespace inlong
helm upgrade inlong --install -n inlong ./
Error: UPGRADE FAILED: failed to create resource: PersistentVolumeClaim in version "v1" cannot be handled as a PersistentVolumeClaim: v1.PersistentVolumeClaim.Spec: v1.PersistentVolumeClaimSpec.Resources: v1.ResourceRequirements.Requests: unmarshalerDecoder: quantities must match the regular expression '^([+-]?[0-9.]+)([eEinumkKMGTP][-+]?[0-9])$', error found in #10 byte of ...|s-storage"}}}}
|..., bigger context ...|orage":"10Gi","storageClassName":"tke-cfs-storage"}}}}
|...
btw, when I changed the value of volumes.persistence.storageClassName to "tke\-cfs\-storage", the Error above disappeared,
but the new error below had occurred .
Error: UPGRADE FAILED: YAML parse error on inlong/templates/tubemq-broker-statefulset.yaml: error converting YAML to JSON: yaml: line 134: found unknown escape character
What you expected to happen
no errors
How to reproduce
volumes.persistence in values.yaml is set to true and volumes.persistence.storageClassName is set to "tke-cfs-storage"
kubectl create namespace inlong
helm upgrade inlong --install -n inlong ./
Environment
kubectl version
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GoVersion:"go1.18.1", Compiler:"gc", Platform:"windows/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.8-aliyun.1", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
InLong version
1.2.0
InLong Component
Other for not specified component
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: