mirror of https://github.com/ceph/ceph-ansible.git
e537779bb3
This commit fixes a bug that occurs especially for dmcrypt scenarios. There is an issue where the 'disk_list' container can't reach the ceph cluster because it's not launched with `--net=host`. If this container can't reach the cluster, it will hang on this step (when trying to retrieve the dm-crypt key) : ``` +common_functions.sh:448: open_encrypted_part(): ceph --cluster abc12 --name \ client.osd-lockbox.9138767f-7445-49e0-baad-35e19adca8bb --keyring \ /var/lib/ceph/osd-lockbox/9138767f-7445-49e0-baad-35e19adca8bb/keyring \ config-key get dm-crypt/osd/9138767f-7445-49e0-baad-35e19adca8bb/luks +common_functions.sh:452: open_encrypted_part(): base64 -d +common_functions.sh:452: open_encrypted_part(): cryptsetup --key-file \ -luksOpen /dev/sdb1 9138767f-7445-49e0-baad-35e19adca8bb ``` It means the `ceph-run-osd.sh` script won't be able to start the `osd_disk_activate` process in ceph-container because he won't have filled the `$DOCKER_ENV` environment variable properly. Adding `--net=host` to the 'disk_list' container fixes this issue. Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1543284 Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com> |
||
---|---|---|
.. | ||
ceph-osd-run.sh.j2 | ||
ceph-osd.service.d-overrides.j2 | ||
ceph-osd.service.j2 | ||
osd.conf.j2 |