Hi Paul,

Can you please update whether the upgrade for 3.6.4 has helped.
Regarding the OVF_STORE disks, those disks should not be deleted since deleting them might reflect on the Disaster Recovery scenarios

Regards,
Maor

On Thu, Mar 24, 2016 at 10:10 PM, Paul Groeneweg | Pazion <paul@pazion.nl> wrote:
I believe my problem is related to this bug https://bugzilla.redhat.com/show_bug.cgi?id=1303316

As you can see in the screenshot the hostedengine storage is unassigned and so both ovf_stores are OK, but not linked and therefore  can't be updated?!

So for now I guess I'll wait for update 3.6.4 and cross my fingers and updates solves the event log error.

Op do 24 mrt. 2016 om 20:15 schreef Paul Groeneweg | Pazion <paul@pazion.nl>:
I checked, the OVf, but I can only remove the OVF.


What happens when I remove them, is it safe?

I checked agent.log and do not see the errors there....

MainThread::INFO::2016-03-24 20:12:28,154::image::116::ovirt_hosted_engine_ha.lib.image.Image::(prepare_images) Preparing images

MainThread::INFO::2016-03-24 20:12:28,811::hosted_engine::684::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(_initialize_storage_images) Reloading vm.conf from the shared storage domain

MainThread::INFO::2016-03-24 20:12:28,811::config::205::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) Trying to get a fresher copy of vm configuration from the OVF_STORE

MainThread::INFO::2016-03-24 20:12:28,936::ovf_store::100::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:18c50ea6-4654-4525-b241-09e15acf5e99, volUUID:2f2ccb59-a3f3-43bf-87eb-53595af01cf5

MainThread::INFO::2016-03-24 20:12:29,147::ovf_store::100::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(scan) Found OVF_STORE: imgUUID:6e14348b-af7a-49bc-9af2-8b703c17a53d, volUUID:fabdd6f4-b8d6-4ffe-889c-df86b34619ca

MainThread::INFO::2016-03-24 20:12:29,420::ovf_store::109::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF) Extracting Engine VM OVF from the OVF_STORE

MainThread::INFO::2016-03-24 20:12:29,580::ovf_store::116::ovirt_hosted_engine_ha.lib.ovf.ovf_store.OVFStore::(getEngineVMOVF) OVF_STORE volume path: /rhev/data-center/mnt/hostedstorage.pazion.nl:_opt_hosted-engine/88b69eba-ef4f-4dbe-ba53-20dadd424d0e/images/6e14348b-af7a-49bc-9af2-8b703c17a53d/fabdd6f4-b8d6-4ffe-889c-df86b34619ca 

MainThread::INFO::2016-03-24 20:12:29,861::config::225::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) Found an OVF for HE VM, trying to convert

MainThread::INFO::2016-03-24 20:12:29,865::config::230::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine.config::(refresh_local_conf_file) Got vm.conf from OVF_STORE

MainThread::INFO::2016-03-24 20:12:29,997::hosted_engine::462::ovirt_hosted_engine_ha.agent.hosted_engine.HostedEngine::(start_monitoring) Current state EngineUp (score: 3400)


So leaves me wondering if I should worry about the errors in the event log.




Op do 24 mrt. 2016 om 16:18 schreef Paul Groeneweg | Pazion <paul@pazion.nl>:

These OVF stores are created on my hosted-engine storage instance. I did not found any reference in the hosted-engine.conf, so you are sure they can't be deleted?

So it holds only info about the hosted-engine disk? So when detaching, do I have any risk destroying my hosted-engine?

I can just detach them in this screen: http://screencast.com/t/ymnzsNHj7e and then re-attach?

I check file permissions, but this looked good compared to the other images. So really strange this eventlog.

Regards,
Paul


Op do 24 mrt. 2016 om 10:01 schreef Maor Lipchuk <mlipchuk@redhat.com>:
Met vriendelijke groeten,

Paul Groeneweg
Pazion
Webdevelopment  -  Hosting  -  Apps

M +31 614 277 577

 ***disclaimer*** 
"This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation."

On Thu, Mar 24, 2016 at 12:12 AM, Paul Groeneweg | Pazion <paul@pazion.nl> wrote:

After the 3.6 updates ( which didn't went without a hitch )

I get the following errors in my event log: 

Failed to update OVF disks 18c50ea6-4654-4525-b241-09e15acf5e99, OVF data isn't updated on those OVF stores (Data Center Default, Storage Domain hostedengine_nfs).

VDSM command failed: Could not acquire resource. Probably resource factory threw an exception.: ()


When I check on file there is some data, but not updated: http://screencast.com/t/hbXQFlou

When I check in the web interface I see 2 OVF files listed. What are these for, can I delete them? http://screencast.com/t/ymnzsNHj7e 

Hopefully someone knows what to do about these warnings/erros and whether I can delete the OVF files.

Best Regards,
Paul Groeneweg


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


Hi Paul,

The OVF_STORE disks are disks which preserve all the VMs and Templates OVF data and are mostly use for disaster recovery scenarios.
Those disks can not be deleted.
Regarding the audit log which you got, can you try to detach and attach the Storage once again and let me know if you still get this even log.

Regards,
Maor