Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Eyal Edri]

Job fixed [1] with new SDKs.
Thanks.

[1] http://jenkins.ovirt.org/job/ovirt_master_system-tests/491/

On Tue, Sep 6, 2016 at 1:07 PM, Juan Hernández  wrote:

> On 09/06/2016 10:37 AM, Eyal Edri wrote:
> > Glad to hear you found the issue!
> > Let me know when it's merged so we can publish it to the nightlies and
> > rerun the tests.
> >
>
> The fix for the master branch was merged. The artifacts (including RPMs)
> are available in the output of the following jobs:
>
>
> http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-
> artifacts-el7-x86_64/61
>   http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-
> fc24-x86_64/36
>
> > On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández  > > wrote:
> >
> > On 09/05/2016 08:43 PM, Rafael Martins wrote:
> > > - Original Message -
> > >> From: "Juan Hernández"  > >
> > >> To: "Yaniv Kaul" mailto:yk...@redhat.com>>
> > >> Cc: "Sandro Bonazzola"  > >, "Rafael Martins"  > >, "Ondra Machacek"
> > >> mailto:omach...@redhat.com>>, "devel"
> > mailto:devel@ovirt.org>>
> > >> Sent: Friday, September 2, 2016 2:31:42 PM
> > >> Subject: Re: [ovirt-devel] Failure in log collector on master:
> > Failure fetching information about hypervisors from
> > >> API. Error (ValueError): legacy is not a valid RngSource
> > >>
> > >> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
> > >>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández
> > mailto:jhern...@redhat.com>
> > >>> >>
> wrote:
> > >>>
> > >>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
> > >>> >
> > >>> >
> > >>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul
> > mailto:yk...@redhat.com>
> > >>> > >
> > >>> > 
> >  > >>> >
> > >>> > Log:
> > >>> >
> > >>> > 2016-09-02 07:26:52::ERROR::hypervisors::197::root::
> > Failure
> > >>> > fetching information about hypervisors from API.
> > >>> > Error (ValueError): legacy is not a valid RngSource
> > >>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
> > >>> > _get_hypervisors_from_api: legacy is not a valid
> RngSource
> > >>> > 2016-09-02 07:26:52::INFO::__main__::1424::root::
> > Gathering oVirt
> > >>> > Engine information...
> > >>> > 2016-09-02 07:27:03::INFO::__main__::1398::root::
> > Gathering
> > >>> > PostgreSQL the oVirt Engine database and log files from
> > >>> > localhost...
> > >>> > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No
> > hypervisors
> > >>> > were selected, therefore no hypervisor data will be
> > collected.
> > >>> > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log
> > files have
> > >>> > been collected and placed in
> > >>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
> > >>> >
> > >>> >
> > >>> > I am not familiar with this error - first time I've
> > seen it,
> > >>> > while
> > >>> > running on Master, on Lago (with a patch I'm working
> > on - that
> > >>> > adds
> > >>> > DNS and IPv6 support to Lago, nothing more - doesn't
> seem
> > >>> > relevant).
> > >>> > Any idea?
> > >>> >
> > >>> >
> > >>> >
> > >>> > Probably a change in the API.
> > >>> > Rafael can you reproduce?
> > >>> >
> > >>> > Juan, Ondra, any insight?
> > >>> >
> > >>>
> > >>> That means that the API is returning "legacy" as the value
> for
> > >>> something
> > >>> that is declared of type "RngSource", and the valid values
> > for that are
> > >>> "random" and "hwrng". But the API can't return that, at
> > least not
> > >>> version 4 of the API. Are you using engine 4? Can you share
> > the output
> > >>> of the clusters resource?
> > >>>
> > >>>   https://.../ovirt-engine/api/clusters
> > >>>
> > >>>
> > >>> Lago is still using the v3 API.
> > >>> I'm not sure what the log collector is using. I assume[1] it's
> v4.
> > >>>
> > >>> Y.
> > >>> [1]
> > >>>
> > https://github.com/oVirt/ovirt-log-collector/blob/
> dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
> >  dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8>
> > >>>
> > >>
> > >> But the version of the engine 

[ovirt-devel] How can i installed ovirt engine with older version like 4.0.2.2 ?

[??????]

Ovirt current version is 4.0.4 , How can i installed ovirt engine with older 
version like 4.0.2.2 ? Could I install it by "yum install"? 

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

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Juan Hernández]

On 09/06/2016 10:37 AM, Eyal Edri wrote:
> Glad to hear you found the issue!
> Let me know when it's merged so we can publish it to the nightlies and
> rerun the tests.
> 

The fix for the master branch was merged. The artifacts (including RPMs)
are available in the output of the following jobs:


http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-el7-x86_64/61
  http://jenkins.ovirt.org/job/ovirt-engine-sdk_master_build-artifacts-
