Bug 1054965 - deployment causes post to /broker/analytics
Summary: deployment causes post to /broker/analytics
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Brenton Leanhardt
QA Contact: libra bugs
URL:
Whiteboard:
Depends On: 1061400
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-17 20:31 UTC by Luke Meyer
Modified: 2014-02-04 18:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1061400 (view as bug list)
Environment:
Last Closed: 2014-02-04 18:52:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Luke Meyer 2014-01-17 20:31:00 UTC 
Description of problem:
When an app deployment occurs from a git push, it's recorded to the broker at /broker/analytics. This isn't apparently deployed with OSE, or at least not with default config. It returns a 500 error (probably because there's no route) which could mislead those looking at logs or packet traces. No other bad effect (not even a stack trace to fill production.log).


How reproducible:
Every time.

Steps to Reproduce:
1. Do an app deployment
2. Look in /var/log/httpd/access_log on the broker

Actual results:
/broker/analytics request with 500 status

Expected results:
No such request, or 2xx status
Note You need to log in before you can comment on or make changes to this bug.