It seems that the import of the storage domain failed since it was inaccessible:

2016-12-28 07:06:25,406 ERROR [org.ovirt.engine.core.bll.storage.domain.GetExistingStorageDomainListQuery] (org.ovirt.thread.pool-6-thread-46) [] Exception: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to HSMGetStorageDomainInfoVDS, error = Domain is either partially accessible or entirely inaccessible: (u'247b250c-ccd3-4056-853f-f03a05369da9',), code = 379 (Failed with error StorageDomainAccessError and code 379)
....
2016-12-28 07:06:25,413 ERROR [org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand] (org.ovirt.thread.pool-6-thread-46) [] Failed query for all Storage Domains. The import command can not proceed without this info

Once that happened the command was logged in the db as failed, and every engine restart the engine tries to run it again (compensate mechanism).
However, since the import storage domain command is not "compensatable" this fails and the domain remains locked.

2016-12-28 07:09:02,643 ERROR [org.ovirt.engine.core.bll.CommandsFactory] (ServerService Thread Pool -- 56) [] CommandsFactory : Failed to get type information using reflection for Class  'org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand', Command Id '2ab30734-bbe4-4f50-897f-f1b393a31852': org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand.<init>(org.ovirt.engine.core.compat.Guid)
2016-12-28 07:09:02,643 ERROR [org.ovirt.engine.core.bll.CommandsFactory] (ServerService Thread Pool -- 56) [] Exception: java.lang.NoSuchMethodException: org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand.<init>(org.ovirt.engine.core.compat.Guid)
....
2016-12-28 07:09:02,646 ERROR [org.ovirt.engine.core.bll.Backend] (ServerService Thread Pool -- 56) [] Failed to run compensation on startup for Command 'org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand', Command Id '2ab30734-bbe4-4f50-897f-f1b393a31852'


I would suggest:
1. Verify the you can access the storage domain.
2. If you can access the domain, you can try removing it from the ui (I think the destroy option should be available).
    After the removal the engine will try to reimport it, and hopefully will succeed.
    Removing the storage domain may cause the engine and the ha-agent to restart.

Jenny

    



On Wed, Dec 28, 2016 at 6:29 PM, Gary Pedretty <gary@ravnalaska.net> wrote:
Here is the engine log from the engine vm.

Gary




------------------------------------------------------------------------
Gary Pedretty                                        gary@ravnalaska.net
Systems Manager                                          www.flyravn.com
Ravn Alaska                           /\                    907-450-7251
5245 Airport Industrial Road         /  \/\             907-450-7238 fax
Fairbanks, Alaska  99709        /\  /    \ \ Second greatest commandment
Serving All of Alaska          /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39
------------------------------------------------------------------------












On Dec 28, 2016, at 1:12 AM, Evgenia Tokar <etokar@redhat.com> wrote:

Hi!

Can you attach the engine log from the hosted engine vm?

Thanks,
Jenny


On Wed, Dec 28, 2016 at 10:56 AM, Gary Pedretty <gary@ravnalaska.net> wrote:
Just setup a new hosted-engine Data Center.  With 3 hosts and gluster based storage domains.  Used the latest installers.  Everything went well, until I got the engine deployed and each host setup and went to the web interface for the first time.

After adding the master storage domain, the hosted_storage added itself like usual, but remained locked.   Everything is working just fine with the exception of no listing of the engine as a VM under that tab or the icon on the current host.   The Volumes tab does not show anything on the hosted_storage, but all the other volumes including the master data and a second data all show normal status for bricks.  Error log is not reporting anything unusual either.  All the gluster volumes including the engine (hosted_storage) show good status via command line in the hosts.

Going to let it run for a day or so before I add any VMs.

Any ideas?

Gary

------------------------------------------------------------------------
Gary Pedretty                                        gary@ravnalaska.net
Systems Manager                                          www.flyravn.com
Ravn Alaska                           /\                    907-450-7251
5245 Airport Industrial Road         /  \/\             907-450-7238 fax
Fairbanks, Alaska  99709        /\  /    \ \ Second greatest commandment
Serving All of Alaska          /  \/  /\  \ \/\   “Love your neighbor as
Really loving the record green up date! Summmer!!   yourself” Matt 22:39
------------------------------------------------------------------------













_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users