[
https://issues.apache.org/jira/browse/HDDS-13875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-13875:
------------------------------------
Fix Version/s: helm-0.3.0
(was: helm-0.2.0)
> Wrong context reference in datanode-statefulset.yaml
> ----------------------------------------------------
>
> Key: HDDS-13875
> URL: https://issues.apache.org/jira/browse/HDDS-13875
> Project: Apache Ozone
> Issue Type: Bug
> Components: Helm
> Affects Versions: helm-0.2.0, helm-0.1.1
> Reporter: Damiano Ernesti
> Assignee: Damiano Ernesti
> Priority: Minor
> Labels: pull-request-available
> Fix For: helm-0.3.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The bug is quite simple.
> In datanode-statefulset.yaml, under
> spec.volumeClaimTemplates.spec.storageClassName, the wrong context from the
> helm chart values is selected to populate the value in question.
> As of now it references:
> {code:yaml}
> .Values.scm.persistence.storageClassName{code}
> The correct reference should be:
> {code:yaml}
> .Values.datanode.persistence.storageClassName{code}
> The current reference makes it impossible to select a specific StorageClass
> for the volumes / volume claims of the datanode(s), as the one from the
> Storage Container Manager will be selected for it instead.
> Steps to reproduce:
> # Create a custom values yaml file with:
> {code:java}
> datanode:
> persistence:
> enabled: true
> storageClassName: <your-non-default-storage-class>{code}
> # Apply it with:
> {code:java}
> helm install ozone ozone/ozone --namespace ozone -f ozone-values.yaml
> --dry-run=server{code}
> # Notice that the indicated storageClassName is completely missing in the
> output, other values if indicated will be present as expected
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
