Issue Watch out for 17.8 cronjob bug

[HostaHost]

Just wanted to let everyone know about a bug I've encountered with our first instance of 17.8 testing, on CentOS 6. If a subscription has its shell set to chrooted, even if you've overridden the shell to use for cron jobs, all your subscriptions' cron jobs will be set to a chrooted shell when you upgrade, likely breaking nearly anything if it hadn't been chrooted previously.

Easy enough to reproduce. Install 17.5, set a subscription's shell to "/bin/bash (chrooted)", add a cron job. You'll end up with this in the user's crontab:

SHELL="/usr/local/psa/bin/chrootsh"

Now execute:

/usr/local/psa/bin/server_pref --update -crontab-secure-shell "/bin/bash"

You'll end up with this in the user's crontab:

SHELL="/bin/bash"

If you upgrade to 17.8, that line will revert to the chrootsh shell, and no variation of the server_pref command will get it to go back. However, if the subscription is set to Forbidden, then the desired effect occurs and the crontab gets /bin/bash back, so this issue only occurs if a subscription is set to chrooted; in that case, the cronjobs will be reset to chrooted and any future modification will reset them to chrooted even if you had hand edited the crontab to remove the chroot shell line.

 

[IgorG]

Thank you for the report, but we would be grateful if you could submit your reports in a more suitable place.
This will help our developers to better understand the problem.