[ovirt-users] OVF_Store In Every Storage Doamin - Can We Remove?
Hi All, The Subject pretty much sums up the question I want to ask: There are two OVF_Store Disks created in all eight Storage Domains we have, making 16 total. This is cluttering up several of our views in the oVirt Admin Webpages. Is there anything stopping us from deleting some/all of these? Cheers Dulux-Oz ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ISUBYKWPTNBS3VMXZCM6PN6MLFXFY4DU/
[ovirt-users] OVF_STORE update error
hi. I use automatic translation, not English as my main language. Please note that this is a difficult expression to understand. I have an NFS storage domain that I used with ovirt 4.4 and I imported it with oracle linux virtualization manager 4.3. As a result, OVF_STORE fails to update. Failed to update VMs/Templates OVF data for Storage Domain [Domain Name] in Data Center [DC Name]. Failed to update OVF disks [OVF_STORE1_diskID],[OVF_STORE2_diskID], OVF data ins't updated on those OVF stores (Data Center [DC Name], Storage Domain [Domain Name]). In addition, there was the following log. [org.ovirt.engine.core.bll.storage.ovfstore.UploadStreamCommant] (EE-ManagedThreadFactory-engineScheduled-Thread-100) [4859c0db] Validation of action 'UploadStream' failed for user SYSTEM. Reasons: VAR__TYPE__STORAGE__DOMAIN,ACTION_TYPE_FAILED_DISK_VOLUME_TYPE_UNSUPPORTED,$volumeTypeSparse,$supportedVolumeTypes Preallocated With ovirt 4.4, OVF STORE is created with thin provisioning. With olvm4.3, I think the problem is that OVF_STORE is created in Preallocated. Is there a way to fix it while the virtual machine is still running? Thank you. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PHLVBO3HL6ZG6II44FOPOOMEAQZIUMQX/
Re: [ovirt-users] OVF_STORE issue after upgrading from 3.6.1 to 3.6.2
On Tue, Jan 26, 2016 at 3:24 PM, Luiz Claudio Prazeres Goncalves < luiz...@gmail.com> wrote: > By the way, I've tried to ,manually, add the engine storage domain , but > failed... it's a wrong procedure, but I did it before talking to Simone :( > ... it was manually removed later > > even after removing the wrong one the "correct one" was not > automatically generated even waiting > 1 h. > > > *as a colateral effect , I suppose, I've started to see the following > errors on agent.log* > > MainThread::INFO::2016-01-26 > 13:03:32,827::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:03:37,842::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:03:42,858::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:03:47,873::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:03:52,889::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:03:57,904::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:04:02,920::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:04:07,936::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::INFO::2016-01-26 > 13:04:12,960::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) > VDSM domain monitor status: PENDING > > MainThread::ERROR::2016-01-26 > 13:04:12,961::hosted_engine::832::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_domain_monitor) > Failed to start monitoring domain > (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during > domain acquisition > > Traceback (most recent call last): > > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > line 454, in start_monitoring > > self._initialize_domain_monitor() > > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > line 833, in _initialize_domain_monitor > > raise Exception(msg) > > Exception: Failed to start monitoring domain > (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during > domain acquisition > > MainThread::WARNING::2016-01-26 > 13:04:12,961::hosted_engine::480::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) > Error while monitoring engine: Failed to start monitoring domain > (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during > domain acquisition > > MainThread::WARNING::2016-01-26 > 13:04:12,961::hosted_engine::483::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) > Unexpected error > > Traceback (most recent call last): > > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > line 454, in start_monitoring > > self._initialize_domain_monitor() > > File > "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", > line 833, in _initialize_domain_monitor > > raise Exception(msg) > > Exception: Failed to start monitoring domain > (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during > domain acquisition > > MainThread::ERROR::2016-01-26 > 13:04:12,961::hosted_engine::496::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) > Shutting down the agent because of 3 failures in a row! > > MainThread::WARNING::2016-01-26 > 13:04:14,979::hosted_engine::767::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_domain_monitor_if_possible) > The VM is running locally or we have no data, keeping the domain monitor. > > MainThread::INFO::2016-01-26 > 13:04:14,980::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(run) > Agent shutting down > > > > MainThread::ERROR::2016-01-26 > 13:04:12,961::hosted_engine::496::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) > Shutting down the agent because of 3 failures in a row! > > MainThread::WARNING::2016-01-26 > 13:04:14,979::hosted_engine::767::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_domain_monitor_if_possible) > The
Re: [ovirt-users] OVF_STORE issue after upgrading from 3.6.1 to 3.6.2
By the way, I've tried to ,manually, add the engine storage domain , but failed... it's a wrong procedure, but I did it before talking to Simone :( ... it was manually removed later even after removing the wrong one the "correct one" was not automatically generated even waiting > 1 h. *as a colateral effect , I suppose, I've started to see the following errors on agent.log* MainThread::INFO::2016-01-26 13:03:32,827::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:03:37,842::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:03:42,858::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:03:47,873::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:03:52,889::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:03:57,904::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:04:02,920::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:04:07,936::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::INFO::2016-01-26 13:04:12,960::hosted_engine::862::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_get_domain_monitor_status) VDSM domain monitor status: PENDING MainThread::ERROR::2016-01-26 13:04:12,961::hosted_engine::832::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_domain_monitor) Failed to start monitoring domain (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during domain acquisition Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 454, in start_monitoring self._initialize_domain_monitor() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 833, in _initialize_domain_monitor raise Exception(msg) Exception: Failed to start monitoring domain (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during domain acquisition MainThread::WARNING::2016-01-26 13:04:12,961::hosted_engine::480::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Error while monitoring engine: Failed to start monitoring domain (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during domain acquisition MainThread::WARNING::2016-01-26 13:04:12,961::hosted_engine::483::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Unexpected error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 454, in start_monitoring self._initialize_domain_monitor() File "/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/agent/hosted_engine.py", line 833, in _initialize_domain_monitor raise Exception(msg) Exception: Failed to start monitoring domain (sd_uuid=7149b31d-430b-4d91-a8a3-ae1024dfd0a9, host_id=2): timeout during domain acquisition MainThread::ERROR::2016-01-26 13:04:12,961::hosted_engine::496::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Shutting down the agent because of 3 failures in a row! MainThread::WARNING::2016-01-26 13:04:14,979::hosted_engine::767::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_domain_monitor_if_possible) The VM is running locally or we have no data, keeping the domain monitor. MainThread::INFO::2016-01-26 13:04:14,980::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down MainThread::ERROR::2016-01-26 13:04:12,961::hosted_engine::496::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Shutting down the agent because of 3 failures in a row! MainThread::WARNING::2016-01-26 13:04:14,979::hosted_engine::767::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_stop_domain_monitor_if_possible) The VM is running locally or we have no data, keeping the domain monitor. MainThread::INFO::2016-01-26 13:04:14,980::agent::143::ovirt_hosted_engine_ha.agent.agent.Agent::(run) Agent shutting down *and now the HA Agent do not start anymore... Anyone know how to fix both issues ? * Thanks -Luiz
Re: [ovirt-users] OVF_STORE issue after upgrading from 3.6.1 to 3.6.2
In fact the hosted-engine storage domain was not created on 3.6.1 and , therefore, that's the OVF_STORE was not there. It's a gluster storage where the engine is being stored, so how can I "force" the generation of the hosted-engine storage domain ... it's not being generated automatically, even waiting > 1 h. Thanks -Luiz 2016-01-26 11:17 GMT-02:00 Simone Tiraboschi : > > > On Tue, Jan 26, 2016 at 1:11 PM, Luiz Claudio Prazeres Goncalves < > luiz...@gmail.com> wrote: > >> Hi, after upgrading from 3.6.1 to 3.6.2 I'm getting an error with >> OVF_STORE. How can I recreate the OVF_STORE? In another post someone said >> that i would be recreated after 1 hour, but not seems to be my case... Do I >> have a way to manually regenerate ? >> > > The engine will create the OVF_STORE only if it correctly imported the > hosted-engine storage domain; can you please check that? > If it's still not there and you are upgrading, maybe you have just a > left-over from previous release where the auto-import of the hosted-engine > storage domain wasn't that stable. Please trying manually cleaning it. > > >> MainThread::WARNING::2016-01-26 >> 12:07:56,734::ovf_store::105::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) >> Unable to find OVF_STORE >> >> MainThread::ERROR::2016-01-26 >> 12:07:56,735::config::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) >> Unable to get vm.conf from OVF_STORE, falling back to initial vm.conf >> >> MainThread::INFO::2016-01-26 >> 12:07:56,790::hosted_engine::464::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) >> Current state EngineUp (score: 3400) >> >> >> Thanks >> >> -Luiz >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] OVF_STORE issue after upgrading from 3.6.1 to 3.6.2
On Tue, Jan 26, 2016 at 1:11 PM, Luiz Claudio Prazeres Goncalves < luiz...@gmail.com> wrote: > Hi, after upgrading from 3.6.1 to 3.6.2 I'm getting an error with > OVF_STORE. How can I recreate the OVF_STORE? In another post someone said > that i would be recreated after 1 hour, but not seems to be my case... Do I > have a way to manually regenerate ? > The engine will create the OVF_STORE only if it correctly imported the hosted-engine storage domain; can you please check that? If it's still not there and you are upgrading, maybe you have just a left-over from previous release where the auto-import of the hosted-engine storage domain wasn't that stable. Please trying manually cleaning it. > MainThread::WARNING::2016-01-26 > 12:07:56,734::ovf_store::105::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) > Unable to find OVF_STORE > > MainThread::ERROR::2016-01-26 > 12:07:56,735::config::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) > Unable to get vm.conf from OVF_STORE, falling back to initial vm.conf > > MainThread::INFO::2016-01-26 > 12:07:56,790::hosted_engine::464::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) > Current state EngineUp (score: 3400) > > > Thanks > > -Luiz > > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] OVF_STORE issue after upgrading from 3.6.1 to 3.6.2
Hi, after upgrading from 3.6.1 to 3.6.2 I'm getting an error with OVF_STORE. How can I recreate the OVF_STORE? In another post someone said that i would be recreated after 1 hour, but not seems to be my case... Do I have a way to manually regenerate ? MainThread::WARNING::2016-01-26 12:07:56,734::ovf_store::105::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Unable to find OVF_STORE MainThread::ERROR::2016-01-26 12:07:56,735::config::234::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) Unable to get vm.conf from OVF_STORE, falling back to initial vm.conf MainThread::INFO::2016-01-26 12:07:56,790::hosted_engine::464::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Current state EngineUp (score: 3400) Thanks -Luiz ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] OVF_STORE?
On 04.11.2014 19:39, Einav Cohen wrote: Hello Einav, > OVF_STOREs are images that contain the meta-data of VMs and Disks > that reside on that data-domain. This meta-data is used in case > the data-domain is imported/exported to/from a different data- > center or a different ovirt setup. > > more details in [1]. Thanks! > > there is a BZ that requests separating these OVF_STOREs to > a separate "tag" under the Disks main tab [2]. > > [1] http://www.ovirt.org/Features/ImportStorageDomain > > [2] Bug 1131508 - [RFE] [engine-webadmin] There should be a separated tag for > OVF_STORE disks under the 'Disks' main tab > [https://bugzilla.redhat.com/show_bug.cgi?id=1131508] > > - Original Message - >> From: "Daniel Helgenberger" >> To: users@ovirt.org >> Sent: Tuesday, November 4, 2014 12:46:52 PM >> Subject: [ovirt-users] OVF_STORE? >> >> Hello, >> >> out of curiosity: After my DC was upgraded to 3.5 I have two disk images >> called OVF_STORE on every data domain. What is their purpose? >> >> Thanks >> -- >> Daniel Helgenberger >> m box bewegtbild GmbH >> >> P: +49/30/2408781-22 >> F: +49/30/2408781-10 >> >> ACKERSTR. 19 >> D-10115 BERLIN >> >> >> www.m-box.de www.monkeymen.tv >> >> Geschäftsführer: Martin Retschitzegger / Michaela Göllner >> Handeslregister: Amtsgericht Charlottenburg / HRB 112767 >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] OVF_STORE?
OVF_STOREs are images that contain the meta-data of VMs and Disks that reside on that data-domain. This meta-data is used in case the data-domain is imported/exported to/from a different data- center or a different ovirt setup. more details in [1]. there is a BZ that requests separating these OVF_STOREs to a separate "tag" under the Disks main tab [2]. [1] http://www.ovirt.org/Features/ImportStorageDomain [2] Bug 1131508 - [RFE] [engine-webadmin] There should be a separated tag for OVF_STORE disks under the 'Disks' main tab [https://bugzilla.redhat.com/show_bug.cgi?id=1131508] - Original Message - > From: "Daniel Helgenberger" > To: users@ovirt.org > Sent: Tuesday, November 4, 2014 12:46:52 PM > Subject: [ovirt-users] OVF_STORE? > > Hello, > > out of curiosity: After my DC was upgraded to 3.5 I have two disk images > called OVF_STORE on every data domain. What is their purpose? > > Thanks > -- > Daniel Helgenberger > m box bewegtbild GmbH > > P: +49/30/2408781-22 > F: +49/30/2408781-10 > > ACKERSTR. 19 > D-10115 BERLIN > > > www.m-box.de www.monkeymen.tv > > Geschäftsführer: Martin Retschitzegger / Michaela Göllner > Handeslregister: Amtsgericht Charlottenburg / HRB 112767 > ___ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] OVF_STORE?
Hello, out of curiosity: After my DC was upgraded to 3.5 I have two disk images called OVF_STORE on every data domain. What is their purpose? Thanks -- Daniel Helgenberger m box bewegtbild GmbH P: +49/30/2408781-22 F: +49/30/2408781-10 ACKERSTR. 19 D-10115 BERLIN www.m-box.de www.monkeymen.tv Geschäftsführer: Martin Retschitzegger / Michaela Göllner Handeslregister: Amtsgericht Charlottenburg / HRB 112767 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users