After creating several ora67cxx containers based on an oel67 seed container, I reran the ubuntu-services.sh to create some ora72xx containers based on an oel72 seed container. The oel72 seed containers got handed out the same DNS address as the oel67 seed containers, namesly 10.207.29.10 which caused issues at the end of ubuntu-services-2.sh and in ubuntu-services-3.sh, namely that DNS resolution failed because oel67 was not running. If oel67 had been running even worse issue would have been the scripts would have resolved to oel67 instead of oel72. Need to find out why DHCP handed out the same IP address, the ".10" address instead of giving oel72 the next available address which would have been ".11" address.
gstanden
commented
5 years ago
After creating several ora67cxx containers based on an oel67 seed container, I reran the ubuntu-services.sh to create some ora72xx containers based on an oel72 seed container. The oel72 seed containers got handed out the same DNS address as the oel67 seed containers, namesly 10.207.29.10 which caused issues at the end of ubuntu-services-2.sh and in ubuntu-services-3.sh, namely that DNS resolution failed because oel67 was not running. If oel67 had been running even worse issue would have been the scripts would have resolved to oel67 instead of oel72. Need to find out why DHCP handed out the same IP address, the ".10" address instead of giving oel72 the next available address which would have been ".11" address.