Greetings, ----- Original Message ----- > > !!!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
Yeah, we were discussing this. It has already been fixed in the dev version of vzctl but it hasn't been pushed to a release yet. For more info, see: https://bugzilla.openvz.org/show_bug.cgi?id=3169 In the mean time, you can fix it yourself by editing the /etc/dists/scripts/redhat-add_ip.sh file and adding the line: ARPCHECK=\"no\" You have to add it twice as seen here: http://git.openvz.org/?p=vzctl;a=commitdiff;h=24a0a40277542fba;hp=f4d35dde74fd74ab068e34748919ac0b9a6a21aa I noticed it with the Fedora 21 beta OS Template... and then when I upgraded my contributed Oracle 7.1 OS Template. I guess CentOS 7.1 just came out? :) TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
