Bug 997320 - misleading help text for adding alias.
Summary: misleading help text for adding alias.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Website
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: chris alfonso
QA Contact: libra bugs
URL:
Whiteboard:
Depends On: 997567
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-15 07:16 UTC by Peter Ruan
Modified: 2016-05-25 13:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 997567 (view as bug list)
Environment:
Last Closed: 2013-08-28 13:04:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Ruan 2013-08-15 07:16:07 UTC
Description of problem:
  When trying to enter an alias from the UI for my app, the help text is misleading and incorrect

Enter your custom domain name. e.g. www.example.com or something.example.com

  If I were to put test.example.com it will display the error.  "Invalid Server Alias 'ppp.example.com' specified".  From the code, it looks like if the instance's hostname has example.com as part of the domain name it will be flagged as error, therefore the help text in the UI is incorrect.

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

How reproducible:
always.

Steps to Reproduce:
1.  In the UI's add alias text box, enter something like test.example.com
2.
3.

Actual results:
failed with the error similar to Invalid Server Alias 'ppp.example.com' specified"

Expected results:
success.

Additional info:

Comment 1 Brenton Leanhardt 2013-08-15 14:36:53 UTC
Does this happen in Online if you choose an rhcloud.com domain for your alias?  If so we should work on the bug there.

Comment 2 Peter Ruan 2013-08-15 15:43:56 UTC
Yes, if I were to put test.rhcloud.com as my alias it throws the same error.  I think it's the regular expression that's flagging it.

Comment 4 Brenton Leanhardt 2013-08-28 13:04:38 UTC
We'll pick this up in the next rebase.


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