BOA daily.sh and other relevant scripts not working for some platforms while working on others

[aanjaneyam]

The problem I have is regarding automatic procedure of daily enabling, disabling and availability of modules in BOA. I followed these steps:

1) Composer create the custom varbase platform.
2) Add the platform to agegir and create the main site with .dev. keyword in its domain name.
3) I also add a dev. alias with no redirection to the above site.
4) I create another{staging} platform identical to the development in 1 above using git and composer install.
5) I clone the site created in no. 2 above with the keyword .stage. in its domain name and successfully migrate it to new staging platform
6) I create another{LIVE} platform identical to the development in 1 above using git and composer install.
7) I clone the site created in no. 2 above with a key word .live. in it's domain name and successfully migrate it to Live platform.
8) so now I have three indentical platforms (just names differet - dev, stage and live) and and have 3 identical/ cloned sites, one in each platform,

Now the problem is that: 1) In the 1st dev site (created in step 2) in dev platform I have update manager and syslog already enabled and redis UNAVAILABLE by default. robots_txt is also disabled in dev and the robots.txt file at drupal root is not deleted. 2) In the 2nd stage site (created in step 5) in dev platform I have update manager and syslog already enabled and redis module UNAVAILABLE by default. robots_txt is also disabled in stage and the robots.txt file at drupal root is not deleted. 3) In the 3rd live site (created in step 7) in dev platform I have update manager and syslog DISABLED whereas redis module ENABLED by default. While robots_txt is enabled in live platform and the robots.txt file at drupal root has been deleted.

So what is update and syslog are enabled automatically in dev and stage sites while redis is UNAVAILABLE and robots.txt is disabled AND update and syslog are disabled by default in the .live. site while redis and robots.txt is enabled by default. Is the above an intended effect based on keywords in respective site's domain name.

I tried to do every things which came to my mind like running barracuda up-head, running permissions fix scripts etc but no effect. The only change I saw after running barracuda up-head and octopus up-head was that the redis module which was previously unavailable in dev and stage platforms became available but were still disabled.

/var/xdrago/log/daily/* do not show any clue either except that they are working for live and demo platforms but not having any effect on dev and stage platforms.

One more thing comes to my mind. I made accidental mistakes when adding the composer based dev and stage platforms to aegir by providing platform path as the project_root rather than project_root/docroot and tried to verify them twice despite error. I only realised later that it is composer code and added docroot to the platform path and then the platform was successfully added to aegir. I did not do the same mistake in demo and live platforms. I am not sure if it has any effect on anything.

[aanjaneyam]

I was wondering if there is any clue to the above. Looks like the daily.sh is somehow not seeing the correct platform and site path even though it displays correctly on the the aegir panel UI and platform/site verifies correctly.

Anyway to check what platform path the script is seeing.

[omega8cc]

It's hard to tell without access to your system to check details, and we can't reproduce the problem ourselves. Very unusual, perhaps some directory structure/keyword exception etc.

[aanjaneyam]

Which keywords. The directory structure is the standard composer directory. The following are my main site names:

1) foo.dev.o1.server.mydomain.org (The Development site in development platform named SomeName Development P001 with platform path at /data/disk/o1/static/somename_development_p001/docroot)

2) foo.stage.o1.server.mydomain.org (The staging site in staging platform named SomeName Stage P001 with platform path at /data/disk/o1/static/somename_stage_p001/docroot)

3) foo.live.o1.server.mydomain.org (The live site in live platform named SomeName Live P001 with platform path at /data/disk/o1/static/somename_live_p001/docroot)

The script works on live but not on stage and dev.

[omega8cc]

While not directly related, we have disabled the procedure of disabling/enabling modules 2e9a37ee2c843419e7d0df95e2b22be82744fa4b -- only redis is enabled in Drupal 8 now. This gargantuan scripts is due for much needed rewrite.