Bug 1746686 - telemeter client config reloader uses wrong port
Summary: telemeter client config reloader uses wrong port
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.2.0
Assignee: Sergiusz Urbaniak
QA Contact: Viacheslav
URL:
Whiteboard:
Depends On:
Blocks: 1746711
TreeView+ depends on / blocked
 
Reported: 2019-08-29 06:25 UTC by Sergiusz Urbaniak
Modified: 2019-10-16 06:40 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1746711 (view as bug list)
Environment:
Last Closed: 2019-10-16 06:38:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 459 0 'None' 'closed' 'Bug 1746686: jsonnet/telemeter: fix client reload port ' 2019-11-25 14:56:37 UTC
Github openshift telemeter pull 229 0 'None' 'closed' 'Bug 1746686: jsonnet: fix client reload port' 2019-11-25 14:56:37 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:40:24 UTC

Comment 6 Viacheslav 2019-09-04 09:19:53 UTC 
Fixed 

$ oc -n openshift-monitoring get pod | grep telemeter
$ oc -n openshift-monitoring rsh -c reload telemeter-client-8b96c457-5cvgn curl -XPOST -v
$ oc -n openshift-monitoring get deployment telemeter-client -o yaml | grep -e 'webhook.*reload'
>> http://localhost:8080/-/reload

on 4.2.0-0.nightly-2019-09-02-172410
Comment 7 errata-xmlrpc 2019-10-16 06:38:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.