On Thu, Mar 28, 2019 at 08:59:21AM +0000, Gianni Milo wrote: > Assuming that the linstor-controller VM resides in a resource named > vm-100-disk-1 , should the following resolve this issue... > > $ systemctl edit linstor-satellite > > Add the following content... > > [Unit] > After=drbd.service > > [Service] > Type=simple > ExecStart=/usr/share/linstor-server/bin/Satellite > --logs=/var/log/linstor-satellite --config-directory=/etc/linstor --keep-res > vm-100-disk-1
LGTM. Obviously, you also need to restart the service. > In the documentation it is stated that drbd.service must be enabled as > well to prevent deleting (and bringing up) the controller VM resource > file. Yes and no. It does not prevent deleting. "Sombody" has to bring up the DRBD resource the controller VM is on. Then Proxmox is able to start the controller VM. This "someone" can and should be the drbd.service. Best, rck _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
