RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1282393 - Wrong options name ETCD_SNAPSHOT_COUNTER in /etc/etcd/etcd.conf
Summary: Wrong options name ETCD_SNAPSHOT_COUNTER in /etc/etcd/etcd.conf
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: etcd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Jan Chaloupka
QA Contact: atomic-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2015-11-16 09:59 UTC by Joy Pu
Modified: 2016-02-16 16:40 UTC (History)
0 users

Fixed In Version: etcd-2.1.1-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-02-16 16:40:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0231 0 normal SHIPPED_LIVE etcd bug fix and enhancement update 2016-02-16 21:39:11 UTC

Description Joy Pu 2015-11-16 09:59:36 UTC
Description of problem:

Version-Release number of selected component (if applicable):
etcd.x86_64 0:2.1.1-3.el7

How reproducible:

Steps to Reproduce:
1. Copy the line of ETCD_SNAPSHOT_COUNTER and remove the '#'
2. Set the value to 10 and restart etcd service
3. Check /var/lib/etcd/default.etcd/member/snap/ directory for the file name
4. Two nearby files name should fit b minus a is 10(as set in step 2).
5. After change it to ETCD_SNAPSHOT_COUNT it can work as expect.

Actual results:
The snap files is not generated every 10 times.

Expected results:
The snap files is separated every 10 times.

Additional info:

Comment 4 Joy Pu 2016-01-11 13:24:43 UTC
Checked with following steps and seems it is fixed in etcd-2.2.2-5.el7
1. check the etcd.conf file
# cat /etc/etcd/etcd.conf |grep COUNT

2. test with the reproduce steps and it works as expect.
1) set ETCD_SNAPSHOT_COUNTER to 10 in etcd.conf
2) restart etcd service
3) check etcd service status with -l
Jan 11 16:24:03 dhcp-73-2-65.eng.pek2.redhat.com etcd[5513]: start to snapshot (applied: 1215132, lastsnap: 1215121)
Jan 11 16:24:03 dhcp-73-2-65.eng.pek2.redhat.com etcd[5513]: saved snapshot at index 1215132
Jan 11 16:24:09 dhcp-73-2-65.eng.pek2.redhat.com etcd[5513]: start to snapshot (applied: 1215143, lastsnap: 1215132)
Jan 11 16:24:09 dhcp-73-2-65.eng.pek2.redhat.com etcd[5513]: saved snapshot at index 1215143

So update this one to VERIFIED

Comment 6 errata-xmlrpc 2016-02-16 16:40:15 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.


Note You need to log in before you can comment on or make changes to this bug.