manager: don't proceed with activation when there's no master device

manager: don't proceed with activation when there's no master device

Since the device-for-all merge it's a sin (trips an assert) to create an
activation request with NULL device.

If we get here, it's probably that the master device exists, but is not ready
for activation (it's in UNMANAGED state in the process of being created).