Re: [ovirt-devel] [ovirt-announce] [ANN] oVirt 4.0.4 RC2 is now available

2016-09-09 Thread Simone Tiraboschi 
On Fri, Sep 9, 2016 at 12:02 PM, Simone Tiraboschi 
wrote:

> We had a quick re-spin of the engine to include a fix for
> https://bugzilla.redhat.com/1372950
> The new engine version is 4.0.4.2; a new oVirt Engine Appliance is also
> available, oVirt Live ISO will follow.
>

ovirt-live 4.0.4_rc2.1 is also in.


>
>
> On Wed, Sep 7, 2016 at 10:28 PM, Rafael Martins 
> wrote:
>
>> The oVirt Project is pleased to announce the availability of the Second
>> Release Candidate of oVirt 4.0.4 for testing, as of September 7th, 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. 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.or
>> g/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
>>
>> --
>> Rafael Martins
>> ___
>> Announce mailing list
>> annou...@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/announce
>>
>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] Fwd: F26 System Wide Change: DNF 2.0

2016-09-09 Thread Vinzenz Feenstra 

> On Sep 9, 2016, at 5:04 PM, Sandro Bonazzola  wrote:
> 
> FYI
> This affects engine-setup, ovirt-hosted-engine-setup, ovirt-host-deploy and 
> any other tool based on OTOPI in 4.2 time frame.

TLDR: 
- Reintroduction of YUM’s configuration options includepkgs and excludepkgs
- DNF group install --with-optional option

So this shouldn’t be too big of an impact, if at all

> 
> -- Forwarded message --
> From: Jan Kurik >
> Date: Fri, Sep 9, 2016 at 4:49 PM
> Subject: F26 System Wide Change: DNF 2.0
> To: Development discussions related to Fedora  >, 
> devel-annou...@lists.fedoraproject.org 
> 
> 
> 
> = Proposed System Wide Change: DNF 2.0 =
> https://fedoraproject.org/wiki/Changes/DNF-2.0 
> 
> 
> 
> Change owner(s):
> * Jan Silhan 
> * Michal Luscon 
> * Igor Gnatenko 
> 
> 
> DNF rebase to version 2.0.
> 
> 
> == Detailed Description ==
> DNF-2.0 is the next upcoming major version of DNF package manager.
> Unfortunately, it brings some incompatibilities with previous version
> of DNF (DNF-1) which were either needed to preserve compatibility with
> YUM CLI or where bigger redesigns were needed. A list of identified
> incompatible changes can be found here
> http://dnf.readthedocs.io/en/latest/dnf-1_vs_dnf-2.html 
> 
> 
> 
> == Scope ==
> Proposal owners:
> * complete release notes
> * deliver DNF-2.0 stack to Rawhide
> 
> Other developers:
> * Owners of 3rd party DNF plugins or components depending on DNF
> should check and adjust their packages otherwise they may not work
> with DNF-2.0.
> 
> Release engineering:
> * All release engineering tools that depends on DNF should be tested
> against DNF-2.0.
> --
> Jan Kuřík
> Platform & Fedora Program Manager
> Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
> --
> devel mailing list
> de...@lists.fedoraproject.org 
> https://lists.fedoraproject.org/admin/lists/de...@lists.fedoraproject.org 
> 
> 
> 
> 
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com 
>  
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] Fwd: F26 System Wide Change: DNF 2.0

2016-09-09 Thread Sandro Bonazzola 
FYI
This affects engine-setup, ovirt-hosted-engine-setup, ovirt-host-deploy and
any other tool based on OTOPI in 4.2 time frame.

-- Forwarded message --
From: Jan Kurik 
Date: Fri, Sep 9, 2016 at 4:49 PM
Subject: F26 System Wide Change: DNF 2.0
To: Development discussions related to Fedora ,
devel-annou...@lists.fedoraproject.org


= Proposed System Wide Change: DNF 2.0 =
https://fedoraproject.org/wiki/Changes/DNF-2.0


Change owner(s):
* Jan Silhan 
* Michal Luscon 
* Igor Gnatenko 


DNF rebase to version 2.0.


