Bug 1399109 - adjust backup file name in etcd-backup-post
Summary: adjust backup file name in etcd-backup-post
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 10:03 UTC by Anping Li
Modified: 2017-08-25 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-25 15:51:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Anping Li 2016-11-28 10:03:39 UTC 
Description of problem:
The backup file named etcd-backup-post-3.0-20161128162131.  if there isn't etcd3 packages, the upgrade_etcd.yml still generate post backup file named with 3.0. The backup post can be skipped for embedded etcds. The backup post should be generated backup named without 3.0 if the last packages isn't etcd3. 



Version-Release number of selected component (if applicable):
openshift-ansible-3.4.29-1.git.0.cdb211b.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install ocp 3.1 with embedded etcd
2. run playbook  upgrade_etcd.yml 
3. check the backup file names 

Actual results:
[root@openshift-221 origin]# ls -1
etcd-backup-post-3.0-20161128162131
etcd-backup-pre-upgrade-20161128162109
openshift.local.volumes

Expected results:


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