Back to bug 1040257
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mike Barrett | 2013-12-11 03:28:56 UTC | Priority | unspecified | high |
| John Keck | 2013-12-12 18:10:58 UTC | Target Release | --- | 2.0.2 |
| CC | jkeck | |||
| Brenton Leanhardt | 2014-01-08 15:39:11 UTC | Target Release | 2.0.2 | 2.0.3 |
| Brenton Leanhardt | 2014-01-09 18:56:16 UTC | Target Release | 2.0.3 | 2.0.2 |
| CC | bleanhar | |||
| Luke Meyer | 2014-01-09 22:20:41 UTC | Status | NEW | ASSIGNED |
| Brenton Leanhardt | 2014-01-17 16:01:51 UTC | Target Release | 2.0.2 | 2.0.3 |
| Luke Meyer | 2014-01-29 03:03:39 UTC | Status | ASSIGNED | MODIFIED |
| Group | redhat | |||
| Fixed In Version | rubygem-openshift-origin-controller-1.17.12.1-1 openshift-origin-broker-1.15.3.1-1 | |||
| Doc Text | Feature: The broker.conf ALLOW_ALIAS_IN_DOMAIN option is introduced; if true, the broker will allow aliases to be created that are in the cloud domain where apps are created, as long as they do not take the standard form of application names, that is, <word>-<word>.<cloud-domain> Reason: Previously (and still by default) this is disallowed in order to prevent confusion or possible name collisions, but some users wanted to be able to do this. Result (if any): When enabled, users who can create aliases can do so within the cloud domain. Only standard name collisions are prevented; no attempt is made to prevent collisions with HA app names. Such name collisions, should they occur on the same node host, could result in traffic being routed to the wrong gear on the node host. OpenShift still does not create a DNS entry for the alias; that is an external step. | |||
| Doc Type | Bug Fix | Enhancement | ||
| John W. Lamb | 2014-01-30 20:36:09 UTC | CC | jolamb | |
| Chris Ryan | 2014-01-30 20:55:19 UTC | CC | cryan | |
| errata-xmlrpc | 2014-01-30 21:31:11 UTC | Status | MODIFIED | ON_QA |
| Peter Ruan | 2014-01-31 20:22:27 UTC | Status | ON_QA | VERIFIED |
| CC | pruan | |||
| Alex Dellapenta | 2014-02-18 19:46:24 UTC | CC | adellape | |
| Doc Text | Feature: The broker.conf ALLOW_ALIAS_IN_DOMAIN option is introduced; if true, the broker will allow aliases to be created that are in the cloud domain where apps are created, as long as they do not take the standard form of application names, that is, <word>-<word>.<cloud-domain> Reason: Previously (and still by default) this is disallowed in order to prevent confusion or possible name collisions, but some users wanted to be able to do this. Result (if any): When enabled, users who can create aliases can do so within the cloud domain. Only standard name collisions are prevented; no attempt is made to prevent collisions with HA app names. Such name collisions, should they occur on the same node host, could result in traffic being routed to the wrong gear on the node host. OpenShift still does not create a DNS entry for the alias; that is an external step. | By default, users were restricted from creating custom domain name aliases in the cloud domain of their applications to prevent confusion or possible name collisions. This enhancement adds a new ALLOW_ALIAS_IN_DOMAIN setting in the /etc/openshift/broker.conf file on the broker host that allows users to create aliases within the cloud domain. However, the alias must not be in the form <name>-<name>.<cloud-domain>. Aliases taking this standard form of application names are rejected to prevent conflicts. See the OpenShift Enterprise Administration Guide for more information. | ||
| errata-xmlrpc | 2014-02-21 11:02:58 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2014-02-25 15:41:34 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2014-02-25 10:41:34 UTC | |||
| Dan McPherson | 2017-03-08 17:36:08 UTC | Target Release | 2.0.3 |
Back to bug 1040257