Bug 1390026 - [ceph-iscsi-ansible] key directory missing on ansible controller when seeding gateways
Summary: [ceph-iscsi-ansible] key directory missing on ansible controller when seeding...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: ceph-ansible
Version: 2
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: 2
Assignee: Paul Cuzner
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-30 23:02 UTC by Paul Cuzner
Modified: 2016-11-22 23:42 UTC (History)
11 users (show)

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:
Clone Of:
Environment:
Last Closed: 2016-11-22 23:42:35 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2817 0 normal SHIPPED_LIVE ceph-iscsi-ansible and ceph-ansible bug fix update 2017-04-18 19:50:43 UTC

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


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