Bug 1626917

Summary:	Link provided to upgrade already existing heketi server is incorrect
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	doc-Container_Native_Storage_with_OpenShift	Assignee:	Bhavana <bmohanra>
Status:	CLOSED CURRENTRELEASE	QA Contact:	storage-qa-internal <storage-qa-internal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	cns-3.10	CC:	asriram, bmohanra, rhs-bugs, sankarshan, storage-doc
Target Milestone:	---	Keywords:	Reopened, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-21 13:33:30 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:
Bug Depends On:
Bug Blocks:	1672844

Description RamaKasturi 2018-09-10 05:59:44 UTC

Document URL: https://access.qa.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.10/html-single/deployment_guide/index#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-log_met

Section Number and Name: 4.7. Creating an Arbiter Volume (optional)

Describe the issue: I see that link provided to upgrade an already existing heketi server is incorrect as it talks about "Creating Arbitrated Replicated volumes"

Suggestions for improvement: Please provide the correct link which talks about upgrading heketi server.

Additional information:

Comment 2 RamaKasturi 2018-09-10 09:09:57 UTC

Issue mentioned in description  needs to be corrected in 5.6 section as well.

Comment 3 RamaKasturi 2019-02-20 09:15:04 UTC

I see that this doc change is already available in the latest documents can we close this bug ?

Comment 4 RamaKasturi 2019-02-20 09:15:47 UTC

Accidentally updated the bug status changing it back to NEW

Comment 5 Anjana Suparna Sriram 2019-02-21 13:33:30 UTC

Closing this bug based on Comment 4.