fc24-x86_64/36

> On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández  > wrote:
> 
> On 09/05/2016 08:43 PM, Rafael Martins wrote:
> > - Original Message -
> >> From: "Juan Hernández"  >
> >> To: "Yaniv Kaul" mailto:yk...@redhat.com>>
> >> Cc: "Sandro Bonazzola"  >, "Rafael Martins"  >, "Ondra Machacek"
> >> mailto:omach...@redhat.com>>, "devel"
> mailto:devel@ovirt.org>>
> >> Sent: Friday, September 2, 2016 2:31:42 PM
> >> Subject: Re: [ovirt-devel] Failure in log collector on master:
> Failure fetching information about hypervisors from
> >> API. Error (ValueError): legacy is not a valid RngSource
> >>
> >> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
> >>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández
> mailto:jhern...@redhat.com>
> >>> >> wrote:
> >>>
> >>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
> >>> >
> >>> >
> >>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul
> mailto:yk...@redhat.com>
> >>> > >
> >>> > 
>  >>> >
> >>> > Log:
> >>> >
> >>> > 2016-09-02 07:26:52::ERROR::hypervisors::197::root::
> Failure
> >>> > fetching information about hypervisors from API.
> >>> > Error (ValueError): legacy is not a valid RngSource
> >>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
> >>> > _get_hypervisors_from_api: legacy is not a valid RngSource
> >>> > 2016-09-02 07:26:52::INFO::__main__::1424::root::
> Gathering oVirt
> >>> > Engine information...
> >>> > 2016-09-02 07:27:03::INFO::__main__::1398::root::
> Gathering
> >>> > PostgreSQL the oVirt Engine database and log files from
> >>> > localhost...
> >>> > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No
> hypervisors
> >>> > were selected, therefore no hypervisor data will be
> collected.
> >>> > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log
> files have
> >>> > been collected and placed in
> >>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
> >>> >
> >>> >
> >>> > I am not familiar with this error - first time I've
> seen it,
> >>> > while
> >>> > running on Master, on Lago (with a patch I'm working
> on - that
> >>> > adds
> >>> > DNS and IPv6 support to Lago, nothing more - doesn't seem
> >>> > relevant).
> >>> > Any idea?
> >>> >
> >>> >
> >>> >
> >>> > Probably a change in the API.
> >>> > Rafael can you reproduce?
> >>> >
> >>> > Juan, Ondra, any insight?
> >>> >
> >>>
> >>> That means that the API is returning "legacy" as the value for
> >>> something
> >>> that is declared of type "RngSource", and the valid values
> for that are
> >>> "random" and "hwrng". But the API can't return that, at
> least not
> >>> version 4 of the API. Are you using engine 4? Can you share
> the output
> >>> of the clusters resource?
> >>>
> >>>   https://.../ovirt-engine/api/clusters
> >>>
> >>>
> >>> Lago is still using the v3 API.
> >>> I'm not sure what the log collector is using. I assume[1] it's v4.
> >>>
> >>> Y.
> >>> [1]
> >>>
> 
> https://github.com/oVirt/ovirt-log-collector/blob/dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
> 
> 
> >>>
> >>
> >> But the version of the engine should be 4, if I understand correctly,
> >> and SDK 4 should work correctly with that version of the engine. In
> >> addition, if it the engine is version 3 the SDK connection should
> have
> >> failed much earlier, during authentication.
> >
> > Hi Juan,
> >
> > I managed to reproduce this with "basic_suite_master" test from
> ovirt-system-tests, that 

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Juan Hernández]

On 09/06/2016 11:49 AM, Yaniv Kaul wrote:
> Interesting that we don't see it on 4.0, saw it's a regression
> introduced somewhere, or a test case we have not seen before?
> Y.
> 

It is a regression that was introduced recently in the master branch of
version 4 of the SDK. The patch that caused the issue wasn't backported
to the 4.0 branch of the SDK, thus you don't see it in 4.0.

