Bug 1414262

Summary: Remove 'update-from-vip' from example in docs.
Product: Red Hat OpenStack Reporter: Harald Jensås <hjensas>
Component: documentationAssignee: Dan Macpherson <dmacpher>
Status: CLOSED DUPLICATE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: augol, lbopf, lmiccini, mburns, sathlang, srevivo
Target Milestone: asyncKeywords: Documentation, Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-30 17:04:22 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:

Description Harald Jensås 2017-01-18 08:12:39 UTC
Description of problem:
The inclusion of 'update-from-vip' is confusing in the doc example.

The 'update-from-vip' is only relevant when doing and update from OSP7.1 to 7.2 or greater.

Version-Release number of selected component (if applicable):

Actual results:
User read the documentation, and see an environment file with 'update' in its name and believe it is a requirement to include this during updates.

Because this is included, the update fails and leave the stack in "UPDATE_FAILED" state.

Expected results:
The OSP8 documentation should not have an example referencing an OSP7 specific environment file.

Additional info:

Comment 1 Amit Ugol 2017-03-08 10:16:46 UTC
@ Dan, Hi, do you need any info from eng. side?

Comment 3 Lucy Bopf 2017-05-26 06:47:03 UTC
Assigning to Martin for review.

Martin, looks like the update-from-vip environment file exists in docs for versions 8 and higher, and should be removed.

Comment 4 Sofer Athlan-Guyot 2017-05-30 10:52:34 UTC

this one https://bugzilla.redhat.com/show_bug.cgi?id=1454710 is for osp9 documentation.

Comment 5 Dan Macpherson 2017-05-30 17:04:22 UTC
I've updated this one as a part of BZ#1456897

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