On 03/31/2015 02:53 PM, Gena Makhomed wrote:
!!!WARNING!!! network did not accessible
after updating CentOS 7.0 inside container to version CentOS 7.1
via # yum update ; reboot
cause:
# tail /var/log/messages:
network: Bringing up loopback interface: [ OK ]
network: Bringing up interface venet0: arping: Device venet0 not
available.
network: Determining if ip address 172.22.22.108 is already in use for
device venet0...
network: arping: Device venet0 not available.
network: ERROR : [/etc/sysconfig/network-scripts/ifup-aliases]
Error, some other host already uses address 172.22.22.108
/etc/sysconfig/network-scripts/ifup-aliases: Error, some other host
already uses address 172.22.22.108.
================================================================
manual workaround: (after each container reboot)
[root@hardware-node]# vzctl enter 108
entered into CT 108
[root@container-108]# ip addr add 172.22.22.108 dev venet0
we need better workaround or complete solution of this regression
A better workaround is to apply this patch:
http://git.openvz.org/?p=vzctl;a=commitdiff;h=24a0a40277542fba5b81
_______________________________________________
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users