> On Tue, Sep 6, 2016 at 11:37 AM, Eyal Edri  > wrote:
> 
> Glad to hear you found the issue!
> Let me know when it's merged so we can publish it to the nightlies
> and rerun the tests.
> 
> On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández  > wrote:
> 
> On 09/05/2016 08:43 PM, Rafael Martins wrote:
> > - Original Message -
> >> From: "Juan Hernández"  >
> >> To: "Yaniv Kaul" mailto:yk...@redhat.com>>
> >> Cc: "Sandro Bonazzola"  >, "Rafael Martins"
> mailto:rmart...@redhat.com>>, "Ondra Machacek"
> >> mailto:omach...@redhat.com>>, "devel"
> mailto:devel@ovirt.org>>
> >> Sent: Friday, September 2, 2016 2:31:42 PM
> >> Subject: Re: [ovirt-devel] Failure in log collector on
> master: Failure fetching information about hypervisors from
> >> API. Error (ValueError): legacy is not a valid RngSource
> >>
> >> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
> >>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández
> mailto:jhern...@redhat.com>
> >>> >>
> wrote:
> >>>
> >>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
> >>> >
> >>> >
> >>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul
> mailto:yk...@redhat.com>
> >>> > >
> >>> > 
>  >>> >
> >>> > Log:
> >>> >
> >>> > 2016-09-02
> 07:26:52::ERROR::hypervisors::197::root:: Failure
> >>> > fetching information about hypervisors from API.
> >>> > Error (ValueError): legacy is not a valid RngSource
> >>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
> >>> > _get_hypervisors_from_api: legacy is not a valid
> RngSource
> >>> > 2016-09-02 07:26:52::INFO::__main__::1424::root::
> Gathering oVirt
> >>> > Engine information...
> >>> > 2016-09-02 07:27:03::INFO::__main__::1398::root::
> Gathering
> >>> > PostgreSQL the oVirt Engine database and log files
> from
> >>> > localhost...
> >>> > 2016-09-02 07:27:05::INFO::__main__::1859::root::
> No hypervisors
> >>> > were selected, therefore no hypervisor data will
> be collected.
> >>> > 2016-09-02 07:27:08::INFO::__main__::1862::root::
> Log files have
> >>> > been collected and placed in
> >>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
> >>> >
> >>> >
> >>> > I am not familiar with this error - first time
> I've seen it,
> >>> > while
> >>> > running on Master, on Lago (with a patch I'm
> working on - that
> >>> > adds
> >>> > DNS and IPv6 support to Lago, nothing more -
> doesn't seem
> >>> > relevant).
> >>> > Any idea?
> >>> >
> >>> >
> >>> >
> >>> > Probably a change in the API.
> >>> > Rafael can you reproduce?
> >>> >
> >>> > Juan, Ondra, any insight?
> >>> >
> >>>
> >>> That means that the API is returning "legacy" as the
> value for
> >>> something
> >>> that is declared of type "RngSource", and the valid
> values for that are
> >>> "random" and "hwrng". But the API can't return that, at
> least not
> >>> version 4 of the API. Are you using engine 4? Can you
> share the output
> >>> of the clusters resource?
> >>>
> >>>   https://.../ovirt-engine/api/clusters
> >>>
> >>>
> >>> Lago is still using the v3 API.
> >>> I'm not sure what the log collector is using. I assume[1]
> it's v4.
> >>>
> >>> Y.
> >>> [1]
> >>>
> 
> https://github.com/oVirt/ovirt-log-collector/blob/dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
>   

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Yaniv Kaul]

Interesting that we don't see it on 4.0, saw it's a regression introduced
somewhere, or a test case we have not seen before?
Y.

On Tue, Sep 6, 2016 at 11:37 AM, Eyal Edri  wrote:

