Bug 859895

Summary: [fork] Caught "node execution failure" when adding mysql/postgresql cartridge to app again after it's removed.
Product: OKD Reporter: Jianwei Hou <jhou>
Component: ContainersAssignee: Mrunal Patel <mpatel>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: jizhao, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-06 18:49:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
development.log none

Description Jianwei Hou 2012-09-24 10:51:59 UTC 
Created attachment 616465 [details]
development.log

Description of problem:
Create an app and embed mysql/postgresql, remove mysql/postgresql and embed it back again, caught node execution failure.

Version-Release number of selected component (if applicable):
On fork_ami_US2105_133

How reproducible:
Always

Steps to Reproduce:
1. Create an application and embed mysql/postgresql 
2. remove mysql/postgresql from app
3. embed mysql/postgresql back again
  
Actual results:
hjw@my n1$ rhc app cartridge add -a r18 -c mysql-5.1 -pxxx -d
Contacting https://ec2-107-21-160-59.compute-1.amazonaws.com
Problem reported from server. Response code was 500.

DEBUG:
MySQL already running
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Failed to create r18
Cartridge return code: 188

Exit Code: 143
broker_c: ["namespace", "rhlogin", "ssh", "app_uuid", "debug", "alter", "cartridge", "cart_type", "action", "app_name", "api"]
api_c: ["placeholder"]
API version:    1.1.3

RESULT:
Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support.


Expected results:
Should embed mysql/postgresql successfully.

Additional info:
development.log is attached.
Comment 1 Mrunal Patel 2012-09-25 19:41:21 UTC 
Fixed in branch.
Comment 2 Xiaoli Tian 2012-09-27 05:46:00 UTC 
Move it to ON_QA to verify in fork_ami_US2105_169
Comment 3 jizhao 2012-09-27 11:03:18 UTC 
Verify this bug on fork_ami_US2105_169.

Steps to Reproduce:
1. Create an application and embed mysql/postgresql 
2. remove mysql/postgresql from app
3. embed mysql/postgresql back again

Actual results:
3. mysq/postgresql can be added back and connected successfully.