Bug 895864
| Summary: | Should provide meaningful error message when adding existing alias to another app if two applications belong to two accounts separately | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ziqian SUN (Zamir) <zsun> |
| Component: | Node | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0.0 | CC: | bleanhar, bmeng, gpei, libra-onpremise-devel, lmeyer, rmillner, szhou, wsun, xjia |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 19:49:59 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: | |||
| Bug Depends On: | 874405 | ||
| Bug Blocks: | |||
|
Description
Ziqian SUN (Zamir)
2013-01-16 07:27:09 UTC
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 |