> Glad to hear you found the issue!
> Let me know when it's merged so we can publish it to the nightlies and
> rerun the tests.
>
> On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández 
> wrote:
>
>> On 09/05/2016 08:43 PM, Rafael Martins wrote:
>> > - Original Message -
>> >> From: "Juan Hernández" 
>> >> To: "Yaniv Kaul" 
>> >> Cc: "Sandro Bonazzola" , "Rafael Martins" <
>> rmart...@redhat.com>, "Ondra Machacek"
>> >> , "devel" 
>> >> Sent: Friday, September 2, 2016 2:31:42 PM
>> >> Subject: Re: [ovirt-devel] Failure in log collector on master: Failure
>> fetching information about hypervisors from
>> >> API. Error (ValueError): legacy is not a valid RngSource
>> >>
>> >> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
>> >>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández > >>> > wrote:
>> >>>
>> >>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
>> >>> >
>> >>> >
>> >>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul > >>> > 
>> >>> > >> wrote:
>> >>> >
>> >>> > Log:
>> >>> >
>> >>> > 2016-09-02 07:26:52::ERROR::hypervisors::197::root::
>> Failure
>> >>> > fetching information about hypervisors from API.
>> >>> > Error (ValueError): legacy is not a valid RngSource
>> >>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
>> >>> > _get_hypervisors_from_api: legacy is not a valid RngSource
>> >>> > 2016-09-02 07:26:52::INFO::__main__::1424::root::
>> Gathering oVirt
>> >>> > Engine information...
>> >>> > 2016-09-02 07:27:03::INFO::__main__::1398::root:: Gathering
>> >>> > PostgreSQL the oVirt Engine database and log files from
>> >>> > localhost...
>> >>> > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No
>> hypervisors
>> >>> > were selected, therefore no hypervisor data will be
>> collected.
>> >>> > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log
>> files have
>> >>> > been collected and placed in
>> >>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
>> >>> >
>> >>> >
>> >>> > I am not familiar with this error - first time I've seen it,
>> >>> > while
>> >>> > running on Master, on Lago (with a patch I'm working on -
>> that
>> >>> > adds
>> >>> > DNS and IPv6 support to Lago, nothing more - doesn't seem
>> >>> > relevant).
>> >>> > Any idea?
>> >>> >
>> >>> >
>> >>> >
>> >>> > Probably a change in the API.
>> >>> > Rafael can you reproduce?
>> >>> >
>> >>> > Juan, Ondra, any insight?
>> >>> >
>> >>>
>> >>> That means that the API is returning "legacy" as the value for
>> >>> something
>> >>> that is declared of type "RngSource", and the valid values for
>> that are
>> >>> "random" and "hwrng". But the API can't return that, at least not
>> >>> version 4 of the API. Are you using engine 4? Can you share the
>> output
>> >>> of the clusters resource?
>> >>>
>> >>>   https://.../ovirt-engine/api/clusters
>> >>>
>> >>>
>> >>> Lago is still using the v3 API.
>> >>> I'm not sure what the log collector is using. I assume[1] it's v4.
>> >>>
>> >>> Y.
>> >>> [1]
>> >>> https://github.com/oVirt/ovirt-log-collector/blob/dfaf35675b
>> ee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
>> >>>
>> >>
>> >> But the version of the engine should be 4, if I understand correctly,
>> >> and SDK 4 should work correctly with that version of the engine. In
>> >> addition, if it the engine is version 3 the SDK connection should have
>> >> failed much earlier, during authentication.
>> >
>> > Hi Juan,
>> >
>> > I managed to reproduce this with "basic_suite_master" test from
>> ovirt-system-tests, that uses everything from master branch. This means
>> that engine version is 4, not 3. It seems to be an issue with engine/sdk,
>> as the value is actually stored on engine as "legacy". Here you can find
>> the xml output of the endpoints you asked: https://gist.github.com/rafael
>> martins/60c21e158a9e6453c14a673f77693d61
>> >
>> > Please let me know if you need anything else.
>> >
>> > Thanks,
>> > Rafael
>> >
>>
>> This is a bug in the Python SDK. Should be fixed by the following patch:
>>
>>   Fix reading of lists of elements
>>   https://gerrit.ovirt.org/63385
>>
>> >
>> >>>
>> >>>
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > Y.
>> >>> >
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Sandro Bonazzola
>> >>> > Better technology. Faster innovation. Powered by community
>> >>> > collaboration.
>> >>> > See how it works at redhat.com 
>> >>> > 
>> >>> 

Re: [ovirt-devel] I have this issue when trying to connect to gerrit

[maok...@126.com]

hi,Shlomo Ben David and Eyal Edri:

Is not the problem:
[maokx@maokx ~]$ date
Tue Sep  6 16:42:15 CST 2016
[maokx@maokx ~]$ getenforce
Permissive
[maokx@maokx ~]$ systemctl status iptables
● iptables.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)
[maokx@maokx ~]$ systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) since Tue 2016-09-06 14:31:58 CST; 2h 10min ago
  Process: 851 ExecStart=/usr/sbin/firewalld --nofork --nopid $FIREWALLD_ARGS 
(code=exited, status=0/SUCCESS)
 Main PID: 851 (code=exited, status=0/SUCCESS)

Sep 06 08:57:24 maokx.com systemd[1]: Starting firewalld - dynamic firewall 
daemon...
Sep 06 08:57:30 maokx.com systemd[1]: Started firewalld - dynamic firewall 
daemon.
Sep 06 14:31:57 maokx.com systemd[1]: Stopping firewalld - dynamic firewall 
daemon...
Sep 06 14:31:58 maokx.com systemd[1]: Stopped firewalld - dynamic firewall 
daemon.
[maokx@maokx ~]$ 



maok...@126.com
 
From: Shlomo Ben David
Date: 2016-09-06 16:16
To: Eyal Edri
CC: maok...@126.com; infra; devel
Subject: Re: [ovirt-devel] I have this issue when trying to connect to gerrit
Hi Maokexu,

Its seems that there is some iptables/firewall issue on your machine.
Please make sure that port 29418 (tcp) is open.

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

On Tue, Sep 6, 2016 at 10:52 AM, Eyal Edri  wrote:
Adding infra.

