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

Bug: Error when updating release #207

Open
TheNumenorean opened this issue Sep 17, 2024 · 2 comments
Open

Bug: Error when updating release #207

TheNumenorean opened this issue Sep 17, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@TheNumenorean
Copy link
Contributor

Bug Description

Getting an error when running

helm upgrade --cleanup-on-fail --install --namespace geonode --create-namespace --values values.yml geonode geonode/geonode-k8s

after first installing geonode.

message:

Error: UPGRADE FAILED: cannot patch "pvc-geonode-geonode" with kind PersistentVolumeClaim: PersistentVolumeClaim "pvc-geonode-geonode" is invalid: spec: Forbidden: spec is immutable after creation except resources.requests and volumeAttributesClassName for bound claims
  core.PersistentVolumeClaimSpec{
        ... // 2 identical fields
        Resources:        {Requests: {s"storage": {i: {...}, s: "10Gi", Format: "BinarySI"}}},
        VolumeName:       "pvc-89d37c7a-7549-423b-ae67-5852edc5cda1",
-       StorageClassName: &"hostpath",
+       StorageClassName: nil,
        VolumeMode:       &"Filesystem",
        DataSource:       nil,
        ... // 2 identical fields
  }

Reproduction Steps

Freshly install geonode with the above helm upgrade command, and then run the command a second time with no changes.

Behavior

Command fails, changes arent made if present.

Additional Information

values:

geonode:
  ingress:
    enabled: false
rabbitmq:
  enabled: false
@TheNumenorean TheNumenorean added the bug Something isn't working label Sep 17, 2024
@AlexGacon
Copy link
Collaborator

@TheNumenorean , could you precise which K8s provider you are trying to use? To me, such a message is related on how the PV is managed by your cluster. Perhaps you have to change the storage class to use for the PV.

@TheNumenorean
Copy link
Contributor Author

Thats a fair point, I am using docker desktop kubernetes. And adding global:storageClass: hostpath does avoid the problem.
To me, it seems odd that it would change the setting value on an update without any external changes,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants