Bug 1384540

Summary:	[DOCS] Creating the Highly Available Router creates the service account rather than needing it to exist already
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Documentation	Assignee:	Gaurav Nelson <gnelson>
Status:	CLOSED CURRENTRELEASE	QA Contact:	zhaozhanqi <zzhao>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	medium
Version:	3.3.0	CC:	aos-bugs, erjones, jokerman, mmccomas
Target Milestone:	---	Keywords:	Unconfirmed
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:	2018-07-12 23:43:52 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 Eric Jones 2016-10-13 13:47:05 UTC

Document URL: 
https://docs.openshift.com/container-platform/3.3/admin_guide/high_availability.html#configuring-a-highly-available-routing-service

Section Number and Name: 
Cluster Administration
High Availability
Configuring a Highly-available Routing Service

Describe the issue: 
The steps to create the Highly Available Router includes a step to create the service account(step 3/4), but when you run the command to deploy the HA router (step 6) the service account is created here as well. In fact, if the service account already exists when you run the command to deploy the HA router, you receive error messages indicating it already exists and the deployment returns a non-zero exit code and "fails" even though it actually deploys the pods.

Suggestions for improvement: 
Remove the steps for creating the service account

Comment 1 Gaurav Nelson 2018-06-11 03:04:41 UTC

Thanks Eric,

Will you be able to check if this is still and issue for OpenShift versions as well?

meanwhile I am making updates to the 3.3 branch docs.

Comment 2 Gaurav Nelson 2018-06-11 03:08:11 UTC

Tracking 3.3 docs changes in PR https://github.com/openshift/openshift-docs/pull/9972

Comment 5 Gaurav Nelson 2018-06-17 23:44:47 UTC

Thanks @zhaozhanqi for reviewing the PR. I have fixed it as per your comment.

@Eric can you please check the changes?

Comment 7 Gaurav Nelson 2018-06-25 01:48:50 UTC

@zhaozhanqi I did not get any response form the reporter. I am putting this up for QE. Please verify the PR https://github.com/openshift/openshift-docs/pull/9972 

If I get a go ahead, I can merge this one.

Comment 8 zhaozhanqi 2018-07-06 07:48:18 UTC

this LGTM, verified this bug.

Comment 9 Gaurav Nelson 2018-07-12 23:43:52 UTC

The incorrect section is removed from https://docs.openshift.com/container-platform/3.3/admin_guide/high_availability.html#configuring-a-highly-available-routing-service