[ovirt-users] New oVirt Node 4.0.6.1 network problem with bond and many vlans - Network.service timeout failed

Sandro Bonazzola sbonazzo at redhat.com
Mon May 8 06:46:24 UTC 2017


On Sat, May 6, 2017 at 11:27 PM, Rogério Ceni Coelho <
rogeriocenicoelho at gmail.com> wrote:

> To install 4.1.1 node  i need to update ovirt engine ?


Since 4.0 is unsupported I would recomment to update ovirt-engine to 4.1.1
too.



>
>
> Em Sáb, 6 de mai de 2017 13:07, Sandro Bonazzola <sbonazzo at redhat.com>
> escreveu:
>
>>
>>
>> Il 04/Mag/2017 20:02, "Rogério Ceni Coelho" <rogeriocenicoelho at gmail.com>
>> ha scritto:
>>
>> Hi oVirt admins,
>>
>> Yesterday, i install a new node 4.0.6.1
>>
>>
>> I would suggest to go with 4.1.1 nodes since 4.0 is not supported anymore.
>>
>>
>> and after config network bond (1) + vlans ( about 50 ), network.service
>> failed with timeout as above. All my old and working fine oVirt nodes run
>> 4.0.5 and have the same 5 min timeout on systemd.
>>
>> When i try to run vms on this new server, some networks are ok and some
>> not.
>>
>> I install oVirt Node with 4.0.3 on same server and this problem do not
>> occur.
>>
>> How can i workaround or change timeout to network.service ?
>>
>> In time, there are any way to update oVirt Node to 4.0.5 from 4.0.3
>> install iso ?
>>
>> [root at prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service
>> â— network.service - LSB: Bring up/down networking
>>    Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
>>    Active: failed (Result: timeout) since Thu 2017-05-04 11:29:43 BRT; 3h
>> 12min ago
>>      Docs: man:systemd-sysv-generator(8)
>>   Process: 7574 ExecStart=/etc/rc.d/init.d/network start (code=killed,
>> signal=TERM)
>>
>> May 04 11:29:12 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface o_p_s_a_lb_758:  [  OK  ]
>> May 04 11:29:18 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface o_p_sites_a_755:  [  OK  ]
>> May 04 11:29:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface o_prod_app_757:  [  OK  ]
>> May 04 11:29:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface o_prod_db_756:  [  OK  ]
>> May 04 11:29:38 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface ovirtmgmt:  [  OK  ]
>> *May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br
>> <http://prd-rbs-ovirt-kvm21-poa.rbs.com.br> systemd[1]: network.service
>> start operation timed out. Terminating.*
>> May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to
>> start LSB: Bring up/down networking.
>> May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit
>> network.service entered failed state.
>> May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]:
>> network.service failed.
>> May 04 11:29:43 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[7574]:
>> Bringing up interface paas_1305:
>> [root at prd-rbs-ovirt-kvm21-poa ~]#
>>
>> [root at prd-rbs-ovirt-kvm21-poa ~]# systemctl restart network.service
>> Job for network.service failed because a timeout was exceeded. See
>> "systemctl status network.service" and "journalctl -xe" for details.
>> [root at prd-rbs-ovirt-kvm21-poa ~]# systemctl status network.service
>> â— network.service - LSB: Bring up/down networking
>>    Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
>>    Active: failed (Result: timeout) since Thu 2017-05-04 14:55:34 BRT;
>> 4min 46s ago
>>      Docs: man:systemd-sysv-generator(8)
>>   Process: 40810 ExecStart=/etc/rc.d/init.d/network start (code=killed,
>> signal=TERM)
>>
>> May 04 14:55:21 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [  OK
>>  ]
>> May 04 14:55:23 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]:
>> Bringing up interface o_hlg_db_766:  RTNETLINK answers: File exists
>> May 04 14:55:26 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [  OK
>>  ]
>> May 04 14:55:28 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]:
>> Bringing up interface o_p_s_a_lb_758:  RTNETLINK answers: File exists
>> May 04 14:55:31 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]: [  OK
>>  ]
>> May 04 14:55:33 prd-rbs-ovirt-kvm21-poa.rbs.com.br network[40810]:
>> Bringing up interface o_p_sites_a_755:  RTNETLINK answers: File exists
>> May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]:
>> network.service start operation timed out. Terminating.
>> May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Failed to
>> start LSB: Bring up/down networking.
>> May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]: Unit
>> network.service entered failed state.
>> May 04 14:55:34 prd-rbs-ovirt-kvm21-poa.rbs.com.br systemd[1]:
>> network.service failed.
>> [root at prd-rbs-ovirt-kvm21-poa ~]#
>>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>>


-- 

SANDRO BONAZZOLA

ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D

Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170508/cc51a07f/attachment.html>


More information about the Users mailing list