The provisioned IP does not match the "next highest index" of the containers already created but rather jumps due to listener being auto-assigned IP by Oracle GNS. For example,
ora66c20 10.207.39.28
ora72c10 10.207.39.27
When the ora66cXX container was created, the expectation was that DHCP would issue '10.207.39.20' for ora66c20. However, because Oracle GNS has assigned up as high as 10.207.39.27 for the listener on ora72c10, DHCP on the Ubuntu host knew to issue the next available IP of 10.207.39.28.
So everything worked correctly in DNS. The only issue which is a very minor one, is that the IP is now out of sync with the container index for all new containers.
This suggests that maybe ASM Flex Clusters should be put on their own dedicated subnet and a new subnet created in orabuntu-lxc once an ASM Flex Cluster has been placed on a given subnet.
The provisioned IP does not match the "next highest index" of the containers already created but rather jumps due to listener being auto-assigned IP by Oracle GNS. For example, ora66c20 10.207.39.28 ora72c10 10.207.39.27 When the ora66cXX container was created, the expectation was that DHCP would issue '10.207.39.20' for ora66c20. However, because Oracle GNS has assigned up as high as 10.207.39.27 for the listener on ora72c10, DHCP on the Ubuntu host knew to issue the next available IP of 10.207.39.28. So everything worked correctly in DNS. The only issue which is a very minor one, is that the IP is now out of sync with the container index for all new containers. This suggests that maybe ASM Flex Clusters should be put on their own dedicated subnet and a new subnet created in orabuntu-lxc once an ASM Flex Cluster has been placed on a given subnet.