You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I previously used the inititializer from #1328 to support separate dataroots per cluster, but want to switch to the official implementation using the per_cluster_dataroot config option.
However, setting per_cluster_dataroot: true leads to internal server errors when trying to start a new interactive app session.
I was able to fix the error by changing the method prefill_templates_root in apps/sys/dashboard/app/controllers/batch_connect/session_contexts_controller.rb to the following, but I'm not sure if using per cluster dataroots makes sense here. At least for our portal, @app.clusters is empty for all apps, so the method would have to default to the non cluster specific path anyway.
Thanks for the ticket. Yes per_cluster_dataroot isn't quite in full support yet mostly because of the job composer. To have full support, we'd need to support it there and we're re-writing it.
I suspect we may get this fixed in #2973 which will happen before 3.1.
I previously used the inititializer from #1328 to support separate dataroots per cluster, but want to switch to the official implementation using the
per_cluster_dataroot
config option.However, setting
per_cluster_dataroot: true
leads to internal server errors when trying to start a new interactive app session.I was able to fix the error by changing the method
prefill_templates_root
inapps/sys/dashboard/app/controllers/batch_connect/session_contexts_controller.rb
to the following, but I'm not sure if using per cluster dataroots makes sense here. At least for our portal,@app.clusters
is empty for all apps, so the method would have to default to the non cluster specific path anyway.Full error message:
The text was updated successfully, but these errors were encountered: