Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-27 Thread Roman Mohr
On Fri, Jun 24, 2016 at 6:34 PM, Scott wrote: > Actually, I figured out a work around. I changed the HostedEngine VM's > vds_group_id in the database to the vds_group_id of my temporary cluster > (found from the vds_groups table). This worked and I could put my main > cluster

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-25 Thread Michal Skrivanek
> On 24 Jun 2016, at 18:34, Scott wrote: > > Actually, I figured out a work around. I changed the HostedEngine VM's > vds_group_id in the database to the vds_group_id of my temporary cluster > (found from the vds_groups table). This worked and I could put my main >

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-24 Thread Scott
Actually, I figured out a work around. I changed the HostedEngine VM's vds_group_id in the database to the vds_group_id of my temporary cluster (found from the vds_groups table). This worked and I could put my main cluster in upgrade mode. Now to continue the process... Thanks, Scott On Fri, Jun

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-24 Thread Scott
Hi Roman, I made it through step 6 however it does look like the problem you mentioned has occurred. My engine VM is running on my host in the temporary cluster. The stats under Hosts show this. But in the Virtual Machines tab this VM still thinks its on my main cluster and I can't change that

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-24 Thread Roman Mohr
On Thu, Jun 23, 2016 at 10:26 PM, Scott wrote: > Hi Roman, > > Thanks for the detailed steps. I follow the idea you have outlined and I > think its easier than what I thought of (moving my self hosted engine back > to physical hardware, upgrading and moving it back to self

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-23 Thread Scott
Hi Roman, Thanks for the detailed steps. I follow the idea you have outlined and I think its easier than what I thought of (moving my self hosted engine back to physical hardware, upgrading and moving it back to self hosted). I will give it a spin in my build RHEV cluster tomorrow and let you

Re: [ovirt-users] InClusterUpgrade Scheduling Policy

2016-06-23 Thread Roman Mohr
Hi Scott, On Thu, Jun 23, 2016 at 8:54 PM, Scott wrote: > Hello list, > > I'm trying to upgrade a self-hosted engine RHEV environment running 3.5/el6 > to 3.6/el7. I'm following the process outlined in these two documents: > >