Bug 1455266

Summary: Deploying mon containers fail with: 'dict object' has no attribute u'mgrs'
Product: [Red Hat Storage] Red Hat Storage Console Reporter: Andrew Schoen <aschoen>
Component: ceph-ansibleAssignee: Sébastien Han <shan>
Status: CLOSED NOTABUG QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2CC: adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, gmeno, kdreyer, nthomas, racpatel, sankarshan, shan, tserlin
Target Milestone: ---   
Target Release: 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-ansible-2.2.7-1.el7scon Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-24 20:29:00 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 Andrew Schoen 2017-05-24 15:28:24 UTC
Description of problem:
Deploying containerized mons fail with:

TASK [ceph-mon : add mgr keys to config and keys paths] ************************
task path: /home/jenkins-build/build/workspace/ceph-docker-nightly-ceph_ansible2.2-jewel-centos7-cluster/ceph-ansible/roles/ceph-mon/tasks/docker/fetch_configs.yml:13
fatal: [mon0]: FAILED! => {
    "failed": true
}

MSG:

'dict object' has no attribute u'mgrs'

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

stable-2-2 branch of ceph-ansible


How reproducible:

always


Steps to Reproduce:
1. deploy a ceph cluster using containerized daemons
2. the first mon will fail because it tries to fetch nonexistent ceph-mgr keys 

Actual results:

containerized mon deployment fails


Expected results:

containerized mon deployment succeeds


Additional info:

This has been reproduced consistently with our upstream ceph-docker nightly tests. For example: https://jenkins.ceph.com/view/ceph-docker/job/ceph-docker-nightly-ceph_ansible2.2-jewel-centos7-cluster/9/console

Comment 3 Andrew Schoen 2017-05-24 15:30:17 UTC
upstream PR https://github.com/ceph/ceph-ansible/pull/1567

Comment 6 Andrew Schoen 2017-05-24 15:52:58 UTC
upstream PR merged to stable-2.2

Comment 12 Andrew Schoen 2017-05-24 20:29:00 UTC
I've realized that this only occurs with our nightly ceph-docker tests and not with ceph-ansible PR testing, QE also did not see this bug in testing. The difference is that our ceph-docker nightly tests were testing with ansible==2.2.0 which exposes this bug. Changing that ansible version to 2.2.3 avoids the issue I've reported here.

The change that https://github.com/ceph/ceph-ansible/pull/1567 brought in should not affect any functionality when using ansible 2.2.3.

My PR to update the ansible version used by ceph-docker tests is here: https://github.com/ceph/ceph-docker/pull/653

Closing this as NOTABUG