[
https://issues.apache.org/jira/browse/RANGER-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binhua Hu updated RANGER-3718:
------------------------------
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，
{code:java}
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 {code}
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.
was:
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 is not judged.
The ranger.sh source code is as follows，
{code:java}
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 {code}
For example, the script(setup.sh) execution is abnormal, but the rangeradmin
process still exists, but the rangeradmin service is unavailable. After the
container is restarted, the script will not be executed again，and the
rangeradmin service will remain unavailable.
> Script exceptions are not considered in ranger-docker
> -----------------------------------------------------
>
> Key: RANGER-3718
> URL: https://issues.apache.org/jira/browse/RANGER-3718
> Project: Ranger
> Issue Type: Improvement
> Components: build-infra
> Affects Versions: 2.0.0, 2.2.0
> Reporter: Binhua Hu
> Priority: Major
>
> 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，
> {code:java}
> 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 {code}
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
