Description of problem: When two applications have the same alias, only one application will be listed in the administration console when searching for the alias. Version-Release number of selected component (if applicable): 2.1.6 How reproducible: Always Steps to Reproduce: 1. Create two applications 2. Assign both applications the same alias 3. Search for the alias in the administration console Actual results: Only one application is listed Expected results: Both applications are listed Additional info: Adding two applications with the same alias is not a normal use case, but it is possible and used by at least one enterprise customer.
This condition will only occur when we relax alias constraints with the undocumented broker.conf option PREVENT_ALIAS_COLLISION=false in order to give two apps the same alias. It's also conceivable, though highly unlikely, that the query could come back with multiple apps by virtue of matching on more than one parameter (app uuid, app name, alias). In any case, with this patch multiple matches now are simply displayed. https://github.com/openshift/origin-server/pull/6020
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/dd23d844a85e0147f5fc49a1f8f035f89972fe59 admin-console: allow multiple app search results https://bugzilla.redhat.com/show_bug.cgi?id=1153287 Bug 1153287 - Applications with the same alias are only listed once in the administration console
Should be resolved when we merge upstream changes again.
Verified and pass on puddle-2-2-2015-01-23 1) turn on admin-console by add the follow item in 000002_openshift_origin_broker_proxy.conf ProxyPass /admin-console http://127.0.0.1:8080/admin-console ProxyPass /assets http://127.0.0.1:8080/assets 2) add same alias to different applications 3) search alias named in https://$broker/admin-console/search. all applications can be found.
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. https://rhn.redhat.com/errata/RHBA-2015-0220.html