Bug 1607970 - create an empty rados index object expects client.admin
Summary: create an empty rados index object expects client.admin
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 3.1
Assignee: Giulio Fidente
QA Contact: subhash
URL:
Whiteboard:
Depends On:
Blocks: 1578730
TreeView+ depends on / blocked
 
Reported: 2018-07-24 16:00 UTC by Giulio Fidente
Modified: 2018-09-26 18:24 UTC (History)
12 users (show)

Fixed In Version: RHEL: ceph-ansible-3.1.0-0.1.rc12.el7cp Ubuntu: ceph-ansible_3.1.0~rc12-2redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-26 18:23:43 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 2928 0 None closed Run creation of empty rados index object to first monitor 2020-06-05 17:40:51 UTC
Github ceph ceph-ansible pull 2933 0 None closed Automatic backport of pull request #2928 2020-06-05 17:40:51 UTC
Red Hat Product Errata RHBA-2018:2819 0 None None None 2018-09-26 18:24:33 UTC

Description Giulio Fidente 2018-07-24 16:00:41 UTC 
create empty rados index from ceph-nfs role fails when distributed as it assumes availability of client.admin locally

this is using ceph-ansible-3.1.0-0.1.rc9

1. https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-nfs/tasks/start_nfs.yml#L11
Comment 5 Ken Dreyer (Red Hat) 2018-07-25 22:31:05 UTC 
The fix is in the upstream stable-3.1 branch, so this fix will be in the next upstream tag after v3.1.0rc10.
Comment 10 subhash 2018-08-14 15:43:03 UTC 
Following the steps from Comment 8 ,
Deployed a ceph 3.1 cluster with nfs role on a dedicated node,it worked fine,Moving to to verified state.
version: ceph-ansible 3.1.0-0.1.rc17.el7cp,ceph 12.2.5-39.el7cp.x86_64
Comment 13 errata-xmlrpc 2018-09-26 18:23:43 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-2018:2819
Note You need to log in before you can comment on or make changes to this bug.