On Tue, Sep 6, 2016 at 10:01 AM, maok...@126.com  wrote:
hi,all:
I have this issue when trying to connect to gerrit:
[maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /home/maokx/.ssh/config
debug1: /home/maokx/.ssh/config line 1: Applying options for gerrit.ovirt.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 56: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to gerrit.ovirt.org [107.22.212.69] port 29418.
debug1: connect to address 107.22.212.69 port 29418: Connection timed out
ssh: connect to host gerrit.ovirt.org port 29418: Connection timed out

[root@maokx ~]# ping gerrit.ovirt.org
PING gerrit.ovirt.org (107.22.212.69) 56(84) bytes of data.
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=1 ttl=25 time=272 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=2 ttl=25 time=285 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=3 ttl=25 time=275 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=4 ttl=25 time=270 ms
^C
--- gerrit.ovirt.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 270.741/275.835/285.228/5.694 ms
[root@maokx ~]# telnet gerrit.ovirt.org 29418
Trying 107.22.212.69...
telnet: connect to address 107.22.212.69: Connection timed out
[root@maokx ~]# 



maok...@126.com

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



-- 
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)

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

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Eyal Edri]

Glad to hear you found the issue!
Let me know when it's merged so we can publish it to the nightlies and
rerun the tests.

On Tue, Sep 6, 2016 at 11:34 AM, Juan Hernández  wrote:

> On 09/05/2016 08:43 PM, Rafael Martins wrote:
> > - Original Message -
> >> From: "Juan Hernández" 
> >> To: "Yaniv Kaul" 
> >> Cc: "Sandro Bonazzola" , "Rafael Martins" <
> rmart...@redhat.com>, "Ondra Machacek"
> >> , "devel" 
> >> Sent: Friday, September 2, 2016 2:31:42 PM
> >> Subject: Re: [ovirt-devel] Failure in log collector on master: Failure
> fetching information about hypervisors from
> >> API. Error (ValueError): legacy is not a valid RngSource
> >>
> >> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
> >>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández  >>> > wrote:
> >>>
> >>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
> >>> >
> >>> >
> >>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul  >>> > 
> >>> > >> wrote:
> >>> >
> >>> > Log:
> >>> >
> >>> > 2016-09-02 07:26:52::ERROR::hypervisors::197::root:: Failure
> >>> > fetching information about hypervisors from API.
> >>> > Error (ValueError): legacy is not a valid RngSource
> >>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
> >>> > _get_hypervisors_from_api: legacy is not a valid RngSource
> >>> > 2016-09-02 07:26:52::INFO::__main__::1424::root:: Gathering
> oVirt
> >>> > Engine information...
> >>> > 2016-09-02 07:27:03::INFO::__main__::1398::root:: Gathering
> >>> > PostgreSQL the oVirt Engine database and log files from
> >>> > localhost...
> >>> > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No
> hypervisors
> >>> > were selected, therefore no hypervisor data will be
> collected.
> >>> > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log files
> have
> >>> > been collected and placed in
> >>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
> >>> >
> >>> >
> >>> > I am not familiar with this error - first time I've seen it,
> >>> > while
> >>> > running on Master, on Lago (with a patch I'm working on -
> that
> >>> > adds
> >>> > DNS and IPv6 support to Lago, nothing more - doesn't seem
> >>> > relevant).
> >>> > Any idea?
> >>> >
> >>> >
> >>> >
> >>> > Probably a change in the API.
> >>> > Rafael can you reproduce?
> >>> >
> >>> > Juan, Ondra, any insight?
> >>> >
> >>>
> >>> That means that the API is returning "legacy" as the value for
> >>> something
> >>> that is declared of type "RngSource", and the valid values for
> that are
> >>> "random" and "hwrng". But the API can't return that, at least not
> >>> version 4 of the API. Are you using engine 4? Can you share the
> output
> >>> of the clusters resource?
> >>>
> >>>   https://.../ovirt-engine/api/clusters
> >>>
> >>>
> >>> Lago is still using the v3 API.
> >>> I'm not sure what the log collector is using. I assume[1] it's v4.
> >>>
> >>> Y.
> >>> [1]
> >>> https://github.com/oVirt/ovirt-log-collector/blob/
> dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
> >>>
> >>
> >> But the version of the engine should be 4, if I understand correctly,
> >> and SDK 4 should work correctly with that version of the engine. In
> >> addition, if it the engine is version 3 the SDK connection should have
> >> failed much earlier, during authentication.
> >
> > Hi Juan,
> >
> > I managed to reproduce this with "basic_suite_master" test from
> ovirt-system-tests, that uses everything from master branch. This means
> that engine version is 4, not 3. It seems to be an issue with engine/sdk,
> as the value is actually stored on engine as "legacy". Here you can find
> the xml output of the endpoints you asked: https://gist.github.com/
> rafaelmartins/60c21e158a9e6453c14a673f77693d61
> >
> > Please let me know if you need anything else.
> >
> > Thanks,
> > Rafael
> >
>
> This is a bug in the Python SDK. Should be fixed by the following patch:
>
>   Fix reading of lists of elements
>   https://gerrit.ovirt.org/63385
>
> >
> >>>
> >>>
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > Y.
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > --
> >>> > Sandro Bonazzola
> >>> > Better technology. Faster innovation. Powered by community
> >>> > collaboration.
> >>> > See how it works at redhat.com 
> >>> > 
> >>> >
> >>>  source-day-2016
> >>>  source-day-2016>>
> >>> >
> >>> >
> >>> > ___
> >>> > Devel mailing list
> >>> > Devel@ovirt.org 

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Eyal Edri]