== Detailed Description ==
DNF-2.0 is the next upcoming major version of DNF package manager.
Unfortunately, it brings some incompatibilities with previous version
of DNF (DNF-1) which were either needed to preserve compatibility with
YUM CLI or where bigger redesigns were needed. A list of identified
incompatible changes can be found here
http://dnf.readthedocs.io/en/latest/dnf-1_vs_dnf-2.html


== Scope ==
Proposal owners:
* complete release notes
* deliver DNF-2.0 stack to Rawhide

Other developers:
* Owners of 3rd party DNF plugins or components depending on DNF
should check and adjust their packages otherwise they may not work
with DNF-2.0.

Release engineering:
* All release engineering tools that depends on DNF should be tested
against DNF-2.0.
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
--
devel mailing list
de...@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/de...@lists.fedoraproject.org



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] test-repo_ovirt_experimental_master job - failed

2016-09-09 Thread Yaniv Kaul 
Indeed, this is the log collector. I wonder if we collect its logs...
Y.


On Thu, Sep 8, 2016 at 6:54 PM, Eyal Edri  wrote:

> I'm pretty sure lago or ovirt system tests aren't doing it but its the log
> collector which is running during that test, I'm not near a computer so
> can't verify it yet.
>
> On Sep 8, 2016 6:05 PM, "Nir Soffer"  wrote:
>
>> On Thu, Sep 8, 2016 at 5:45 PM, Eyal Edri  wrote:
>> > Adding devel.
>> >
>> > On Thu, Sep 8, 2016 at 5:43 PM, Shlomo Ben David 
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> Job [1] is failing with the following error:
>> >>
>> >> lago.ssh: DEBUG: Command 8de75538 on lago_basic_suite_master_engine
>> >> errors:
>> >>  ERROR: Failed to collect logs from: 192.168.200.2; /bin/ls:
>> >> /rhev/data-center/mnt/blockSD/eb8c9f48-5f23-48dc-ab7d-945189
>> 0fd422/master/tasks/1350bed7-443e-4ae6-ae1f-9b24d18c70a8.temp:
>> >> No such file or directory
>> >> /bin/ls: cannot open directory
>> >> /rhev/data-center/mnt/blockSD/eb8c9f48-5f23-48dc-ab7d-945189
>> 0fd422/master/tasks/1350bed7-443e-4ae6-ae1f-9b24d18c70a8.temp:
>> >> No such file or directory
>>
>> This looks like a lago issue - it should never read anything inside /rhev
>>
>> This is a private directory for vdsm, no other process should ever depend
>> on the content inside this directory, or even on the fact that it exists.
>>
>> In particular, /rhev/data-center/mnt/blockSD/*/master/tasks/*.temp
>> Is not a log file, and lago should not collect it.
>>
>> Nir
>>
>> >> lago.utils: ERROR: Error while running thread
>> >> Traceback (most recent call last):
>> >>   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 53, in
>> >> _ret_via_queue
>> >> queue.put({'return': func()})
>> >>   File
>> >> "/home/jenkins/workspace/test-repo_ovirt_experimental_master
>> /ovirt-system-tests/basic_suite_master/test-scenarios/002_bootstrap.py",
>> >> line 493, in log_collector
>> >> result.code, 0, 'log collector failed. Exit code is %s' %
>> result.code
>> >>   File "/usr/lib/python2.7/site-packages/nose/tools/trivial.py", line
>> 29,
>> >> in eq_
>> >> raise AssertionError(msg or "%r != %r" % (a, b))
>> >> AssertionError: log collector failed. Exit code is 2
>> >>
>> >>
>> >> * The previous issue already fixed (SDK) and now we have a new issue on
>> >> the same area.
>> >>
>> >>
>> >> [1] -
>> >> http://jenkins.ovirt.org/view/experimental%20jobs/job/test-r
>> epo_ovirt_experimental_master/1462/testReport/(root)/002_
>> bootstrap/add_secondary_storage_domains/
>> >>
>> >>
>> >> 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
>> >
>> >
>> >
>> >
>> > --
>> > Eyal Edri
>> > Associate Manager
>> > RHV DevOps
>> > EMEA ENG Virtualization R
>> > Red Hat Israel
>> >
>> > phone: +972-9-7692018
>> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
>> >
>> > ___
>> > Devel mailing list
>> > Devel@ovirt.org
>> > http://lists.ovirt.org/mailman/listinfo/devel
>>
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel