Bug 1027220 - Public mappings are created using UUID and not the application name
Summary: Public mappings are created using UUID and not the application name
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Michal Fojtik
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 11:46 UTC by Michal Fojtik
Modified: 2015-05-14 23:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-11 15:08:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michal Fojtik 2013-11-06 11:46:00 UTC
Description of problem:

When you add cartridge that adds a public HTTP mapping, the result mapping is:

527a2922f3f3dd1c66000001-mfojtik.dev.rhcloud.com/haproxy_monitor 127.1.244.129:8080/

instead of:

ruby01-mfojtik.dev.rhcloud.com/haproxy_monitor 127.1.244.129:8080/

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

devenv, maybe PROD/INT?

Steps to Reproduce:

1. rhc app create ruby01 -s ruby-1.9
2. rhc add-cartridge https://raw.github.com/mfojtik/openshift-origin-cartridge-hamonitor/master/metadata/manifest.yml -a ruby01

Now check the /etc/httpd/conf.d/openshift/nodes.txt files, you will see something like:

ruby01-mfojtik.dev.rhcloud.com 127.1.244.2:8080
ruby01-mfojtik.dev.rhcloud.com/health HEALTH
ruby01-mfojtik.dev.rhcloud.com/haproxy-status 127.1.244.3:8080/
527a2922f3f3dd1c66000001-mfojtik.dev.rhcloud.com/haproxy_monitor 127.1.244.129:8080/

Expected results:

The public mapping DNS should use the application name instead of application UUID.

Comment 1 Michal Fojtik 2013-11-06 15:23:36 UTC
I work this out, adding the Group-Overrides and Provides into manifest.yml:

Group-Overrides:
- components:
  - web_framework
  - hamonitor

The mappings are now created correctly and the cartridge is installed into primary gear in scaled app.

I think we should document this behavior, so I will keep this bug open until I update the docs.


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