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 1386963 - etcd2 -> etcd3 migration utility fails against OpenShift 3.4 configuration data
Summary: etcd2 -> etcd3 migration utility fails against OpenShift 3.4 configuration data
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: etcd3
Version: 7.2
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 7.3
Assignee: Jan Chaloupka
QA Contact: Martin Jenner
Depends On:
TreeView+ depends on / blocked
Reported: 2016-10-19 23:31 UTC by Mike Fiedler
Modified: 2016-12-06 17:43 UTC (History)
10 users (show)

Fixed In Version: etcd3-3.0.14-3.el7
Doc Type: If docs needed, set a value
Doc Text:
This enhancement update fixes migration utility that was failing when migrating from v2 to v3
Clone Of:
Last Closed: 2016-12-06 17:43:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2890 0 normal SHIPPED_LIVE etcd3 bug fix update 2016-12-06 22:40:58 UTC

Description Mike Fiedler 2016-10-19 23:31:49 UTC
Description of problem:

The migration of OpenShift data from etcd2 -> etcd3 currently fails while running the etcdctl migrate tool.   It errors out immediately whether a custom transformer or the default one is used.

The error (with some extra debugging in the custom transformer used) is:

ERROR CODING NODE 0 {Key: , CreatedIndex: 0, ModifiedIndex: 0, TTL: 0}
Reader(0)[write /dev/stdin: bad file descriptor] = 
Err: write /dev/stdin: bad file descriptor
Error:  exit status 1
failed to transform keys

Version-Release number of selected component (if applicable): and etcd 2.3.7 -> etcd3 3.0.12

How reproducible:  always (at least on the OCP 3.4 data sets we have tried)

Steps to Reproduce:
1.   Install OCP with a separate etcd 2.3.7 
2.   Create some projects, pods, etc.   General OCP data
3.   Backup the etcd environment
4.   yum swap etcd etcd3 and verify the OCP env is still operational running etcd3 in etcd2 mode
5.   etcdctl --endpoints $endpoints migrate --data-dir=/var/lib/etcd

Actual results:  Error message (as above)

Expected results:

Successful migration

Comment 3 Timothy St. Clair 2016-10-20 14:19:07 UTC
fix is here: https://github.com/coreos/etcd/pull/6690, we'll need to update our etcdctl binaries.  

Hold off on final update until we've had a bit more time to validate.

Comment 5 Mike Fiedler 2016-10-20 20:47:51 UTC
Changing sev to high since it blocks migration.

Comment 6 Jan Chaloupka 2016-10-21 11:53:54 UTC
Merged upstream, updating rpm.

Comment 8 Joy Pu 2016-11-15 05:45:03 UTC
Hi Mike,

Can you help to provide some data for etcd for testing this? Seems I can not find OCP 3.4 env for testing it. And I try to reproduce it with some key value with '%' such as "test%" and "%", then migrate datedir from etcd-2.3.7-4 to etcd3-3.0.12-3, also borrow a openshift 3.3 env to test it. But it won't trigger the problem.

Comment 12 Joy Pu 2016-11-15 23:21:08 UTC
It's OK. :) Will following the new bug for the migration problem. And thanks for providing the information.

Comment 14 errata-xmlrpc 2016-12-06 17:43:17 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.