Any update?
If we can't solve it soon, I suggest to revert the patch for running log
collector in the meantime, because we risk of having new regression coming
it,
and its our only way to verifying if master is broken or not.

Another option is to move master to work with API V4, which we should do
soon probably, but I don't know how long that can take and who can do it.

e/

On Mon, Sep 5, 2016 at 9:43 PM, Rafael Martins  wrote:

> - Original Message -
> > From: "Juan Hernández" 
> > To: "Yaniv Kaul" 
> > Cc: "Sandro Bonazzola" , "Rafael Martins" <
> rmart...@redhat.com>, "Ondra Machacek"
> > , "devel" 
> > Sent: Friday, September 2, 2016 2:31:42 PM
> > Subject: Re: [ovirt-devel] Failure in log collector on master: Failure
> fetching information about hypervisors from
> > API. Error (ValueError): legacy is not a valid RngSource
> >
> > On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
> > > On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández  > > > wrote:
> > >
> > > On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
> > > >
> > > >
> > > > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul  > > > 
> > > > >> wrote:
> > > >
> > > > Log:
> > > >
> > > > 2016-09-02 07:26:52::ERROR::hypervisors::197::root:: Failure
> > > > fetching information about hypervisors from API.
> > > > Error (ValueError): legacy is not a valid RngSource
> > > > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
> > > > _get_hypervisors_from_api: legacy is not a valid RngSource
> > > > 2016-09-02 07:26:52::INFO::__main__::1424::root:: Gathering
> oVirt
> > > > Engine information...
> > > > 2016-09-02 07:27:03::INFO::__main__::1398::root:: Gathering
> > > > PostgreSQL the oVirt Engine database and log files from
> > > > localhost...
> > > > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No
> hypervisors
> > > > were selected, therefore no hypervisor data will be
> collected.
> > > > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log files
> have
> > > > been collected and placed in
> > > > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
> > > >
> > > >
> > > > I am not familiar with this error - first time I've seen it,
> > > > while
> > > > running on Master, on Lago (with a patch I'm working on -
> that
> > > > adds
> > > > DNS and IPv6 support to Lago, nothing more - doesn't seem
> > > > relevant).
> > > > Any idea?
> > > >
> > > >
> > > >
> > > > Probably a change in the API.
> > > > Rafael can you reproduce?
> > > >
> > > > Juan, Ondra, any insight?
> > > >
> > >
> > > That means that the API is returning "legacy" as the value for
> > > something
> > > that is declared of type "RngSource", and the valid values for
> that are
> > > "random" and "hwrng". But the API can't return that, at least not
> > > version 4 of the API. Are you using engine 4? Can you share the
> output
> > > of the clusters resource?
> > >
> > >   https://.../ovirt-engine/api/clusters
> > >
> > >
> > > Lago is still using the v3 API.
> > > I'm not sure what the log collector is using. I assume[1] it's v4.
> > >
> > > Y.
> > > [1]
> > > https://github.com/oVirt/ovirt-log-collector/blob/
> dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
> > >
> >
> > But the version of the engine should be 4, if I understand correctly,
> > and SDK 4 should work correctly with that version of the engine. In
> > addition, if it the engine is version 3 the SDK connection should have
> > failed much earlier, during authentication.
>
> Hi Juan,
>
> I managed to reproduce this with "basic_suite_master" test from
> ovirt-system-tests, that uses everything from master branch. This means
> that engine version is 4, not 3. It seems to be an issue with engine/sdk,
> as the value is actually stored on engine as "legacy". Here you can find
> the xml output of the endpoints you asked: https://gist.github.com/
> rafaelmartins/60c21e158a9e6453c14a673f77693d61
>
> Please let me know if you need anything else.
>
> Thanks,
> Rafael
>
>
> > >
> > >
> > > >
> > > >
> > > >
> > > >
> > > > Y.
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sandro Bonazzola
> > > > Better technology. Faster innovation. Powered by community
> > > > collaboration.
> > > > See how it works at redhat.com 
> > > > 
> > > >
> > >  source-day-2016
> > >  source-day-2016>>
> > > >
> > > >
> > > > ___
> > > > Devel mailing list
> > > > Devel@ovi

