[ovirt-users] [ovirt-announce] [Call for feedback] share also your successful upgrades experience
Sandro Bonazzola
sbonazzo at redhat.com
Thu Dec 21 14:35:31 UTC 2017
2017-12-21 15:33 GMT+01:00 Sandro Bonazzola <sbonazzo at redhat.com>:
>
>
> 2017-12-21 15:16 GMT+01:00 FERNANDO FREDIANI <fernando.frediani at upx.com>:
>
>> Seems an upgrade guide is more than needed for a 4.1 to 4.2 upgrade.
>> Perhaps with all the feedback comming that can be done.
>>
>
>
Sorry, previous mail started by mistake.
We have an upgrade guide which indeed needs some love:
https://ovirt.org/documentation/upgrade-guide/upgrade-guide/
But upgrade from 4.0 to 4.1 and 4.1 to 4.2 is not different, just different
ovirt-release rpm to be used.
>
>
>>
>> On 21/12/2017 11:55, Misak Khachatryan wrote:
>>
>> Did upgrade to 4.2 yesterday.
>>
>> Everything wen smoothly except few glitches.
>>
>> I have 4 host install - 3 gluster and one node with local storage.
>> One of the gluster servers failed to start it's brick with Peer reject
>> status, solved very fast by googling.
>> On the node i hit old bug, can't upgrade it since 4.1.5 version, finally
>> it seems i just need to reinstall it from scratch.
>>
>>
>>
>> Best regards,
>> Misak Khachatryan
>>
>> On Thu, Dec 21, 2017 at 5:35 PM, Sandro Bonazzola <sbonazzo at redhat.com>
>> wrote:
>>
>>> Hi,
>>> now that oVirt 4.2.0 has been released, we're starting to see some
>>> reports about issues that for now are related to not so common deployments.
>>> We'd also like to get some feedback from those who upgraded to this
>>> amazing release without any issue and add these positive feedback under our
>>> developers (digital) Christmas tree as a gift for the effort put in this
>>> release.
>>> Looking forward to your positive reports!
>>>
>>> Not having positive feedback? Let us know too!
>>> We are putting an effort in the next weeks to promptly assist whoever
>>> hit troubles during or after the upgrade. Let us know in this
>>> users at ovirt.org mailing list (preferred) or on IRC using irc.oftc.net
>>> server and #ovirt channel.
>>>
>>> We are also closely monitoring bugzilla.redhat.com for new bugs on
>>> oVirt project, so you can report issues there as well.
>>>
>>> Thanks,
>>> --
>>>
>>> SANDRO BONAZZOLA
>>>
>>> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>>>
>>> Red Hat EMEA <https://www.redhat.com/>
>>> <https://red.ht/sig>
>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>>
>>>
>>> _______________________________________________
>>> Announce mailing list
>>> Announce at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/announce
>>>
>>>
>>
>>
>> _______________________________________________
>> Users mailing listUsers at ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
>
> --
>
> SANDRO BONAZZOLA
>
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
>
> Red Hat EMEA <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20171221/5fae6fbb/attachment.html>
More information about the Users
mailing list