Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 895864 - Should provide meaningful error message when adding existing alias to another app if two applications belong to two accounts separately
Should provide meaningful error message when adding existing alias to another...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
1.0.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Luke Meyer
libra bugs
: Triaged
Depends On: 874405
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-16 02:27 EST by Ziqian SUN (Zamir)
Modified: 2017-03-08 12 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When a user added an alias to an application, the broker did not check if another app already has that alias. Consequence: If a duplicate alias was added, it could silently succeed if the gear landed on a different node host from the application with the existing alias, or it would fail with an unexplained "node execution error" if it landed on the same node. Fix: Fixed by changes made in the model refactor for OSE 1.2; upgrade to OSE 1.2. Result: Duplicate aliases will be rejected by the broker. The alias must be removed from the previous app in order to add it to the new app.
Story Points: ---
Clone Of: 874405
Environment:
Last Closed: 2013-07-09 15:49:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1031 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 1.2 Infrastructure Release Advisory 2013-07-09 19:48:02 EDT

  None (edit)
Description Ziqian SUN (Zamir) 2013-01-16 02:27:09 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:
Comment 10 Luke Meyer 2013-05-14 14:53:00 EDT
Should be fixed in 1.2, please re-test.
Comment 11 Gaoyun Pei 2013-05-15 04:40:48 EDT
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/
Comment 13 errata-xmlrpc 2013-07-09 15:49:59 EDT
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

Note You need to log in before you can comment on or make changes to this bug.