Re: [ovirt-devel] Failure in log collector on master: Failure fetching information about hypervisors from API. Error (ValueError): legacy is not a valid RngSource

[Juan Hernández]

On 09/05/2016 08:43 PM, Rafael Martins wrote:
> - Original Message -
>> From: "Juan Hernández" 
>> To: "Yaniv Kaul" 
>> Cc: "Sandro Bonazzola" , "Rafael Martins" 
>> , "Ondra Machacek"
>> , "devel" 
>> Sent: Friday, September 2, 2016 2:31:42 PM
>> Subject: Re: [ovirt-devel] Failure in log collector on master: Failure 
>> fetching information about hypervisors from
>> API. Error (ValueError): legacy is not a valid RngSource
>>
>> On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
>>> On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández >> > wrote:
>>>
>>> On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
>>> >
>>> >
>>> > On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul >> > 
>>> > >> wrote:
>>> >
>>> > Log:
>>> >
>>> > 2016-09-02 07:26:52::ERROR::hypervisors::197::root:: Failure
>>> > fetching information about hypervisors from API.
>>> > Error (ValueError): legacy is not a valid RngSource
>>> > 2016-09-02 07:26:52::ERROR::__main__::1147::root::
>>> > _get_hypervisors_from_api: legacy is not a valid RngSource
>>> > 2016-09-02 07:26:52::INFO::__main__::1424::root:: Gathering oVirt
>>> > Engine information...
>>> > 2016-09-02 07:27:03::INFO::__main__::1398::root:: Gathering
>>> > PostgreSQL the oVirt Engine database and log files from
>>> > localhost...
>>> > 2016-09-02 07:27:05::INFO::__main__::1859::root:: No hypervisors
>>> > were selected, therefore no hypervisor data will be collected.
>>> > 2016-09-02 07:27:08::INFO::__main__::1862::root:: Log files have
>>> > been collected and placed in
>>> > /tmp/sosreport-LogCollector-20160902072705.tar.xz.
>>> >
>>> >
>>> > I am not familiar with this error - first time I've seen it,
>>> > while
>>> > running on Master, on Lago (with a patch I'm working on - that
>>> > adds
>>> > DNS and IPv6 support to Lago, nothing more - doesn't seem
>>> > relevant).
>>> > Any idea?
>>> >
>>> >
>>> >
>>> > Probably a change in the API.
>>> > Rafael can you reproduce?
>>> >
>>> > Juan, Ondra, any insight?
>>> >
>>>
>>> That means that the API is returning "legacy" as the value for
>>> something
>>> that is declared of type "RngSource", and the valid values for that are
>>> "random" and "hwrng". But the API can't return that, at least not
>>> version 4 of the API. Are you using engine 4? Can you share the output
>>> of the clusters resource?
>>>
>>>   https://.../ovirt-engine/api/clusters
>>>
>>>
>>> Lago is still using the v3 API.
>>> I'm not sure what the log collector is using. I assume[1] it's v4.
>>>
>>> Y.
>>> [1]
>>> https://github.com/oVirt/ovirt-log-collector/blob/dfaf35675bee3da1c53b4fd74b816efafa13d070/src/helper/hypervisors.py#L8
>>>
>>
>> But the version of the engine should be 4, if I understand correctly,
>> and SDK 4 should work correctly with that version of the engine. In
>> addition, if it the engine is version 3 the SDK connection should have
>> failed much earlier, during authentication.
> 
> Hi Juan,
> 
> I managed to reproduce this with "basic_suite_master" test from 
> ovirt-system-tests, that uses everything from master branch. This means that 
> engine version is 4, not 3. It seems to be an issue with engine/sdk, as the 
> value is actually stored on engine as "legacy". Here you can find the xml 
> output of the endpoints you asked: 
> https://gist.github.com/rafaelmartins/60c21e158a9e6453c14a673f77693d61
> 
> Please let me know if you need anything else.
> 
> Thanks,
> Rafael
> 

This is a bug in the Python SDK. Should be fixed by the following patch:

  Fix reading of lists of elements
  https://gerrit.ovirt.org/63385

> 
>>>
>>>
>>> >
>>> >
>>> >
>>> >
>>> > Y.
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > 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
>>> 
>>> >
>>>
>>>
>>> --
>>> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
>>> 3ºD, 28016 Madrid, Spain
>>> Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat
>>> S.L.
>>>
>>>
>>
>>
>> --
>> Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, plan

Re: [ovirt-devel] I have this issue when trying to connect to gerrit

[Shlomo Ben David]

Hi Maokexu,

Its seems that there is some iptables/firewall issue on your machine.
Please make sure that port 29418 (tcp) is open.

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

On Tue, Sep 6, 2016 at 10:52 AM, Eyal Edri  wrote:

