November 2016 - Devel - oVirt List Archives

engine 4.0 build broken
by Piotr Kliczewski 03 Nov '16

03 Nov '16

Sometime ago we merged [1] which broke the build [2]. Please revert or push a fix. Thanks, Piotr [1] https://gerrit.ovirt.org/#/c/64892/ [2] http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-patch-el7-x86_64/961/

1 0

[ANN] oVirt 4.0.5 Fifth Release Candidate is now available
by Sandro Bonazzola 02 Nov '16

02 Nov '16

The oVirt Project is pleased to announce the availability of oVirt 4.0.5 fifth release candidate for testing, as of November 2nd, 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 fifth release candidate of the fifth in a series of stabilization updates to the 4.0 series. 4.0.5 brings 15 enhancements and 85 bugfixes, including 41 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 will be available soon [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.5 release highlights: http://www.ovirt.org/release/4.0.5/ (may take a while to be updated due to oVirt website builder down [6]) * 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.5/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors [6] http://lists.ovirt.org/pipermail/infra/2016-November/018531.html -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Password for database in ovirt-system-tests/basic_suite_3.6
by Dominik Holler 02 Nov '16

02 Nov '16

Hi, I want to have a look at the database in ovirt-system-tests/basic_suite_3.6, but unfortunately I do not know the password for the database. I tried already various ones by: [root@lago_basic_suite_3_6_engine ~]# psql -U engine -p 5432 -h 127.0.0.1 Can anyone give me a hint how to get the password for the database? Thanks, Dominik

3 3

[ACTION REQUIRED][URGENT] Broken dependency on oVirt engine 4.0.5.5: missing vdsm-jsonrpc-java >= 1.2.7
by Sandro Bonazzola 02 Nov '16

02 Nov '16

Failed to build transaction : ovirt-engine-backend-4.0.5.5-1.el7.centos.noarch requires vdsm-jsonrpc-java >= 1.2.7 1.2.7 is not yet tagged: * f212665 - (HEAD -> ovirt-4.0, origin/ovirt-4.0) do not reconnect to policy reset (7 days ago) <Piotr Kliczewski> * fe8261b - (tag: v1.2.6) version bump (3 weeks ago) <Piotr Kliczewski> Please either revert the requirement on new vdsm-jsonrpc-java or provide vdsm-jsonrpc-java >= 1.2.7 as soon as possible. Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 2

[ACTION REQUIRED] oVirt 4.0.5 RC5 build starting
by Lev Veyde 01 Nov '16

01 Nov '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. - add your builds to releng-tools/releases/ovirt-4.0.5_rc5.conf within releng-tools project Thanks in advance, Lev Veyde.

1 0