On Mon, Feb 8, 2021 at 12:33 PM lejeczek via Users <
users@ovirt.org> wrote:
On 08/02/2021 06:44, Ales Musil wrote:
>
>
> On Mon, Feb 8, 2021 at 12:18 AM lejeczek via Users
> <users@ovirt.org <mailto:users@ovirt.org>> wrote:
>
> Hi guys,
>
> I'm trying oVirt in a KVM and I get this:
> ...
> [ INFO ] The host has been set in non_operational
> status,
> deployment errors: code 505: Host c8ovirt1.private.road
> installation failed. Failed to configure management
> network
> on the host., code 519: Host c8ovirt1.private.road
> does
> not comply with the cluster road networks, the following
> networks are missing on host: 'ovirtmgmt', code 1120:
> Failed to configure management network on host
> c8ovirt1.private.road due to setup networks failure.,
> code 9000: Failed to verify Power Management
> configuration
> for Host c8ovirt1.private.road., code 10802: VDSM
> c8ovirt1.private.road command HostSetupNetworksVDS
> failed:
> Internal JSON-RPC error: {'reason': 'Failed to find
> interface to with route table ID 254 to store route
> rules'},
> ...
>
> How much of a worry is it and how to fix such KVM vm so
> oVirt would be happy?
> many thanks, L.
> _______________________________________________
> Users mailing list -- users@ovirt.org
> <mailto:users@ovirt.org>
> To unsubscribe send an email to users-leave@ovirt.org
> <mailto:users-leave@ovirt.org>
> Privacy Statement:
> https://www.ovirt.org/privacy-policy.html
> <https://www.ovirt.org/privacy-policy.html>
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> <https://www.ovirt.org/community/about/community-guidelines/>
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZHD5KCPMKXOSPFK7E6JWA27H6SPHHO6/
> <https://lists.ovirt.org/archives/list/users@ovirt.org/message/UZHD5KCPMKXOSPFK7E6JWA27H6SPHHO6/>
>
>
>
> Hello,
>
> usually KVM hosts work without any issues for me, as long
> as there is a single interface that will act as a
> management network.
>
> Can you please share relevant part from supervdsm.log?
>
> Thank you.
> Regards,
> Ales
>
>
Just in case it's not clear from that log snippet I pasted,
should have made it clearer, it's deployment of the engine.
KVM vm has only on single iface.
...
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Generate
the error message from the engine events]
[ INFO ] ok: [localhost]
[ INFO ] The host has been set in non_operational status,
deployment errors: code 505: Host c8ovirt1.private.road
installation failed. Failed to configure management network
on the host., code 519: Host c8ovirt1.private.road does
not comply with the cluster road networks, the following
networks are missing on host: 'ovirtmgmt', code 1120:
Failed to configure management network on host
c8ovirt1.private.road due to setup networks failure.,
code 9000: Failed to verify Power Management configuration
for Host c8ovirt1.private.road., code 10802: VDSM
c8ovirt1.private.road command HostSetupNetworksVDS failed:
Internal JSON-RPC error: {'reason': 'Failed to find
interface to with route table ID 254 to store route rules'},
[ INFO ] skipping: [localhost]
[ INFO ] You can now connect to
https://c8ovirt1.private.road:6900/ovirt-engine/ and check
the status of this host and eventually remediate it, please
continue only when the host is listed as 'up'
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create
temporary lock file]
[ INFO ] changed: [localhost]
[ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Pause
execution until /tmp/ansible.con_3ppb_he_setup_lock is
removed, delete it once ready to proceed]
...
and tail of supervdsm.log
...
(cwd None)
MainThread::DEBUG::2021-02-07
18:03:40,618::cmdutils::138::root::(exec_cmd) SUCCESS: <err>
= b''; <rc> = 0
MainThread::DEBUG::2021-02-07
18:03:40,618::cmdutils::130::root::(exec_cmd)
/usr/sbin/lldptool -ping (cwd None)
MainThread::DEBUG::2021-02-07
18:03:40,668::cmdutils::138::root::(exec_cmd) SUCCESS: <err>
= b''; <rc> = 0
MainThread::DEBUG::2021-02-07
18:03:40,669::cmdutils::130::root::(exec_cmd)
/usr/sbin/lldptool get-lldp -i ens3 adminStatus (cwd None)
MainThread::DEBUG::2021-02-07
18:03:40,672::cmdutils::138::root::(exec_cmd) SUCCESS: <err>
= b''; <rc> = 0
MainThread::DEBUG::2021-02-07
18:03:40,672::cmdutils::130::root::(exec_cmd)
/usr/sbin/lldptool set-lldp -i ens3 adminStatus=rx (cwd None)
MainThread::DEBUG::2021-02-07
18:03:40,674::cmdutils::138::root::(exec_cmd) SUCCESS: <err>
= b''; <rc> = 0
MainThread::DEBUG::2021-02-07
18:03:40,675::supervdsm_server::311::SuperVdsm.Server::(main)
Started serving super vdsm object
restore-net::INFO::2021-02-07
18:03:43,508::restore_net_config::290::root::(restore)
starting network restoration.
restore-net::DEBUG::2021-02-07
18:03:43,510::cmdutils::130::root::(exec_cmd) /sbin/tc qdisc
show (cwd None)
restore-net::DEBUG::2021-02-07
18:03:43,520::cmdutils::138::root::(exec_cmd) SUCCESS: <err>
= b''; <rc> = 0
restore-net::DEBUG::2021-02-07
18:03:43,579::context::144::root::(register_async) Async
action: Retrieve applied config: ethernet ens3 started
restore-net::DEBUG::2021-02-07
18:03:43,579::context::144::root::(register_async) Async
action: Retrieve applied config: bridge virbr0 started
restore-net::DEBUG::2021-02-07
18:03:43,579::context::144::root::(register_async) Async
action: Retrieve applied config: tun vnet0 started
restore-net::DEBUG::2021-02-07
18:03:43,582::context::153::root::(finish_async) Async
action: Retrieve applied config: ethernet ens3 finished
restore-net::DEBUG::2021-02-07
18:03:43,582::context::153::root::(finish_async) Async
action: Retrieve applied config: bridge virbr0 finished
restore-net::DEBUG::2021-02-07
18:03:43,583::context::153::root::(finish_async) Async
action: Retrieve applied config: tun vnet0 finished
restore-net::DEBUG::2021-02-07
18:03:43,600::context::144::root::(register_async) Async
action: Retrieve applied config: ethernet ens3 started
restore-net::DEBUG::2021-02-07
18:03:43,600::context::144::root::(register_async) Async
action: Retrieve applied config: bridge virbr0 started
restore-net::DEBUG::2021-02-07
18:03:43,600::context::144::root::(register_async) Async
action: Retrieve applied config: tun vnet0 started
restore-net::DEBUG::2021-02-07
18:03:43,602::context::153::root::(finish_async) Async
action: Retrieve applied config: ethernet ens3 finished
restore-net::DEBUG::2021-02-07
18:03:43,602::context::153::root::(finish_async) Async
action: Retrieve applied config: bridge virbr0 finished
restore-net::DEBUG::2021-02-07
18:03:43,602::context::153::root::(finish_async) Async
action: Retrieve applied config: tun vnet0 finished
restore-net::INFO::2021-02-07
18:03:43,610::restore_net_config::89::root::(unified_restoration)
Remove networks ({}) and bonds ({}).
restore-net::INFO::2021-02-07
18:03:43,610::restore_net_config::96::root::(unified_restoration)
Setup networks ({}) and bonds ({}).
restore-net::INFO::2021-02-07
18:03:43,610::restore_net_config::297::root::(restore)
restoration completed successfully.
regards, L.
This looks like a log after reboot. Is there a setup networks call with the failure?
Thanks.
Regards,
Ales
> --
>
> Ales Musil
>
> Software Engineer - RHV Network
>
> Red Hat EMEA <https://www.redhat.com>
>
> amusil@redhat.com <mailto:amusil@redhat.com> IM: amusil
>
> <https://red.ht/sig>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KJH7LEPTQMJVUZQWC45HQEUGVIV2Y2ZO/
