[RANGER-3718] Script exceptions are not considered in ranger-docker

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 2.2.0
• Component/s: build-infra
• Assignee: Abhishek Kumar
• Reporter: Binhua Hu
• Created: 19/Apr/22 02:26
• Updated: 09/May/22 21:39
• Resolved: 09/May/22 21:39

Description

There is a problem with the ranger.sh script in the dev-support/ranger-docker/scripts directory. When the ranger.sh script is executed, the file(.setupDone) is created directly. The execution result of the script(setup.sh) is not judged.

The ranger.sh source code is as follows，

if [ ! -e ${RANGER_HOME}/.setupDone ]
then  
   SETUP_RANGER=true
else  
   SETUP_RANGER=falsefi
if [ "${SETUP_RANGER}" == "true" ]
then  
   cd ${RANGER_HOME}/admin && ./setup.sh

  touch ${RANGER_HOME}/.setupDone
fi

cd ${RANGER_HOME}/admin && ./ews/ranger-admin-services.sh start 

 

For example, the script(setup.sh) execution is abnormal, but the rangeradmin process still exists, and the rangeradmin service is unavailable. After the container is restarted, the script will not be executed again，and the rangeradmin service will remain unavailable.