Bug 1440303 - [3.2] The etcd db file should be backed during upgrade
Summary: [3.2] The etcd db file should be backed during upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.2.1
Assignee: Scott Dodson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1433272
Blocks: 1440296 1440299
TreeView+ depends on / blocked
 
Reported: 2017-04-07 20:20 UTC by Scott Dodson
Modified: 2017-06-29 13:33 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If etcd 3.x or later were running on the host a v3 snapshot db must be backed up as part of the backup process. If this directory is not included in the backup then etcd will fail to restore the backup even though v3 data was not used. The etcd backup steps have been amended to ensure that the v3 snapshot database is included in our backups.
Clone Of: 1433272
Environment:
Last Closed: 2017-06-29 13:33:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1666 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-06-29 17:32:39 UTC

Comment 1 Scott Dodson 2017-06-02 19:34:30 UTC 
https://github.com/openshift/openshift-ansible/pull/4361
Comment 3 Anping Li 2017-06-12 03:26:08 UTC 
No packages can be found, could you build a puddle?
Comment 4 Scott Dodson 2017-06-12 13:25:19 UTC 
puddle rebuilt
Comment 5 Anping Li 2017-06-14 05:49:44 UTC 
The db was backed by atomic-openshift-utils-3.2.57
[root@etcd-single snap]# ls /var/lib/origin/etcd-backup-20170614052025/member/snap
0000000000000002-0000000000002711.snap  db
Comment 7 errata-xmlrpc 2017-06-29 13:33:14 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-2017:1666
Note You need to log in before you can comment on or make changes to this bug.