** Description changed: - In a scenario where Ceph is encrypted and using Vault as the keymanager, - in a scenario where vault and ceph are both stopped, any OSDs on the - unit(s) affected will require a further reboot if they try to start - before vault is unsealed. + [Impact] + Various configuration option values that are read from environment variables are incorrectly parsed as strings rather than ints which means that for certain deployment use-cases, the timeouts for starting the ceph-osd volume units cannot be increased to accommodate dependencies starting first. + + [Test Case] + Deploy ceph with vault for key management + set a systemd override for ceph-volume@ + Environment=CEPH_VOLUME_SYSTEMD_TRIES=2000 + Seal vault units (by restarting the vault service) + Reboot ceph-osd machines - Environment override is ignored as its not correctly parsed. + + [Regression Potential] + Low - this fix has been accept upstream in later releases. + + + [Original Bug Report] + In a scenario where Ceph is encrypted and using Vault as the keymanager, in a scenario where vault and ceph are both stopped, any OSDs on the unit(s) affected will require a further reboot if they try to start before vault is unsealed.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804261 Title: Ceph OSD units requires reboot if they boot before vault (and if not unsealed with 150s) To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1804261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
