Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Prepare ocp with etcd2 installed, after swap etcd2 to etcd3, services restart failed.
Version-Release number of selected component (if applicable):
etcd-2.3.7-4.el7.x86_64
etcd3-3.0.3-1.el7.x86_64
How reproducible:
sometimes
Steps to Reproduce:
1. prepare a env with etcd2
2. [root@etcd ~]# yum swap etcd etcd3 -y
3. [root@etcd ~]# systemctl restart etcd
Actual results:
etcd service restart failed
[root@etcd ~]# journalctl -xe -u etcd
...
Jan 06 08:18:00 etcd.example.com etcd[124364]: database file (/var/lib/etcd/member/snap/db index 0) does not match with snapshot (index 1150115).
Jan 06 08:18:00 etcd.example.com systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE
Jan 06 08:18:00 etcd.example.com systemd[1]: Failed to start Etcd Server.
...
Expected results:
etcd service restart success
Additional info:
Is this bug caused by "yum swap" command? Will there be same issue if we migrate Etcd in future? For example: migrate etcd-2.x to etcd-3.0.15-x; migrate etcd3-3.0.14.x to etcd-3.0.15-x.