Red Hat Bugzilla – Bug 895864
Should provide meaningful error message when adding existing alias to another app if two applications belong to two accounts separately
Last modified: 2017-03-08 12:35 EST
+++ This bug was initially created as a clone of Bug #874405 +++ Description of problem: Add an alias to app which belongs to one account,and try to add the same alias to another app which belongs to another account,can not add successfully,but have not meaningful error message,will prompt like:Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support. Should have meaningful prompt for user. Version-Release number of selected component (if applicable): OpenShift Enterprise puddle: 1.1.x/2013-01-14.3 rhc 1.3.2 from the puddle How reproducible: Always Steps to Reproduce: 1.Create an app(app1) using one account rhc app create -a app1 -t php-5.3 -l wsun@redhat.com 2.Create another app(app2) using another account rhc app create -a app2 -t php-5.3 -l wsun+1@redhat.com 3.Add alias for app1 rhc alias add app1 test.com 4.Add the same alias for app2 rhc alias add app2 test.com Actual results: 3.[sunwei@dhcp-8-229 dev]$ rhc alias add rack8test test.com -l wsun+1@redhat.com Password: ****** RESULT: Application event 'add-alias' successful 4.[sunwei@dhcp-8-229 dev]$ rhc alias add rack9test test.com -l wsun@redhat.com Password: ****** Node execution failure (invalid exit code from node). If the problem persists please contact Red Hat support. Expected results: Show meaningful prompt: The alias is already in use. Additional info:
Should be fixed in 1.2, please re-test.
move it to VERIFIED due to this issue has been fixed on puddle: http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.2/2013-05-14.1/
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1031.html