a140262 opened a new pull request, #1901:
URL: https://github.com/apache/incubator-celeborn/pull/1901

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     - Make sure the PR title start w/ a JIRA ticket, e.g. '[CELEBORN-XXXX] 
Your PR title ...'.
     - Be sure to keep the PR description updated to reflect all changes.
     - Please write your PR title to summarize what this PR proposes.
     - If possible, provide a concise example to reproduce the issue for a 
faster review.
   -->
   
   ### What changes were proposed in this pull request?
   Update volumeMounts's name by a dynamic {{ $.Release.Name }} prefix  in 
`master-stateful.yaml` and `worker-stateful.yaml`
   
   ### Why are the changes needed?
   
   When running multiple Celeborn clusters with different release names and 
Celeborn versions, helm install was failed until making the initContainers' 
volume name dynamic. See the error from master's statefulset :
   
   >> kubectl describe statefulset.apps/clbv3-master  -n celeborn
   
   Events:
     Type     Reason        Age                From                    Message
     ----     ------        ----               ----                    -------
     Warning  FailedCreate  5s (x14 over 46s)  statefulset-controller  create 
Pod clbv3-master-0 in StatefulSet clbv3-master failed error: Pod 
"clbv3-master-0" is invalid: spec.initContainers[0].volumeMounts[0].name: Not 
found: "celeborn-master-vol-0"
   
   
   ### Does this PR introduce _any_ user-facing change?
   no
   
   
   ### How was this patch tested?
   Helm install Celeborn cluster twice in the same namespace but different 
release names. It shouldn't fail.
   For example:
   ```
   helm install celeborn charts/celeborn-shuffle-service  -n celeborn
   helm install clbv3 charts/celeborn-shuffle-service  -n celeborn
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to