Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

When upgrading the hosts I did add another Cluster 3.6 to be able to keep my VMs running ( as I couldn't connect el6 and el7 hosts in 1 cluster ). I was afaraid to lose my hosted-engine during upgrade, so kept hosted-engine as long as possible on old version. I then switched old Cluster to 3.6 and

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Tue, Feb 9, 2016 at 12:10 PM, Simone Tiraboschi wrote: > > > On Tue, Feb 9, 2016 at 11:57 AM, Paul Groeneweg | Pazion > wrote: > >> >> When upgrading the hosts >> I did add another Cluster 3.6 to be able to keep my VMs running ( as I >> couldn't connect

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Tue, Feb 9, 2016 at 9:45 AM, Paul Groeneweg | Pazion wrote: > I have added 2 logs from 2 hosts > > Both the hosts are just additional host: 2016-02-07 20:32:30 DEBUG otopi.plugins.otopi.dialog.human human.queryString:156 query OVEHOSTED_ADDITIONAL_HOST 2016-02-07 20:32:30

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Tue, Feb 9, 2016 at 11:57 AM, Paul Groeneweg | Pazion wrote: > > When upgrading the hosts > I did add another Cluster 3.6 to be able to keep my VMs running ( as I > couldn't connect el6 and el7 hosts in 1 cluster ). > The approach was right since you cannot mix hosts with el6

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Tue, Feb 9, 2016 at 10:53 AM, Paul Groeneweg | Pazion wrote: > The original (first host) was removed ( about a year a go I removed this > one ) and it is also removed from hosted-engine --vm-status overview. > > I ran 'hosted-engine --deploy' again on all the hosts because I

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

The original (first host) was removed ( about a year a go I removed this one ) and it is also removed from hosted-engine --vm-status overview. I ran 'hosted-engine --deploy' again on all the hosts because I upgraded all hosts to EL7. ( I have als ran engine-setup for the upgrade ) How can I fix

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

For the record, my hosted-engine still runs el6. The hosts now run el7. This means I need to save backup and restore to a new instance? I do need to upgrade hosted-engine to el7? I don't get the overall picture, but what I find strange is, the spUUID in my hosted-engine.conf is not found. When I

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Mon, Feb 8, 2016 at 11:25 PM, Paul Groeneweg | Pazion wrote: > > I found vdsClient and ran a few commands. > > [root@geisha-1 ~]# vdsClient -s 0 getStorageDomainInfo > 88b69eba-ef4f-4dbe-ba53-20dadd424d0e > > uuid = 88b69eba-ef4f-4dbe-ba53-20dadd424d0e > > version = 3 > > role

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Tue, Feb 9, 2016 at 11:51 AM, Paul Groeneweg | Pazion wrote: > For the record, my hosted-engine still runs el6. > You can run the 3.6 engine also on el6 so no issue there. > The hosts now run el7. > To reach 3.6 cluster compatibility level you need to upgrade all the hosts

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

Thanks for your response. I have reverted the commented entries and restarted ovirt-ha-agent. Now status on the daemon gives the error again: http://screencast.com/t/DCZo6QJM1 The hosted engine domain is not shown in the web storage overview... When I start import it shows a warning:

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

Update: 1. I was able to remove the warnirngs about the not found ovf / vm.conf by commenting the conf_volume_UUID, conf_image_UUID entries in the hosted-engine.conf. After a restart of the ovirt-ha-agent the errors were gone. ( I believe this is not a permanent solution ). 2. This morning I

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Mon, Feb 8, 2016 at 9:47 AM, Paul Groeneweg | Pazion wrote: > Update: > The OVF_STORE volume will contain the engine VM description in a format that the engine can easily handle. It will be created by the engine when: - it imported the hosted-engine storage domain - the

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

Op ma 8 feb. 2016 om 11:28 schreef Simone Tiraboschi : > On Mon, Feb 8, 2016 at 10:55 AM, Paul Groeneweg | Pazion > wrote: > >> Thanks for your response. >> >> I have reverted the commented entries and restarted ovirt-ha-agent. >> Now status on the daemon

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

On Mon, Feb 8, 2016 at 10:55 AM, Paul Groeneweg | Pazion wrote: > Thanks for your response. > > I have reverted the commented entries and restarted ovirt-ha-agent. > Now status on the daemon gives the error again: > http://screencast.com/t/DCZo6QJM1 > > Here I'm a bit confused:

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

I found vdsClient and ran a few commands. [root@geisha-1 ~]# vdsClient -s 0 getStorageDomainInfo 88b69eba-ef4f-4dbe-ba53-20dadd424d0e uuid = 88b69eba-ef4f-4dbe-ba53-20dadd424d0e version = 3 role = Master remotePath = hostedstorage.pazion.nl:/opt/hosted-engine type = NFS class = Data pool =

Re: [ovirt-users] ovirt 3.6 hostedengine.metadata, missing OVF_STORE

I still keep getting The Hosted Engine Storage Domain doesn't exist. It should be imported into the setup. I went digging a little further and found this in the engine.log 2016-02-08 22:30:25,083 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetStorageDomainInfoVDSCommand]