- Devel - oVirt List Archives

Old Ovirt site is down
by Fred Rolland 05 Sep '16

05 Sep '16

Hi, http://old.ovirt.org/ is down. Can someone look at it ? Thanks, Freddy Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. ------------------------------ Apache/2.2.15 (Red Hat) Server at old.ovirt.org Port 80

3 4

Update gerrit plugins (oauth, avatars-gravatar)
by Shlomo Ben David 05 Sep '16

05 Sep '16

Hi, Today 04/09/2016 at 23:00 i'm planning to update gerrit-oauth plugin from v0.3 ==> v2.11.3 In addition i will add the new avatars-gravatar plugin (v2.11) Update Duration: ~10 min During the update the gerrit.ovirt.org server won't be available An update email will be sent when done. Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1

4 4

[VDSM] Failing networking tests
by Nir Soffer 05 Sep '16

05 Sep '16

Hi all, These tests seems to fail unrelated builds: http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/1600/conso… Seen it once, please check. 19:43:05 ====================================================================== 19:43:05 ERROR: test_local_auto_with_dynamic_address_from_ra (network.netinfo_test.TestIPv6Addresses) 19:43:05 ---------------------------------------------------------------------- 19:43:05 Traceback (most recent call last): 19:43:05 File "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 19:43:05 return f(*args, **kwargs) 19:43:05 File "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/network/netinfo_test.py", line 419, in test_local_auto_with_dynamic_address_from_ra 19:43:05 IPV6_NETPREFIX_LEN, family=6) 19:43:05 File "/usr/lib64/python2.7/contextlib.py", line 24, in __exit__ 19:43:05 self.gen.next() 19:43:05 File "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/network/nettestlib.py", line 454, in wait_for_ipv6 19:43:05 raise Exception('IPv6 addresses has not been caught within the ' 19:43:05 Exception: IPv6 addresses has not been caught within the given timeout. 19:43:05 19:43:05 -------------------- >> begin captured logging << -------------------- 19:43:05 2016-09-04 19:42:32,949 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name veth_hU8rsgT1oy type veth peer name veth_OgkZCPxdBp (cwd None) 19:43:05 2016-09-04 19:42:32,962 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:32,965 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /usr/sbin/dnsmasq --dhcp-authoritative -p 0 --dhcp-option=3 --dhcp-option=6 -i veth_hU8rsgT1oy -I lo -d --bind-dynamic --enable-ra --dhcp-range=2001:1:1:1::,slaac,2m (cwd None) 19:43:05 2016-09-04 19:42:33,475 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:43:05 2016-09-04 19:42:33,501 DEBUG [root] (MainThread) SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:43:05 2016-09-04 19:42:33,502 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_hU8rsgT1oy -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:43:05 2016-09-04 19:42:33,514 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:33,515 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -I INPUT -i veth_hU8rsgT1oy -p udp --sport 546 --dport 547 -j ACCEPT (cwd None) 19:43:05 2016-09-04 19:42:33,523 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:33,525 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_OgkZCPxdBp up (cwd None) 19:43:05 2016-09-04 19:42:33,532 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:33,533 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev veth_hU8rsgT1oy up (cwd None) 19:43:05 2016-09-04 19:42:33,543 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:33,543 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip -6 addr add dev veth_hU8rsgT1oy 2001:1:1:1::1/64 (cwd None) 19:43:05 2016-09-04 19:42:33,550 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:53,541 DEBUG [root] (MainThread) dnsmasq: started, version 2.76 DNS disabled 19:43:05 dnsmasq: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC loop-detect inotify 19:43:05 dnsmasq: warning: interface veth_hU8rsgT1oy does not currently exist 19:43:05 dnsmasq-dhcp: router advertisement on 2001:1:1:1:: 19:43:05 dnsmasq-dhcp: IPv6 router advertisement enabled 19:43:05 dnsmasq-dhcp: RTR-ADVERT(veth_hU8rsgT1oy) 2001:1:1:1:: 19:43:05 dnsmasq-dhcp: RTR-ADVERT(veth_hU8rsgT1oy) 2001:1:1:1:: 19:43:05 19:43:05 2016-09-04 19:42:53,542 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/service iptables status (cwd None) 19:43:05 2016-09-04 19:42:53,589 DEBUG [root] (MainThread) SUCCESS: <err> = 'Redirecting to /bin/systemctl status iptables.service\nRunning in chroot, ignoring request.\n'; <rc> = 0 19:43:05 2016-09-04 19:42:53,590 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -D INPUT -i veth_hU8rsgT1oy -p udp --sport 68 --dport 67 -j ACCEPT (cwd None) 19:43:05 2016-09-04 19:42:53,612 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:53,613 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/iptables --wait -D INPUT -i veth_hU8rsgT1oy -p udp --sport 546 --dport 547 -j ACCEPT (cwd None) 19:43:05 2016-09-04 19:42:53,630 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:53,631 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link del dev veth_hU8rsgT1oy (cwd None) 19:43:05 2016-09-04 19:42:53,669 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 --------------------- >> end captured logging << --------------------- 19:43:05 19:43:05 ====================================================================== 19:43:05 FAIL: test_events_keys (network.netlink_test.NetlinkEventMonitorTests) 19:43:05 ---------------------------------------------------------------------- 19:43:05 Traceback (most recent call last): 19:43:05 File "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/testValidation.py", line 97, in wrapper 19:43:05 return f(*args, **kwargs) 19:43:05 File "/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/network/netlink_test.py", line 173, in test_events_keys 19:43:05 for d in _caught]))) 19:43:05 AssertionError: Expected events have not been caught (in the right order). 19:43:05 Expected: 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa'} 19:43:05 {'event': 'new_addr', 'address': '192.0.2.1/24'} 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa'} 19:43:05 {'event': 'new_addr', 'family': 'inet6'} 19:43:05 {'event': 'del_neigh'} 19:43:05 {'event': 'del_addr', 'family': 'inet6'} 19:43:05 {'event': 'del_addr', 'address': '192.0.2.1/24'} 19:43:05 {'destination': '192.0.2.1', 'event': 'del_route'} 19:43:05 {'event': 'del_link', 'name': 'dummy_40rKa'}. 19:43:05 Caught: 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa', 'address': '6e:f3:b9:80:5d:20'} 19:43:05 {'event': 'new_addr', 'family': 'inet', 'address': '192.0.2.1/24'} 19:43:05 {'destination': '192.0.2.1', 'event': 'new_route', 'family': 'inet'} 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa', 'address': '6e:f3:b9:80:5d:20'} 19:43:05 {'destination': '192.0.2.0/24', 'event': 'new_route', 'family': 'inet'} 19:43:05 {'destination': '192.0.2.0', 'event': 'new_route', 'family': 'inet'} 19:43:05 {'destination': '192.0.2.255', 'event': 'new_route', 'family': 'inet'} 19:43:05 {'destination': 'ff00::/8', 'event': 'new_route', 'family': 'inet6'} 19:43:05 {'destination': 'fe80::/64', 'event': 'new_route', 'family': 'inet6'} 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa', 'address': '6e:f3:b9:80:5d:20'} 19:43:05 {'event': 'new_addr', 'family': 'inet6', 'address': 'fe80::6cf3:b9ff:fe80:5d20/64'} 19:43:05 {'destination': 'fe80::6cf3:b9ff:fe80:5d20', 'event': 'new_route', 'family': 'inet6'} 19:43:05 {'destination': 'fe80::', 'event': 'new_route', 'family': 'inet6'} 19:43:05 {'event': 'new_link', 'name': 'dummy_40rKa', 'address': '6e:f3:b9:80:5d:20'} 19:43:05 {'destination': 'fe80::/64', 'event': 'del_route', 'family': 'inet6'} 19:43:05 {'destination': 'ff00::/8', 'event': 'del_route', 'family': 'inet6'} 19:43:05 {'event': 'del_addr', 'family': 'inet6', 'address': 'fe80::6cf3:b9ff:fe80:5d20/64'} 19:43:05 {'destination': 'fe80::', 'event': 'del_route', 'family': 'inet6'} 19:43:05 {'destination': 'fe80::6cf3:b9ff:fe80:5d20', 'event': 'del_route', 'family': 'inet6'} 19:43:05 {'event': 'del_addr', 'family': 'inet', 'address': '192.0.2.1/24'} 19:43:05 {'destination': '192.0.2.1', 'event': 'del_route', 'family': 'inet'} 19:43:05 {'event': 'del_link', 'name': 'dummy_40rKa', 'address': '6e:f3:b9:80:5d:20'}. 19:43:05 -------------------- >> begin captured logging << -------------------- 19:43:05 2016-09-04 19:42:54,605 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link add name dummy_40rKa type dummy (cwd None) 19:43:05 2016-09-04 19:42:54,623 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:54,623 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip -4 addr add dev dummy_40rKa 192.0.2.1/24 (cwd None) 19:43:05 2016-09-04 19:42:54,640 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:05 2016-09-04 19:42:54,642 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link set dev dummy_40rKa up (cwd None) 19:43:05 2016-09-04 19:42:54,658 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:16 2016-09-04 19:42:54,659 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-1 /sbin/ip link del dev dummy_40rKa (cwd None) 19:43:16 2016-09-04 19:42:54,684 DEBUG [root] (MainThread) SUCCESS: <err> = ''; <rc> = 0 19:43:16 --------------------- >> end captured logging << ---------------------

