dgoodwin and I ran into a situation where turning off FORCECERT=1 or true is not FORCECERT=0 The setting to turn off FORCECERT is FORCECERT="" Thats not very user friendly :) Lets make sure all the candlepin env vars are consistent and have a positive and negative value. Something like true=1, false=0
6b0e154335ff8d692bd92864cd14222da81c3966 Switched GENDB and FORCECERT to look for "1" to enable, anything else we assume means disable.
[root@jsefler-f12-candlepin candlepin]# git show-ref master 35b05045626775ae02cb42eb6c67cfa7e6e2ba14 refs/heads/master 35b05045626775ae02cb42eb6c67cfa7e6e2ba14 refs/remotes/origin/master [root@jsefler-f12-candlepin candlepin]# pwd /root/candlepin [root@jsefler-f12-candlepin candlepin]# ls client proxy README rel-eng [root@jsefler-f12-candlepin candlepin]# find . -wholename "*" | xargs -i[] grep FORCECERT "[]" if [ -f $CA_KEY ] && [ -f $CA_CERT ] && [ "$FORCECERT" != "1" ]; then if [ "$FORCECERT" = "1" ]; then [root@jsefler-f12-candlepin candlepin]# find . -wholename "*" | xargs -i[] grep GENDB "[]" GENDB=1 IMPORTDIR=$IMPORTDIR buildconf/scripts/deploy if [ "$GENDB" == "1" ]; then - Fix GENDB in deploy script. (dgoodwin) LOOKING AT THE LOGIC FOR ALL CODED OCCURRENCES OF ENV VARS (FORCECERT and GENDB), THEY BOTH ARE TRUE ONLY WHEN SET TO 1. ANY OTHER VALUE OR LACK THEREOF IS A FALSE. VERIFIED THE CODE SUCH THAT... "1" means true !"1" means false
Group move of VERIFIED Candlepin component bugs to RELEASE_PENDING