Spent a couple hours today working on testing a couple restores of openvz/lxc containers and ran into some network trouble. I was able to figure out the cause and hope the below helps others as well.
Symptoms were network config would not be written to the container but you could manually configure CentOS 7.
Cause: Undefined subroutine &PVE::Network::is_ip_in_cidr
Solution: manually update perl package PVE::Network in /usr/share/perl5/PVE/Network.pm from GIT at *** won't let me post anything with a link
Why: It appears there were some changes made to the /usr/share/perl5/PVE/LXC/Setup/Redhat.pm perl module which depended on an updated /usr/share/perl5/PVE/Network.pm that were not yet available via apt-get update & upgrade, specifically the is_ip_in_cidr function and was causing an error on lxc container start. Once this was updated that worked - mostly. But that was another problem (maybe with something specific to my environemnt)
Version: ProxMox V4 updated to latest via apt-get update & upgrade.
This was pretty much a fresh install to which then I did an update on and had this issue. If there is a place I should file a bug report to let me know. It's working fine on my system after this quick fix which took a bit to track down.
I generated a patch to save some people some digging - hope it helps.
(edit: never mind the site wouldn't allow me to include that with the "CODE" tag as i guess it appeared to look like links or something.)
Symptoms were network config would not be written to the container but you could manually configure CentOS 7.
Cause: Undefined subroutine &PVE::Network::is_ip_in_cidr
Solution: manually update perl package PVE::Network in /usr/share/perl5/PVE/Network.pm from GIT at *** won't let me post anything with a link
Why: It appears there were some changes made to the /usr/share/perl5/PVE/LXC/Setup/Redhat.pm perl module which depended on an updated /usr/share/perl5/PVE/Network.pm that were not yet available via apt-get update & upgrade, specifically the is_ip_in_cidr function and was causing an error on lxc container start. Once this was updated that worked - mostly. But that was another problem (maybe with something specific to my environemnt)
Version: ProxMox V4 updated to latest via apt-get update & upgrade.
This was pretty much a fresh install to which then I did an update on and had this issue. If there is a place I should file a bug report to let me know. It's working fine on my system after this quick fix which took a bit to track down.
I generated a patch to save some people some digging - hope it helps.
(edit: never mind the site wouldn't allow me to include that with the "CODE" tag as i guess it appeared to look like links or something.)