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):
Steps to Reproduce:
1. deploy hosted-engine
It fails adding the engine-vm to the engine.
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.
It happens on each kind of storage
Adding the first storage domain is enough to solve it: when you add the first data domain the datacenter comes up and the engine-VM got shown.
Can u please take a look at this, I'm not sure if we can remove this CDA (change-id I2586b0026c85f053b6cd0aebeb555d760afc0937) right now, though it seems that the behavior currently blocks adding Hosted Engine
Moving to virt per the bug description indicating the problem is mainly with the HE and Storage Pool
After discussing with Roy and Omer, moving this to SLA since the fix will eventually be in the SLA side
Created attachment 1059026 [details]
engine's log file
engine's VM log file
*** This bug has been marked as a duplicate of bug 1242215 ***