[DRBD-user] linstor-proxmox: Intentionally removing diskless assignment

[Roland Kammerer]

On Wed, Dec 18, 2019 at 12:19:45PM +0100, Andreas Pflug wrote:
> Could not delete diskless resource vm-105-disk-3 on <migrationSource>,
> because:
> [{ "ret_code":53739522,
>    "message":"Node: <migrationSource>, Resource: vm-105-disk-3 marked
> for deletion.",
>    "details":"Node: <migrationSource>, Resource: vm-105-disk-3 UUID is:
> <uuid>",
>    "obj_refs":{"RscDfn":"vm-105-disk-3","Node":"<migrationSource>"}
>  },
>  { "ret_code":53739523,
>    "message":"Deleted 'vm-105-disk-3' on '<migrationSource>'",
>    "obj_refs":{"RscDfn":"vm-105-disk-3","Node":"<migrationSource>"}
>  },
>  { "ret_code":53739523,
>    "message":"Notified '<storageHost2>' that 'vm-105-disk-3' is being
> deleted on Node(s): [<migrationSource>]",
>    "obj_refs":{"RscDfn":"vm-105-disk-3","Node":"<migrationSource>"}
>  },
>  { "ret_code":-4611686018373647386,
>    "message":"(Node: '<migrationTarget>') Failed to adjust DRBD resource
> vm-105-disk-3","error_report_ids":["<reportid>"],

Here obviously the error report would be interesting:
linstor err s <ID>.

As well as everything one would do to diagnose a DRBD problem, like
'drbdsetup status vm-105-disk-3', syslogs/journal grepepd for the
resource,...

Regards, rck