Bug 1049565 - Gear ID is not available in routing events
Summary: Gear ID is not available in routing events
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks: 1049566
TreeView+ depends on / blocked
 
Reported: 2014-01-07 19:02 UTC by Clayton Coleman
Modified: 2015-05-15 02:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1049566 (view as bug list)
Environment:
Last Closed: 2014-01-30 00:47:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Clayton Coleman 2014-01-07 19:02:23 UTC 
Routing SPI events do not contain the gear id.  This means that a consumer can't construct gear DNS entries (<gear_id>-<domain>.<domain_suffix>) nor associate an endpoint with gear ids.

This is a critical issue for at least one customer and should be targeted for OSE 2.0.2
Comment 1 Clayton Coleman 2014-01-07 19:02:57 UTC 
Fixed in https://github.com/openshift/origin-server/pull/4419
Comment 2 Mrunal Patel 2014-01-08 16:58:24 UTC 
https://github.com/openshift/origin-server/pull/4428 has been merged.
Comment 3 Peter Ruan 2014-01-09 00:31:33 UTC 
Verified with latest devenv

:action: :add_gear
:app_name: app2
:namespace: spiroute
:gear_id: 52cde521eab1408e8f000001
:public_port_name: haproxy-1.4
:public_address: 54.205.169.193
:public_port: 38042
:protocols:
- http
- ws
:types:
- load_balancer
:mappings:
- frontend: ''
  backend: ''
- frontend: /health
  backend: /configuration/health
:deprecated: use add_public_endpoint
Note You need to log in before you can comment on or make changes to this bug.