Attached logs, from engine and SPM. Some fields was anonimyzed.
In the meantime, I've put in place a workaround:
update the engine DB, removed the storage I've tried to add from both
storage_domain_dynamic and storage_domain_static.
After couple of minutes (more than 15) the LUN was again available, tried
to add, success.
Would be interesting why it was failing at first attempt.
Thanks
2017-10-11 16:07 GMT+02:00 Adam Litke <alitke(a)redhat.com>:
Please provide engine and vdsm logs during the failure window.
On Wed, Oct 11, 2017 at 8:23 AM, Roberto Nunin <robnunin(a)gmail.com> wrote:
> I've tried to add a second FC data domain to our oVirt remote infra,
> built with 6 hosts in remote and 4 local, where hosted-engine is running.
>
> Currently, we are using 4.0.1.1-1.el7.centos.
>
> After FC storage setup (zoning/masking), tried to add the new volume to
> the remote DC.
>
> Process was failing with:
>
> 2017-10-11 12:57:31,174 ERROR [org.ovirt.engine.core.dal.dbb
> roker.auditloghandling.AuditLogDirector] (default task-5) [bfcbca2]
> Correlation ID: bfcbca2, Job ID: 0850b9ba-a898-472c-9dbd-3ae4f27b2992,
> Call Stack: null, Custom Event ID: -1, Message: Failed to attach Storage
> Domain oVirt_datastore_2_NO to Data Center CompanyDCoVirt4. (User:
> me(a)srv-ldap-new.company.com-authz).
>
> on SPM, vdsm log report:
>
> jsonrpc.Executor/0::ERROR::2017-10-11 12:57:26,503::sdc::140::Storag
> e.StorageDomainCache::(_findDomain) looking for unfetched domain
> 17d3d910-3f79-468e-9ffb-a7bd2bd174aa
> jsonrpc.Executor/0::ERROR::2017-10-11 12:57:26,503::sdc::157::Storag
> e.StorageDomainCache::(_findUnfetchedDomain) looking for domain
> 17d3d910-3f79-468e-9ffb-a7bd2bd174aa
> jsonrpc.Executor/0::ERROR::2017-10-11 12:57:26,505::sdc::146::Storag
> e.StorageDomainCache::(_findDomain) domain 17d3d910-3f79-468e-9ffb-a7bd2bd174aa
> not found
>
>
> After this attempt, I've double checket that all 6 hosts have identified
> the new volume. All are ok.
>
> Another attempt to add the volume to the remote DC, was failing blocking
> me to chosse the volume ID into the GUI interface, because "the LUN is
> already part of a Storage DOmain".
>
> I think that something is still marking as used the new volume into the
> host-engine DB, even if it isn't available into the GUI interface.
> If this could be the reason, how to correctly manage this issue ? (apart
> update the entire installation, planned :) )
>
> Thanks in advance
>
> --
> Roberto
>
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
--
Adam Litke