Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1609574

Summary: [DOCS] etcdctl2 commands to be removed from the latest documentation of v3.9
Product: OpenShift Container Platform Reporter: Jatan Malde <jmalde>
Component: DocumentationAssignee: Kathryn Alexander <kalexand>
Status: CLOSED DUPLICATE QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-09 17:39:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of the error none

Description Jatan Malde 2018-07-29 17:00:58 UTC 
Created attachment 1471373 [details]
screenshot of the error

Document URL:

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.9/html-single/day_two_operations_guide/#restoring-etcd_deprecating-etcd

Section Number and Name: 

4.6.1.2. Backing up etcd data

Describe the issue: 

For a reference of v3 data model the command contains the etcdctl2 command on it.

Suggestions for improvement: 

For the reference of v3 data model the v3 etcdctl3 command should be listed on it.
Check the attachment in the bugzilla for the exact point where the error is listed.

Additional information:
Comment 1 Vikram Goyal 2018-08-09 04:40:55 UTC 
@Kathryn - not sure if this requires QE. Will leave it up to you to decide.
Comment 2 Kathryn Alexander 2018-08-09 17:39:38 UTC 
If you upgraded from a version before 3.6, you do need to update both datastores.

My contact in engineering thought that it would be better to make people run an "extra" command than to risk someone not thinking it was necessary and risk losing the old schema.

We recently updated the docs to add a note to clarify this: "Because clusters upgraded from previous versions of {product-title} might contain v2 data stores, back up both v2 and v3 datastores."

*** This bug has been marked as a duplicate of bug 1603122 ***