Description of problem:

As for https://bugzilla.redhat.com/show_bug.cgi?id=1215623#c8
the engine now refuses to add the engine VM cause at that point there is no Acive Datacenter cause there is no no active storage domain (hosted-engine one is directly managed by hosted-engine and not by the engine itself).

In the engine logs we could found:
2015-05-04 18:23:10,994 WARN  [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (DefaultQuartzScheduler_Worker-85) [1c4d795d] CanDoAction of action 'AddVmFromScratch' failed for user null@N/A. Reasons: VAR__ACTION__ADD,VAR__TYPE__VM,ACTION_TYPE_FAILED_IMAGE_REPOSITORY_NOT_FOUND
2015-05-04 18:23:10,995 INFO  [org.ovirt.engine.core.bll.AddVmFromScratchCommand] (DefaultQuartzScheduler_Worker-85) [1c4d795d] Lock freed to object 'EngineLock [exclusiveLocks= key: HostedEngine value: VM_NAME
, sharedLocks= ]'

ACTION_TYPE_FAILED_IMAGE_REPOSITORY_NOT_FOUND was recently added, change-Id: I2586b0026c85f053b6cd0aebeb555d760afc0937


Version-Release number of selected component (if applicable):
3.6-master

How reproducible:
100%

Steps to Reproduce:
1. deploy hosted-engine
2.
3.

Actual results:
It fails adding the engine-vm to the engine.

Expected results:
Engine-vm got added into the engine either cause the hosted-engine storage domains was added to the engine as for https://bugzilla.redhat.com/show_bug.cgi?id=1215158 or cause ACTION_TYPE_FAILED_IMAGE_REPOSITORY_NOT_FOUND got ignored for the engine-vm.

Additional info:
It happens on each kind of storage