Bug 1767943 - [Docs] For CAM CORS setup the restart command should be 'master-restart controllers' instead of 'master-restart controller'
Summary: [Docs] For CAM CORS setup the restart command should be 'master-restart contr...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.z
Assignee: Avital Pinnick
QA Contact: Xin jiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-01 17:14 UTC by John Matthews
Modified: 2019-11-06 12:06 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-06 12:06:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description John Matthews 2019-11-01 17:14:11 UTC
Description of problem:

"""
In OpenShift Container Platform 3.10 and 3.11, these components run in static Pods managed by a kubelet and are restarted by running the following commands:

$ /usr/local/bin/master-restart api
$ /usr/local/bin/master-restart controller
"""


Should be
"""
In OpenShift Container Platform 3.10 and 3.11, these components run in static Pods managed by a kubelet and are restarted by running the following commands:

$ /usr/local/bin/master-restart api
$ /usr/local/bin/master-restart controllers
"""



Note:
 when we run as 'controllers' we now see status of '2'
#  /usr/local/bin/master-restart controllers
2


opposed to prior 
#  /usr/local/bin/master-restart controller
Component controller is already stopped

Comment 2 Xin jiang 2019-11-04 02:40:25 UTC
Verified.


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