2 2

[VDSM] Avoiding leaks when handling exceptions
by Nir Soffer 05 Sep '16

05 Sep '16

Hi all, I found an interesting post about error handling and how to avoid such leaks - please check: https://cosmicpercolator.com/2016/01/13/exception-leaks-in-python-2-and-3/ Nir

2 2

Do we still need db upgrade jobs?
by Eyal Edri 05 Sep '16

05 Sep '16

Any reason to keep running db upgrade jobs? [1] while we already have engine setup+upgrade jobs running per patch? [2] [1] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-db-from-master_el7… [2] http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_creat… -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

2 2

[VDSM] Broken test - testV2VOutput
by Nir Soffer 05 Sep '16

05 Sep '16

Hi all, The following test fails consistently, looks like bad test, running real v2v instead of the fake-v2v script. Last change in this area was commit 985cbe87077512adf1ff594841b7f79674d451fc Author: Tomáš Golembiovský <tgolembi(a)redhat.com> Date: Wed Jun 22 15:21:26 2016 +0200 v2v: Log detailed output of virt-v2v The detailed log of virt-v2v output is often necessary to debug conversion failures. We provide '-v -x' arguments to virt-v2v to get the detailed output and store the logs in the VDSM log directory. We cannot use execCmd() to store the log output. Therefore we use CPopen directly to redirect stderr to stdout and pipe it to tee to store everything in a log file. Logs older than 30 days are removed periodically on the daily basis. Please fix or disable this test. ====================================================================== ERROR: testV2VOutput (v2vTests.v2vTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/root/rpmbuild/BUILD/vdsm-4.18.999/tests/v2vTests.py", line 552, in testV2VOutput with open('fake-virt-v2v.err', 'r') as f: IOError: [Errno 2] No such file or directory: 'fake-virt-v2v.err' -------------------- >> begin captured logging << -------------------- 2016-09-04 23:06:55,217 DEBUG [root] (MainThread) /usr/bin/taskset --cpu-list 0-7 /root/rpmbuild/BUILD/vdsm-4.18.999/tests/fake-virt-v2v -v -x -ic 'vpx://adminr%40vsphere@0.0.0.0/ovirt/0.0.0.0?no_verify=1' -o vdsm -of raw -oa sparse --vdsm-image-uuid 00000000-0000-0000-0000-000000000001 --vdsm-vol-uuid 00000000-0000-0000-0000-000000000002 --vdsm-image-uuid 00000000-0000-0000-0000-000000000003 --vdsm-vol-uuid 00000000-0000-0000-0000-000000000004 --password-file /tmp/mypass --vdsm-vm-uuid 00000000-0000-0000-0000-000000000005 --vdsm-ovf-output /usr/local/var/run/vdsm/v2v --machine-readable -os /rhev/data-center/00000000-0000-0000-0000-000000000006/00000000-0000-0000-0000-000000000007 TEST (cwd None) 2016-09-04 23:06:55,292 DEBUG [root] (MainThread) SUCCESS: <err> = 'libguestfs: trace: internal_autosync = 0\nlibguestfs: sending SIGTERM to process 12345\nlibguestfs: trace: shutdown = 0\nlibguestfs: trace: close\nlibguestfs: closing guestfs handle 0x1e265f0 (state 0)\n'; <rc> = 0 --------------------- >> end captured logging << ---------------------

2 1

Fwd: BuildRequires on obsoleted packages provided by Python
by Sandro Bonazzola 04 Sep '16

04 Sep '16

Fyi, vdsm included in the list of packages buildrequiring orphaned packages on fedora ---------- Messaggio inoltrato ---------- Da: "Charalampos Stratakis" <cstratak(a)redhat.com> Data: 31/Ago/2016 02:11 PM Oggetto: BuildRequires on obsoleted packages provided by Python A: "Development discussions related to Fedora" < devel(a)lists.fedoraproject.org> Cc: "Fedora Python SIG" <python-devel(a)lists.fedoraproject.org> > Hello all, > > While checking out the SPEC file of python, it seems there were some packages that, while separate at some point, they got included in python's stdlib and then obsoleted as standalone packages (thus to cope with the change, python was obsoleting these packages and providing them as well in the SPEC). So every package that currently (Build)Requires any of these packages will essentially drag python with it. > > I will remove these provides soon, since the packages were orphaned long time ago, but the packages that still require them, will need to be fixed and (Build)Require python instead. > > Here is a github commit with these changes from a testing repo: > https://github.com/fedora-python/python2-spec/commit/dfdd96e653d65ce6835955… > > And a list of the provided packages and the affected ones > > Distutils: None > > python-sqlite: > cas > yum > > python-ctypes: > drobo-utils > glusterfs-extra-xlators > glusterfs-geo-replication > python-smbios > > python-hashlib: > pyrpkg > > python-uuid: > dpm-server-mysql > oz > python2-celery > > python-argparse: > R2spec > catkin > diskimage-builder > euca2ools > fedora-review > feedstail > gfal2-util > glacier-cli > grin > hash-slinger > imagefactory > instack > libstoragemgmt > nordugrid-arc-nagios-plugins > os-apply-config > os-cloud-confic > os-collect-confic > os-net-config > pyrpkg > python-amqpclt > python-catkin_pkg > python-catkin_tools > python-cloudservers > python-gear > python-novaclient > python-postman > python-requestbuilder > python-rosdistro > python-rospkg > python-sparklines > python2-oslo-config > repo_manager > rpkg > vdsm > > Depending on feedback here I will follow (or not) the mass bug filling procedure so maintainer fix their packages. > > The reasoning behind this change, at the current time, is that I intent to rename python to python2 soon, which will lead to a re-review of python, so at the moment trying to have things as clear and consistent as possible. Plans for that change is only for rawhide (although it would be nice for f25 as well). > > Regards, > > Charalampos Stratakis > Associate Software Engineer > Python Maintenance Team, Red Hat > -- > devel mailing list > devel(a)lists.fedoraproject.org > https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

1 0

Fwd: Unversioned and >/=/>= obsoletes
by Sandro Bonazzola 02 Sep '16

02 Sep '16

FYI, Fedora reviewed vdsm spec file regarding obsoletes. ---------- Forwarded message ---------- From: Igor Gnatenko <ignatenko(a)redhat.com> Date: Fri, Sep 2, 2016 at 1:14 PM Subject: Unversioned and >/=/>= obsoletes To: Development discussions related to Fedora <devel(a)lists.fedoraproject.org>, devel-announce(a)lists.fedoraproject.org All guidelines mandate the use of </<= Obsoletes, but unfortunately we have some number of packages (179 source rpms -> 292 binary rpms) with unversioned Obsoletes or with >/=/>= Obsoletes. It is causing problems with upgrade (if package is getting re-added) or with 3rd-party repositories. Older package is obsoleting new package. Problem categories (in following text by "never" I mean latest N-2 releases): * Package/SubPackage was never built in Fedora Package "python" has "Obsoletes: python2" which was never built -> drop Obsoletes SubPackage "qpid-proton-c" of "qpid-proton" has "Obsoletes: qpid-proton" which was not the package for long time -> drop Obsoletes * Package replacement Package "storaged" has "Obsoletes: udisks2" -> take latest version from koji (2.1.7-1) and make Obsoletes versioned: udisks2 < 2.1.7-2 storaged is not simple use-case as it replaces udisks2, but latter is still not retired. * "=" Obsoletes "rubygem-vte" has "Obsoletes: ruby-vte = 3.0.9-1.fc26" (probably it's macro in spec) which seems really weird as it will not obsolete F24/F25 with such version * Obsoletes by Provides It doesn't work to prevent undefined behavior. Imagine you have installed "A" and "B", both providing "C". Package "D" has "Obsoletes: C", it should not remove "A" and "B". ** %{?_isa} "glibc-headers" has "Obsoletes: glibc-headers(i686)". %{?_isa} is just text, it's not part of architecture or something else. ** Other provides "rubygem-http_connection" has "Obsoletes: rubygem(right_http_connection)". Latter is virtual provides. * Weird obsoletes (broken) "krb5-server" has "Obsoletes: krb5-server-1.14.3-8.fc26.i686". Basically it will not obsolete anything because it's threated as package name (and we definitely don't have such package name). * >/>= Obsoletes "vdsm" has "Obsoletes: vdsm-infra >= 4.16.0". It's almost same as unversioned Obsoletes. So it must not be used. Table of affected packages/maintainers: https://ignatenkobrain.fedorapeople.org/broken-obsoletes/2016-09-02/broken- obsoletes.txt -- -Igor Gnatenko -- devel mailing list devel(a)lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>

3 2

oVirt "experimental" system tests now broken for master and 4.0
by Barak Korren 01 Sep '16

01 Sep '16

Hi there, The oVirt "experimental" system tests form "master and 4.0 started failing today at approximately 9:20 ([1], [2]) at the AddHost stage. I suspect the failure is due to a mom build that was performed today at 9:05 ([3], [4]). This is because the following can be found in the VDSM logs ([5], [6]): MainThread::ERROR::2016-09-01 06:18:41,076::vdsm::151::vds::(run) Exception raised Traceback (most recent call last): File "/usr/share/vdsm/vdsm", line 149, in run serve_clients(log) File "/usr/share/vdsm/vdsm", line 104, in serve_clients cif = clientIF.getInstance(irs, log, scheduler) File "/usr/share/vdsm/clientIF.py", line 204, in getInstance cls._instance = clientIF(irs, log, scheduler) File "/usr/share/vdsm/clientIF.py", line 105, in __init__ self._prepareMOM() File "/usr/share/vdsm/clientIF.py", line 273, in _prepareMOM self.mom = MomClient(momconf) File "/usr/lib/python2.7/site-packages/vdsm/momIF.py", line 46, in __init__ raise MomNotAvailableError() MomNotAvailableError MainThread::INFO::2016-09-01 06:18:41,077::vdsm::153::vds::(run) Stopping threads MainThread::INFO::2016-09-01 06:18:41,077::vdsm::164::vds::(run) Exiting Please have a look. Thanks, Barak. [1]: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/1283/ [2]: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/1077/ [3]: http://jenkins.ovirt.org/job/mom_master_create-rpms-el7-x86_64_created/15/ [4]: http://jenkins.ovirt.org/job/mom_4.0_create-rpms-el7-x86_64_created/11/ [5]: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/1283/artif… [6]: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/1077/artifact… -- Barak Korren bkorren(a)redhat.com RHEV-CI Team

2 2

[ANN] oVirt 4.0.4 First Release Candidate is now available
by Sandro Bonazzola 01 Sep '16

01 Sep '16

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 4.0.4 for testing, as of August 31st, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the first release candidate of the fourth in a series of stabilization updates to the 4.0 series. 4.0.4 brings 7 enhancements and 93 bugfixes, including 33 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is available. [4] * A new oVirt Next Generation Node is available [4]. * A new oVirt Engine Appliance is available for Red Hat Enterprise Linux and CentOS Linux (or similar) * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.4 release highlights: http://www.ovirt.org/release/4.0.4/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.4/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2