DNS records not created with pre-created port
Bug #1544997 reported by
Sridhar Venkat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-infoblox |
Fix Released
|
Medium
|
Aliaksandr Dziarkach |
Bug Description
I created a port using neutron port-create. And used it to create a nova instance.
I do not see DNS record created in Infoblox. I am using network name for zone pattern and instance name for DNS hostname pattern.
Is this scenario supported?
Changed in networking-infoblox: | |
assignee: | nobody → Aliaksandr Dziarkach (aliaksandr-dziarkach) |
Changed in networking-infoblox: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
May I add to this: When the DNS/DHCP Support is True, IP Allocation Strategy is Host Record, the sync_neutron_ to_infoblox. py script would error. The error would go away when DNS/DHCP Support is changed to False during the script execution, under this condition, this script will not create any Host Record for pre-existing Openstack Ports. The error varies depending on the recovery attempts, here is a sample:
ERROR __main__ [req-5a80dc52- 416b-452c- b406-daa1a55b41 8a - - - - -] Error occurred: DHCP member is not reserved for network view: (Openstack), cidr (10.1.1.0/24)
I am using IOA 2.0.1 with Openstack Liberty and Infoblox 7.3.4