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
Bug description
Dolphinnext cannot validate ssh connection and submit jobs if the user's shell is fish and not bash.
To Reproduce
Connect to your HPC (remote)
change your default shell to fish (chsh -s /usr/bin/fish <USER>)
3a. Try validate a ssh connection will creating a new environement run
3b. Try to run any pipeline
Expected behavior
From your local workstation (hosting dolphinnext)
==> 3a. Validation failed
==> 3b. /etc/profile (line 13): Unsupported use of '='. In fish, please use 'set PS1 '# ''.
from sourcing file /etc/profile
source: Error while reading file '/etc/profile'
Hi, could you try adding chsh -s /bin/bash <USER> in the run command section of your run environment? This command will be executed before executing other commands.
this command ask for the user password, and I don't to have my password wrote in clear anywhere :)
this command change the default login shell of the user, so instead of executing this command each time a pipeline is started, it's would be simpler to just run the command once for all. But, I really love fish don't really want to go back to bash.
One solution, I guess, would be to explicitly run the command with bash with it's -c option :
Bug description
Dolphinnext cannot validate ssh connection and submit jobs if the user's shell is fish and not bash.
To Reproduce
chsh -s /usr/bin/fish <USER>
)3a. Try validate a ssh connection will creating a new environement run
3b. Try to run any pipeline
Expected behavior
From your local workstation (hosting dolphinnext)
==> 3a. Validation failed
==> 3b. /etc/profile (line 13): Unsupported use of '='. In fish, please use 'set PS1 '# ''.
from sourcing file /etc/profile
source: Error while reading file '/etc/profile'
Temporary FIX
chsh -s /bin/bash <USER>
on HPCOS (both local and remote machines)
The text was updated successfully, but these errors were encountered: