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

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1687930

Summary:

[DOC] RHCS Container installation guide should use 'sudo' instead of using 'root' user

Product:

[Red Hat Storage] Red Hat Ceph Storage

Reporter:

Karun Josy <kjosy>

Component:

Documentation

Assignee:

John Brier <jbrier>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Uday kurundwade <ukurundw>

Severity:

medium

Docs Contact:

Priority:

unspecified

Version:

3.2

CC:

asriram, ceph-qe-bugs, edonnell, jbrier, kdreyer, kjosy, ukurundw, vereddy

Target Milestone:

Target Release:

3.2

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-08-26 06:55:41 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:

1685931

Attachments:

Description	Flags
section 1.6 using root commands	none

Description Karun Josy 2019-03-12 16:40:31 UTC

Description of problem:


RHCS Container guide [1] switches between ‘admin’ and ‘root’ user very frequently without mentioning it in the installation procedure. 
It would be better if we use 'sudo' in commands instead of using 'root' user (preferably) or we should either mention explicitly before changing user.

[1] https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html-single/container_guide/

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

Comment 1 John Brier 2019-03-29 20:25:02 UTC

Thanks for the report Karun.

I see what you mean. I went through only a third of the guide but found numerous steps where one is root and the following one requires the admin user or vice versa. [1]

My plan is to mention the user to run the command when it changes from previous step but not convert the guide to using sudo instead of root. Personally, when I install Ceph, on the admin node I just open two terminals, one logged in as root and one logged in as the admin user. It works fine for me. I definitely see the argument for using sudo instead but I want to maintain consistency with the rest of the guides and we don't use sudo for any of them AFAIK. Maybe in the future we can do that.


1)
firewall section needs to mention to use root user for all commands.


1.4. Installing the Ceph Object Gateway in a Container
Use[run] the following commands [as the ansible user] from the Ansible administration node. 


[as root] Create a new copy of the rgws.yml.sample file located in the group_vars directory. 


[as the ansible user] Run the ceph-ansible playbook. 

[as root] Verify that the Ceph Object Gateway pools were created properly: 


1.5. Installing Metadata Servers

[as root] Navigate to the /usr/share/ceph-ansible directory: 

[as the ansible user] Run the Ansible playbook: 

1.6. Installing the Ceph iSCSI gateway in a container

step 1 demonstrates cd-ing to /usr/share/ceph-ansible directory as admin user but step 2 requires root privs and doesn't mention it. step 3 command is shown as admin user

step 9 [as the admin user] Run the Ansible playbook


1.6.1. Configuring the Ceph iSCSI gateway in a container

[as root] Start the iSCSI gateway command-line interface: 

Creating (sic) [Create] the iSCSI gateways using either IPv4 or IPv6 addresses: 

Adding (sic) [Add] a RADOS Block Device (RBD): 

Creating (sic) [Create] a client: 

Adding (sic) disks to a clien

1.6.2. Removing the Ceph iSCSI gateway in a container

need to review rest of the guide beyond 1.6.2

Comment 6 John Brier 2019-04-12 14:09:56 UTC

Created attachment 1554804 [details]
section 1.6 using root commands