Bug 1357820

Summary: Need add profiling flags to /etc/etcd/etcd.conf in etcd-2.3.7
Product: Red Hat Enterprise Linux 7 Reporter: Joy Pu <ypu>
Component: etcdAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 7.2Keywords: Extras
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: etcd-2.3.7-4.el7 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-15 08:30:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Joy Pu 2016-07-19 09:56:04 UTC
Description of problem:

New added flags for profiling is not added to the etcd.conf file.
Here is the flags from etcd --help:

profiling flags:
	--enable-pprof 'false'
		Enable runtime profiling data via HTTP server. Address is at client URL + "/debug/pprof"

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

How reproducible:

Steps to Reproduce:
1. Get etcd --help
$ etcd --help
2. Compare the flags with the flags we get from etcd.conf

Actual results:
one new added flag missing

Expected results:
The flag should be added

Additional info:

Comment 2 Jan Chaloupka 2016-07-19 10:56:58 UTC
This does not affect AH 7.2.6. The flags that are commented out in the etcd.config file does not take any effect. At the same time, they are set in the file so an etcd operator is aware of them and does not have to read the etcd documentation. For additional information about available options/flags and their meaning, it is always necessary to read the documentation and update the etcd.conf accordingly.

Thus, I will update the etcd.conf only without rebuilding.

Comment 5 Joy Pu 2016-08-26 07:38:32 UTC
Checked in the etcd-2.3.7-4.el7, the flag is added:


So set this to verified.

Comment 7 errata-xmlrpc 2016-09-15 08:30:28 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.