Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-07 Thread Michael Watters
Can you configure a *new* cluster and migrate the engine to that? You should be able to import your existing storage domains and logical networks under the new cluster which can then be used as a migration target for any running VMs. Your other option would be to build a new engine using 4.0 and

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-07 Thread Chris Adams
Once upon a time, Chris Adams said: > However, now I'm back into the catch-22 of 3.6.7+hosted engine: the > cluster compatibility level can't be raised while there's a running VM, > and that includes the hosted engine. I'm still stuck on this - anybody have any solution?

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Chris Adams
Once upon a time, Simone Tiraboschi said: > On Wed, Mar 1, 2017 at 5:04 PM, Chris Adams wrote: > > I first tried setting the policy, but got "Error while executing action: > > The set cluster compatibility version does not allow mixed major host OS > >

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Simone Tiraboschi
On Wed, Mar 1, 2017 at 5:04 PM, Chris Adams wrote: > Once upon a time, Simone Tiraboschi said: > > On Wed, Mar 1, 2017 at 3:19 PM, Chris Adams wrote: > > > However, now I'm back into the catch-22 of 3.6.7+hosted engine: the > > > cluster

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Chris Adams
Once upon a time, Simone Tiraboschi said: > On Wed, Mar 1, 2017 at 3:19 PM, Chris Adams wrote: > > However, now I'm back into the catch-22 of 3.6.7+hosted engine: the > > cluster compatibility level can't be raised while there's a running VM, > > and that

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Simone Tiraboschi
On Wed, Mar 1, 2017 at 3:19 PM, Chris Adams wrote: > Once upon a time, Simone Tiraboschi said: > > > I recreated a 3.5 setup and upgraded the engine to 3.6 - that should > > > have been enough to import the hosted engine storage domain, right? > > > > Did

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Chris Adams
Once upon a time, Simone Tiraboschi said: > > I recreated a 3.5 setup and upgraded the engine to 3.6 - that should > > have been enough to import the hosted engine storage domain, right? > > Did you also raised the cluster compatibility level to 3.6 on the engine? No (I

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-03-01 Thread Simone Tiraboschi
On Tue, Feb 28, 2017 at 10:04 PM, Chris Adams wrote: > Once upon a time, Simone Tiraboschi said: > > On Fri, Feb 24, 2017 at 8:24 PM, Chris Adams wrote: > > > > > So, on to my next upgrade issue (sorry for all the questions and thanks >

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-02-27 Thread Chris Adams
Once upon a time, Simone Tiraboschi said: > Can you please attach your engine.log ? Sorry, I was rolling back to 3.5 snapshots to test my 3.6 procedure (trying to make sure I didn't just screw up), made a mistake, and started over. Now however, I can't do anything, because

Re: [ovirt-users] 3.5->3.6 did not import hosted engine storage domain

2017-02-26 Thread Simone Tiraboschi
On Fri, Feb 24, 2017 at 8:24 PM, Chris Adams wrote: > So, on to my next upgrade issue (sorry for all the questions and thanks > for everybody's help)... I upgraded my test cluster from 3.5 to 3.6 > (latest version of each, all on CentOS 7 except the engine on CentOS 6). > Now