Fernando, thanks! That did it!
- added the ovirt 3.6 repo to the host
- tried to update vdsm but had complaints about no glusterfs >= 3.7.x
available
- glusterfs 3.7.11 seems to be the latest with FC22 packages, so added
that as a repo
- vdsm updated as expected
- reinstalled host from GUI
- fired right up
Ya saved me!
On Wed, Aug 17, 2016 at 10:23 PM Fernando Fuentes
<ffuentes(a)darktcp.net> wrote:
> __
> Erik,
>
> I had a similar issue in the past. I think that updating vdsm on
> your host can do the trick.
> Put your host on maintenance mode and upgrade your host to 3.6.
>
> Make sure you install the 3.6 repos.
>
> Good luck!
>
> Regards,
>
> --
> Fernando Fuentes
> ffuentes(a)txweather.org
>
http://www.txweather.org
>
>
>
> On Wed, Aug 17, 2016, at 09:45 PM, Erik Brakke wrote:
>> Hello,
>> I changed my cluster and data center compatibility from 3.5 to 3.6
>> with a 3.5 host. D'oh!
>> Engine: 3.6 on FC22
>> Host: 3.5 on FC22 (local storage)
>>
>> - Can I change the data center and cluster back to 3.5? How?
>> - I tried to upgrade host to 3.6 in the GUI. Maintenance->Reinstall
>> did not work, and Upgrade option is greyed out. Is there a way to
>> upgrade host to 3.6?
>>
>> Thanks
>> _________________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users