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/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:

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

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

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

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

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

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

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

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/05/2016 08:43 PM, Rafael Martins wrote: > - Original Message - >> From: "Juan Hernández" >> To: "Yaniv Kaul" >> Cc: "Sandro Bonazzola" , "Rafael Martins" >> , "Ondra Machacek" >>

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

- Original Message - > From: "Juan Hernández" > To: "Yaniv Kaul" > Cc: "Sandro Bonazzola" , "Rafael Martins" > , "Ondra Machacek" > , "devel" > Sent: Friday, September

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

- Original Message - > From: "Sandro Bonazzola" > To: "Yaniv Kaul" , "Rafael Martins" , > "Ondra Machacek" , > "Juan Antonio Hernandez Fernandez" > Cc: "devel" > Sent:

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

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

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

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: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. >

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

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

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