On 09/02/2016 02:24 PM, Yaniv Kaul wrote:
On Fri, Sep 2, 2016 at 3:14 PM, Juan Hernández
<jhernand(a)redhat.com
<mailto:jhernand@redhat.com>> wrote:
On 09/02/2016 02:00 PM, Sandro Bonazzola wrote:
>
>
> On Fri, Sep 2, 2016 at 1:38 PM, Yaniv Kaul <ykaul(a)redhat.com
<mailto:ykaul@redhat.com>
> <mailto:ykaul@redhat.com <mailto:ykaul@redhat.com>>> 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/dfaf35675bee3da1c53b4fd...
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.
>
>
>
>
> Y.
>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at
redhat.com <
http://redhat.com>
<
http://redhat.com>
>
<
https://www.redhat.com/it/about/events/red-hat-open-source-day-2016
<
https://www.redhat.com/it/about/events/red-hat-open-source-day-2016>>
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org <mailto:Devel@ovirt.org>
>
http://lists.ovirt.org/mailman/listinfo/devel
<
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, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.