[ovirt-devel] [engine 4.0->4.1 upgrade] How to effectively test an upgrade

[Yaniv Kaul]

On Fri, Jul 28, 2017 at 12:39 PM, Lukas Svaty <lsvaty at redhat.com> wrote:

> I would say for sanity these steps would be sufficient. I am considering
> just an empty engine, as I believe you're question is regarding ansible
> automation of this.
>
> a) check health page
> b) check database status
> c) check service (ovirt-engine, ovirt-engine-dwhd and other ovirt related
> services running before upgrade) status
>

- Login to the UI
- Create a VM
- (If you are using the API, create it using the API)
- Run a VM
- Live migrate a VM


Y.


>
> LS
>
> On Mon, Jul 24, 2017 at 5:20 PM, Tasdik Rahman <prodicus at outlook.com>
> wrote:
>
>> Hello there,
>>
>> I was wondering how should one test after upgrading the system. The
>> versions I am at hand right now is from
>>
>>    - 4.0 -> 4.1
>>    - 4.1 - > 4.2
>>
>> But I am guessing the testing should not differ much between the
>> different versions.
>>
>> Suggestions would be appreciated.
>>
>> Thanks,
>> Tasdik
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/devel/attachments/20170729/e1ded37f/attachment.html>