BIGTOP-4538. Fix deployment error of Ranger on Red Hat distros in container.

[iwasakims]

https://issues.apache.org/jira/browse/BIGTOP-4538

sudo failed with the message like sudo: PAM account management error: Authentication service cannot retrieve authentication info.

[mNotice: /Stage[main]/Ranger::Admin/Package[ranger-admin]/ensure: created[0m
[mNotice: /Stage[main]/Ranger::Admin/Exec[initdb]/returns: executed successfully[0m
[mNotice: /Stage[main]/Ranger::Admin/Service[postgresql]/ensure: ensure changed 'stopped' to 'running'[0m
[mNotice: /Stage[main]/Ranger::Admin/Exec[change_postgres_password]/returns: sudo: PAM account management error: Authentication service cannot retrieve authentication info[0m
[mNotice: /Stage[main]/Ranger::Admin/Exec[change_postgres_password]/returns: sudo: a password is required[0m
[1;31mError: 'sudo -u postgres psql -c "ALTER USER postgres WITH PASSWORD 'admin';"' returned 1 instead of one of [0][0m
[1;31mError: /Stage[main]/Ranger::Admin/Exec[change_postgres_password]/returns: change from 'notrun' to ['0'] failed: 'sudo -u postgres psql -c "ALTER USER postgres WITH PASSWORD 'admin';"' returned 1 instead of one of [0][0m
[mNotice: /Stage[main]/Ranger::Admin/File[/usr/lib/ranger-admin/install.properties]: Dependency Exec[change_postgres_password] has failures: true[0m
[1;33mWarning: /Stage[main]/Ranger::Admin/File[/usr/lib/ranger-admin/install.properties]: Skipping because of failed dependencies[0m
[1;33mWarning: /Stage[main]/Ranger::Admin/Exec[setup.sh]: Skipping because of failed dependencies[0m
[1;33mWarning: /Stage[main]/Ranger::Admin/Exec[set_globals.sh]: Skipping because of failed dependencies[0m
[1;33mWarning: /Stage[main]/Ranger::Admin/Exec[systemctl daemon-reload]: Skipping because of failed dependencies[0m
[1;33mWarning: /Stage[main]/Ranger::Admin/Service[ranger-admin]: Skipping because of failed dependencies[0m

I observed the issue on CI environment. I can not reproduce the error on my local host machines (ubuntu 26.04 x86_64 and MacOS (Mac mini M4)). I guess AppArmor issue of Ubuntu 24.04 is related.

Since initdb using user param of exec resource succeeds, getting rid of using sudo could be the quick fix.

[sekikn]

+1, tested on Rocky Linux 9 (x86_64). Thanks @iwasakims.

[vagrant@rocky9 bigtop]$ curl -sL https://github.com/apache/bigtop/pull/1399.diff | git apply
[vagrant@rocky9 bigtop]$ cd provisioner/docker
[vagrant@rocky9 docker]$ ./docker-hadoop.sh -d -dcp -C config_rockylinux-9.yaml -F docker-compose-cgroupv2.yml -G -L -k bigtop-utils,ranger -s ranger -c 1

(snip)

:bigtop-tests:smoke-tests:ranger:test (Thread[Execution worker for ':' Thread 3,5,main]) completed. Took 0.981 secs.

BUILD SUCCESSFUL in 15s