Red Hat Bugzilla – Bug 1015571
Unable to install scalable drupal via web console
Last modified: 2015-05-14 22:25:21 EDT
Description of problem:
The below red message was displayed during drupal installation.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Clicked on the drupal+scalable
The initial build for the application failed: Shell command '/sbin/runuser -s /bin/sh 221b56d62cfc11e389ef12313d14d1f1 -c "exec /usr/bin/runcon 'unconfined_u:system_r:openshift_t:s0:c0,c505' /bin/sh -c \"gear postreceive >> /tmp/initial-build.log 2>&1\""' returned an error. rc=255 .Last 10 kB of build output: Stopping PHP cartridge Syntax error on line 2 of /var/lib/openshift/221b56d62cfc11e389ef12313d14d1f1/php/configuration/etc/conf.d/openshift.conf: DocumentRoot must be a directory httpd (no pid file) not running Building PHP cartridge Checking pear: pear.drush.org/drush Attempting to discover channel "pear.drush.org"... downloading channel.xml ... Starting to download channel.xml (804 bytes) ....done: 804 bytes Auto-discovered channel "pear.drush.org", alias "drush", adding to registry downloading drush-188.8.131.52.tgz ... Starting to download drush-184.108.40.206.tgz (504,788 bytes) ...done: 504,788 bytes install ok: channel://pear.drush.org/drush-220.127.116.11 /var/lib/openshift/221b56d62cfc11e389ef12313d14d1f1/app-root/runtime/repo/.openshift/action_hooks/build: line 24: /var/lib/openshift/221b56d62cfc11e389ef12313d14d1f1//.drush/drushrc.php: No such file or directory An error occurred executing 'gear postreceive' (exit code: 1) Error message: Failed to execute action hook 'build' for 221b56d62cfc11e389ef12313d14d1f1 application drupaljenkinsscalable For more details about the problem, try running the command again with the '--trace' option.
This limitation is outlined in the quickstart README: https://github.com/openshift/drupal-quickstart/blob/master/README.md
I do not think this can be handled by runtime. I'm sending this to CLI, as this caveat should be outline on the web console.
Created attachment 807730 [details]
Actually, this is explicitly stated in the Drupal quickstart page on PRD.
Created attachment 807732 [details]
…as well as on the AMI image (ami-850749ec, a.k.a. devenv-stage_465) in question.
What else exactly can we do?
ok, if this is issue well known for scalable apps. I'm ok with that.