Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deployment of ceph-mon failing due to incorrectly specified file modes

See original GitHub issue

Checked out ceph-ansible yesterday (08/02/2016) and am hitting the following error when deploying my MONs:

00:29:45 TASK: [ceph-mon | set initial monitor key permissions] ************************ 
00:29:45 failed: [jrpcaioiad-8_ceph_mon_container-67e07109] => {"details": "bad symbolic permission for mode: 384", "failed": true, "gid": 0, "group": "root", "mode": "0600", "owner": "root", "path": "/var/lib/ceph/tmp/keyring.mon.jrpcaioiad-8_ceph_mon_container-67e07109", "size": 77, "state": "file", "uid": 0}
00:29:45 msg: mode must be in octal or symbolic form
00:29:45 failed: [jrpcaioiad-8_ceph_mon_container-48ff43a8] => {"details": "bad symbolic permission for mode: 384", "failed": true, "gid": 0, "group": "root", "mode": "0600", "owner": "root", "path": "/var/lib/ceph/tmp/keyring.mon.jrpcaioiad-8_ceph_mon_container-48ff43a8", "size": 77, "state": "file", "uid": 0}
00:29:45 msg: mode must be in octal or symbolic form
00:29:45 failed: [jrpcaioiad-8_ceph_mon_container-1f848f0c] => {"details": "bad symbolic permission for mode: 384", "failed": true, "gid": 0, "group": "root", "mode": "0600", "owner": "root", "path": "/var/lib/ceph/tmp/keyring.mon.jrpcaioiad-8_ceph_mon_container-1f848f0c", "size": 77, "state": "file", "uid": 0}
00:29:45 msg: mode must be in octal or symbolic form
00:29:45 
00:29:45 FATAL: all hosts have already failed -- aborting

It looks like this is a result of https://github.com/ceph/ceph-ansible/commit/dcec63adc865df4eb1ad17553a5443a9050d4585 and we will need to change the integer modes to strings.

Issue Analytics

State:
Created 8 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

geerlingguycommented, Mar 20, 2016

I just wanted to leave a comment and mention I hit this same bug in 2.0.1 (maybe other versions too), but only if I defined an octal in a variable set that was passed into a task using with_items. If I set the octal as a string or raw for the mode parameter, everything worked fine.

Using @cobyrne09’s suggestion (quoting the octal) worked for me.

1reaction

lesebcommented, Mar 21, 2017

@poppyschmo not that I’m aware of.