Comment 6 for bug 1840347

Another thing I'm not sure about how it should react this way but worth to explore:

     77 override_dh_installinit:
    ....
    131 # Ensure Debian/Ubuntu specific systemd units are NOT automatically enabled and started
    132 # Enable systemd targets only
    133 dh_systemd_enable -Xceph-mon.service -Xceph-osd.service -X ceph-mds.service
    134 # Start systemd targets only
    135 dh_systemd_start --no-restart-on-upgrade -Xceph-mon.service -Xceph-osd.service -X ceph-mds.service
    136
    137 override_dh_systemd_enable:
    138 # systemd enable done as part of dh_installinit
    139
    140 override_dh_systemd_start:
    141 # systemd start done as part of dh_installinit

Documentation:
Note that dh_systemd_start should be run after dh_installinit so that it can detect
corresponding SysV init scripts. The default sequence in dh does the right thing, this
note is only relevant when you are calling dh_systemd_start manually.

I would first try with the following to place the dh_systemd_[enable|start] execution where it should belong.

     77 override_dh_installinit:
    ....
- 131 # Ensure Debian/Ubuntu specific systemd units are NOT automatically enabled and started
- 132 # Enable systemd targets only
- 133 dh_systemd_enable -Xceph-mon.service -Xceph-osd.service -X ceph-mds.service
- 134 # Start systemd targets only
- 135 dh_systemd_start --no-restart-on-upgrade
    136
    137 override_dh_systemd_enable:
+ # Ensure Debian/Ubuntu specific systemd units are NOT automatically enabled and started
- 138 # systemd enable done as part of dh_installinit
+ 138 dh_systemd_enable -Xceph-mon.service -Xceph-osd.service -X ceph-mds.service
    139
    140 override_dh_systemd_start:
+ # Enable systemd targets only
- 141 # systemd start done as part of dh_installinit
+ 141 dh_systemd_start --no-restart-on-upgrade

That's what I would do first and give that a try.

- Eric