I am seeing random failures for test
It looks like this is a timing issue since by the time we print out the
error we actually see the resize succeeded. see example below:
Can you please assign someone from the storage team to fix this test?
Fedora 29 oVirt packages building is still in progress.
The following package still need to be built, help with getting them built
on fedora 29 will be appreciated.
---------- Forwarded message ---------
Da: Mohan Boddu <mboddu(a)bhujji.com>
Date: mer 29 mag 2019 alle ore 01:05
Subject: Fedora 28 End Of Life
To: <announce(a)lists.fedoraproject.org>, <
As of the 28th of May 2019, Fedora 28 has reached its end of life
for updates and support. No further updates, including security
updates, will be available for Fedora 28. Fedora 29 will continue to receive
updates until approximately one month after the release of Fedora 31.
The maintenance schedule of Fedora releases is documented on the
Fedora Project wiki . The Fedora Project wiki also contains
instructions  on how to upgrade from a previous release of Fedora
to a version receiving updates.
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
I'm happy to announce, that with  landing in master, we're now
building Python 3 packages for VDSM. Example pipeline run can be found
Currently the py3 RPMs still have some broken dependencies and there are
ongoing efforts to fix these. All scripts in built RPMs have py3 shebang
lines, but there is no guarantee that all of them will work. We also
build for Fedora 28 only - more patches are on the way that will build
RPMs for Fedora 30.
If you want to make py3 RPMs out of your VDSM patch, you simply need to
post 'ci please build' in gerrit - that will launch 'build-artifacts'
stdci stage which produces py2 and py3 RPMs in its sub-stages.
I use following code to change it's os information
then I get an error like following:
Exception in thread "main" org.ovirt.engine.sdk4.Error: Fault reason is "Operation Failed". Fault detail is "[Cannot edit VM. Invalid time zone for given OS type., Attribute: vmStatic]". HTTP response code is "400". HTTP response message is "Bad Request".
In my test, I find for the virtual machine which is in "down" status, it's running as same as I expect.But with those alive virtual machine with current os is not "other" ,it will make the mistake as above.
Could someone know what's the problem is and how to change the os type for alive virtual machine?