Re: [ovirt-users] Hosted engine already imported
On Apr 27, 2017, at 12:12 AM, Simone Tiraboschi
<stirabos(a)redhat.com> wrote:
On Tue, Apr 25, 2017 at 7:53 PM, Jamie Lawrence <jlawrence(a)squaretrade.com> wrote:
Hi all,
In my hopefully-near-complete quest to automate Ovirt configuration in our environment,
I’m very close. One outstanding issue that remains is that, even though the hosted engine
storage domain actually was imported and shows in the GUI, some part of Ovirt appears to
think that hasn’t happened yet.
Did the engine imported it automatically once you had your first regular storage domain
it did you forced it somehow?
It was imported automatically. The chain of events was install HE, wait for the emails
saying it was done cogitating, create the regular Gluster SD, import it. Shortly
thereafter, the HE domain was imported, and things (storage, hosts, clusters) all appear
correct in the GUI, but the error persists.
-j
In the GUI, a periodic error is logged: “The Hosted Engine Storage
Domain doesn’t exist. It will be imported automatically…”
In engine.log, all I’m seeing that appears relevant is:
2017-04-25 10:28:57,988-07 INFO
[org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand]
(org.ovirt.thread.pool-6-thread-9) [1e44dde0] Lock Acquired to object
'EngineLock:{exclusiveLocks='[]', sharedLocks='null'}'
2017-04-25 10:28:57,992-07 WARN
[org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand]
(org.ovirt.thread.pool-6-thread-9) [1e44dde0] Validation of action
'ImportHostedEngineStorageDomain' failed for user SYSTEM. Reasons:
VAR__ACTION__ADD,VAR__TYPE__STORAGE__DOMAIN,ACTION_TYPE_FAILED_STORAGE_DOMAIN_ALREADY_EXIST
2017-04-25 10:28:57,992-07 INFO
[org.ovirt.engine.core.bll.storage.domain.ImportHostedEngineStorageDomainCommand]
(org.ovirt.thread.pool-6-thread-9) [1e44dde0] Lock freed to object
'EngineLock:{exclusiveLocks='[]', sharedLocks='null’}’
Otherwise the log is pretty clean.
I saw nothing of interest in the Gluster logs or the hosted-engine-ha logs on the host it
is running on.
It appears harmless, but then we aren’t actually using these systems yet, and in any case
we don’t want the error spamming the log forever. This is 4.1.1.8-1.el7.centos, hosted
engine on Centos 7.6.1311, Gluster for both the hosted engine and general data domains.
Has anyone seen this before?
Thanks in advance,
-j
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users