silent-night-no-trace opened a new issue, #17632:
URL: https://github.com/apache/dolphinscheduler/issues/17632

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   The Helm-deployed DataStation cluster was upgraded from version 3.2.2 to 
3.3.1.
   
   I configured a Spark task in the task definition, referencing a pod template 
YAML file uploaded from the resource center.
   
   <img width="990" height="618" alt="Image" 
src="https://github.com/user-attachments/assets/3c5dbb86-7bbb-442c-9e4c-e8d30d4b6f1d";
 />
   
   Scheduling the Spark task worker node resulted in an error: "Resource not 
found: Caused by: java.io.FileNotFoundException: File 
file:/tmp/dolphinscheduler/root/resources/spark-driver-template.yaml does not 
exist".
   
   However, when I checked the uploaded resources on the resource list page, 
the tenant was empty.
   
   
   <img width="1198" height="323" alt="Image" 
src="https://github.com/user-attachments/assets/55d5b6a8-5e3d-4109-b0dd-482cab85c50e";
 />
   
   However, version 3.2.2 runs fine. What should I do?
   
   ### What you expected to happen
   
   spark task runs fine
   
   ### How to reproduce
   
    3.3.1.
   
   configure a Spark task in the task definition, referencing a pod template 
YAML file uploaded from the resource center.
   
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.3.1
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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