Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1747156

Summary: It appears to be enabled by default and setting enable_telemetry = false doesn't appear to disable telemetry at
Product: Red Hat OpenStack Reporter: Alex Schultz <aschultz>
Component: instack-undercloudAssignee: James Slagle <jslagle>
Status: CLOSED ERRATA QA Contact: Arik Chernetsky <achernet>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: achernet, ddf-bot, dhill, emacchi, mburns, mmagr, msecaur, rhos-docs, vkapalav
Target Milestone: ---Keywords: TestOnly, Triaged, ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: instack-undercloud-8.4.7-13.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1736786 Environment:
Last Closed: 2020-03-10 11:18:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1736782, 1736786    
Bug Blocks:    

Description Alex Schultz 2019-08-29 18:58:58 UTC 
+++ This bug was initially created as a clone of Bug #1736786 +++

enable_telemetry appears to be enabled by default and setting enable_telemetry = false doesn't appear to disable telemetry at all ... I've setted it to enable_telemetry = false , set the messaging driver to noop and re-ran undercloud install ... it reverted the driver to messaging !
Comment 1 Lon Hohberger 2019-11-08 11:46:51 UTC 
According to our records, this should be resolved by instack-undercloud-8.4.9-1.el7ost.  This build is available now.
Comment 3 errata-xmlrpc 2020-03-10 11:18:32 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-2020:0760