> Adding infra.
>
> On Tue, Sep 6, 2016 at 10:01 AM, maok...@126.com  wrote:
>
>> hi,all:
>> I have this issue when trying to connect to gerrit:
>> [maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
>> OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
>> debug1: Reading configuration data /home/maokx/.ssh/config
>> debug1: /home/maokx/.ssh/config line 1: Applying options for
>> gerrit.ovirt.org
>> debug1: Reading configuration data /etc/ssh/ssh_config
>> debug1: /etc/ssh/ssh_config line 56: Applying options for *
>> debug2: ssh_connect: needpriv 0
>> debug1: Connecting to gerrit.ovirt.org [107.22.212.69] port 29418.
>> debug1: connect to address 107.22.212.69 port 29418: Connection timed out
>> ssh: connect to host gerrit.ovirt.org port 29418: Connection timed out
>>
>> [root@maokx ~]# ping gerrit.ovirt.org
>> PING gerrit.ovirt.org (107.22.212.69) 56(84) bytes of data.
>> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=1 t
>> tl=25 time=272 ms
>> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=2 t
>> tl=25 time=285 ms
>> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=3 t
>> tl=25 time=275 ms
>> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=4 t
>> tl=25 time=270 ms
>> ^C
>> --- gerrit.ovirt.org ping statistics ---
>> 4 packets transmitted, 4 received, 0% packet loss, time 3006ms
>> rtt min/avg/max/mdev = 270.741/275.835/285.228/5.694 ms
>> [root@maokx ~]# telnet gerrit.ovirt.org 29418
>> Trying 107.22.212.69...
>> telnet: connect to address 107.22.212.69: Connection timed out
>> [root@maokx ~]#
>>
>> --
>> maok...@126.com
>>
>> ___
>> Devel mailing list
>> Devel@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>>
>
>
>
> --
> 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)
>
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

Re: [ovirt-devel] I have this issue when trying to connect to gerrit

[Eyal Edri]

Adding infra.

On Tue, Sep 6, 2016 at 10:01 AM, maok...@126.com  wrote:

> hi,all:
> I have this issue when trying to connect to gerrit:
> [maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
> OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
> debug1: Reading configuration data /home/maokx/.ssh/config
> debug1: /home/maokx/.ssh/config line 1: Applying options for
> gerrit.ovirt.org
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 56: Applying options for *
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to gerrit.ovirt.org [107.22.212.69] port 29418.
> debug1: connect to address 107.22.212.69 port 29418: Connection timed out
> ssh: connect to host gerrit.ovirt.org port 29418: Connection timed out
>
> [root@maokx ~]# ping gerrit.ovirt.org
> PING gerrit.ovirt.org (107.22.212.69) 56(84) bytes of data.
> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=1
> ttl=25 time=272 ms
> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=2
> ttl=25 time=285 ms
> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=3
> ttl=25 time=275 ms
> 64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=4
> ttl=25 time=270 ms
> ^C
> --- gerrit.ovirt.org ping statistics ---
> 4 packets transmitted, 4 received, 0% packet loss, time 3006ms
> rtt min/avg/max/mdev = 270.741/275.835/285.228/5.694 ms
> [root@maokx ~]# telnet gerrit.ovirt.org 29418
> Trying 107.22.212.69...
> telnet: connect to address 107.22.212.69: Connection timed out
> [root@maokx ~]#
>
> --
> maok...@126.com
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
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)
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel

[ovirt-devel] I have this issue when trying to connect to gerrit

[maok...@126.com]

hi,all:
I have this issue when trying to connect to gerrit:
[maokx@maokx ~]$ ssh -vv gerrit.ovirt.org
OpenSSH_6.6.1, OpenSSL 1.0.1e-fips 11 Feb 2013
debug1: Reading configuration data /home/maokx/.ssh/config
debug1: /home/maokx/.ssh/config line 1: Applying options for gerrit.ovirt.org
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 56: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to gerrit.ovirt.org [107.22.212.69] port 29418.
debug1: connect to address 107.22.212.69 port 29418: Connection timed out
ssh: connect to host gerrit.ovirt.org port 29418: Connection timed out

[root@maokx ~]# ping gerrit.ovirt.org
PING gerrit.ovirt.org (107.22.212.69) 56(84) bytes of data.
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=1 ttl=25 time=272 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=2 ttl=25 time=285 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=3 ttl=25 time=275 ms
64 bytes from gerrit.ovirt.org (107.22.212.69): icmp_seq=4 ttl=25 time=270 ms
^C
--- gerrit.ovirt.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 270.741/275.835/285.228/5.694 ms
[root@maokx ~]# telnet gerrit.ovirt.org 29418
Trying 107.22.212.69...
telnet: connect to address 107.22.212.69: Connection timed out
[root@maokx ~]# 



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