Bug 1390026

Summary: [ceph-iscsi-ansible] key directory missing on ansible controller when seeding gateways
Product: [Red Hat Storage] Red Hat Storage Console Reporter: Paul Cuzner <pcuzner>
Component: ceph-ansibleAssignee: Paul Cuzner <pcuzner>
Status: CLOSED ERRATA QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: urgent Docs Contact:
Priority: high    
Version: 2CC: adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, hnallurv, kdreyer, kurs, nthomas, sankarshan, tchandra
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-iscsi-ansible-1.5-1.el7cp ceph-iscsi-config-1.5-1.el7cp Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-22 23:42:35 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:

Description Paul Cuzner 2016-10-30 23:02:24 UTC 
Description of problem:
The ansible playbook is attempted to gather ceph.conf and client admin keyring from a designated monitor, to a specific folder on the ansible host machine. However, the target directory does not exist resulting in the failure of the playbook



Version-Release number of selected component (if applicable):
1.4 - 

How reproducible:
Always happens on a clean server deployment

Steps to Reproduce:
1. run the 1.4 ansible playbook on a clean rnvironment where /root/ceph-iscsi-cond dir does *not* exist
2.
3.

Actual results:
Task/playbook fails

Expected results:
Directory should be created ahead of the copy of the conf/keyring files

Additional info:
Comment 2 Paul Cuzner 2016-11-02 04:38:00 UTC 
please test against 1.5test release
Comment 3 Tejas 2016-11-02 09:24:25 UTC 
Verified in build:
ceph-iscsi-ansible-1.5-1.el7test.noarch
ceph-iscsi-config-1.5-1.el7test.noarch
Comment 7 errata-xmlrpc 2016-11-22 23:42:35 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:2817