Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1688684 - Add pre checks in tendrl-ansible for directory permission
Summary: Add pre checks in tendrl-ansible for directory permission
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: web-admin-tendrl-ansible
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-14 08:37 UTC by gowtham
Modified: 2019-04-11 07:57 UTC (History)
4 users (show)

Fixed In Version: 3.4.5
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description gowtham 2019-03-14 08:37:45 UTC
Description of problem:
Tendrl components need permissions to read and write data in a few directories. Before import, tendrl-ansible should make sure all the below directories should have permission for the corresponding users to read and write the data.

1. /tmp - read and write and execute permission for root user
2. /va/lib/carbon - read and write permission for carbon user
3. /var/lib/graphite-web/graphite.db  - read and write permission for apache user
4. /var/log/graphite-web - read and write permission for apache user

Version-Release number of selected component (if applicable):
tendrl-commons-1.6.3-17.el7rhgs

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
RHWA fails when few repositories do not have permission

Expected results:
RHWA should have pre and post check for directory permission 

Additional info:

Comment 2 Martin Bukatovic 2019-03-14 13:50:51 UTC
This would require a separate playbook, it doesn't belong to prechecks, as these directories may not exists before installation, when the prechecks playbook is expected to be run.


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