Description of problem: When a new host is being added after a deployment has been completed, IP allocation starts with the first in the range again. This could result in duplication of IPs. This is with subnets set to IPAM- Internal DB and Boot mode Static. HA Neutron with (3 controller, 2 Compute, 3 Ceph nodes, 1 RHEL node added after deployment) Version-Release number of selected component (if applicable): ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el7ost.noarch ruby193-rubygem-staypuft-0.5.12-1.el7ost.noarch rhel-osp-installer-client-0.5.5-2.el7ost.noarch openstack-puppet-modules-2014.2.8-1.el7ost.noarch rhel-osp-installer-0.5.5-2.el7ost.noarch How reproducible: Steps to Reproduce: 1.Complete deployment 2.discover a new host 3.Assign the host and configure networks 4.Verify the auto suggested IP. It defaults to the first IP in the subnet IP range. Actual results: First IP in the subnet range appears in the auto allocated IP despite the fact that it was used early in the deployment. Expected results: IP auto allocation should increment to the next IP in the range. Additional info:
*** This bug has been marked as a duplicate of bug 1176423 ***