]
weiweijiang jiang commented on JBIDE-15261:
-------------------------------------------
JBT 4.1.0.final.core also got this issue, and I create a [php-5.3,mysql-5.1] app and the
source code is "https://github.com/openshift/drupal-example.git"
Cannot create wordpress example
-------------------------------
Key: JBIDE-15261
URL:
https://issues.jboss.org/browse/JBIDE-15261
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Beta2
Reporter: nan wei
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
Attachments: create-wordpress-example.png, initial-build-failed.png
Version:
JBoss Deverloper Studio 7 Beta
OpenShift Plugin: 2.5.0.Beta2-v20130621-1052-B65
OpenShift Enterprise 1.2/2013-07-18.4
How reproducible:
always
Steps to Reproduce:
1. Create an app in the JBoss Deverloper Studio.
Name: mysqltest
Type: PHP 5.3(php-5.3)
Embeddable Cartridges: MySQL Database 5.1(mysql-5.1)
2. Click Advanced
Add Source
Code:https://github.com/openshift/wordpress-example
!create-wordpress-example.png!
Actual results:
When creating an app, check mysql cartridge and add source code together, it will fail,
and return the following error:
!initial-build-failed.png!
{code}
Could not create application "a3"
Could not request
https://broker.ose0717.com/broker/rest/domains/nwei/applications: The
initial build for the application failed. Last 10 kB of build output:
httpd (no pid file) not running
Could not find mysql database. Please run:
rhc cartridge add -a a3 -c mysql-5.1
then make a sample commit (add whitespace somewhere) and re-push
An error occurred executing 'gear postreceive'
For more details about the problem, try running the command again with the
'--trace' option.
{code}
But if use rhc client, there is no such problem, it is created successfully.
# rhc app create mysqltest1 php-5.3 mysql-5.1
--from-code=https://github.com/openshift/wordpress-example
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: