This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2251383 - Designate did not publish name and Floating IP with associated port DNS attributes
Summary: Designate did not publish name and Floating IP with associated port DNS attri...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 17.1 (Wallaby)
Hardware: x86_64
OS: All
medium
low
Target Milestone: ---
: ---
Assignee: Miguel Lavalle
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-11-24 15:38 UTC by Luigi Tamagnone
Modified: 2025-01-10 09:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2025-01-10 09:36:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   OSP-30554 0 None None None 2025-01-10 09:36:01 UTC
Red Hat Issue Tracker OSP-33379 0 None None None 2025-01-10 09:36:40 UTC

Description Luigi Tamagnone 2023-11-24 15:38:23 UTC
Description of problem:
Designate is configured and running, a zone is set on the project.
We create a Network with dns_domain set with the zone name (for example: test.prod.iaas.xxx.fr.).
When we create a new instance (myvm) on a network that has the entry dns_domain set.
The port created for the instance does not contain dns_assignment with the expected values (myvm.test.prod.iaas.xxx.fr.).
When we attached a FIP (that does not contain dns_domain value), the FIP normaly will have the dns_assignment attached to it and the DNS entry on designate myvm.test.prod.iaas.xxx.fr will contain the IP of the FIP.

Version-Release number of selected component (if applicable):
[rhosp-release] Red Hat OpenStack Platform release 17.1.1 (Wallaby)
[os-release] Red Hat Enterprise Linux 9.2 (Plow) 9.2 (Plow)

How reproducible:
Every time the instance or the port is attached to the floating IP no record is published

Steps to Reproduce:
0. (overcloud) [stack@underadmin ~]$ openstack network show dnstest-net
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| dns_domain                | test.prod.iaas.xxx.fr.        |
| name                      | dnstest-net                          |
| provider:network_type     | geneve                               |
| provider:segmentation_id  | 65537                                |
| router:external           | Internal                             |
| subnets                   | 6e890a79-d1b4-4057-9693-e7e6a2307417 |
+---------------------------+--------------------------------------+
[ml2_type_geneve]
vni_ranges=1:65536

(overcloud) [stack@underadmin ~]$ openstack network show NET_adm
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| dns_domain                | test.prod.iaas.xxx.fr.        |
| provider:segmentation_id  | 56685                                |
| id                        | e3074047-17f1-4c96-ab9e-d902060d8b44 |
| subnets                   | 80d760e6-f3a9-4663-8084-fbb20d3cba0b |
| router:external           | Internal                             |
| provider:network_type     | geneve                               |
1.(overcloud) [stack@underadmin ~]$ openstack port create --network dnstest-net --dns-name testgsRH5 testgsRH5
+-------------------------+------------------------------------------------------------------------------------------------------+
| Field                   | Value                                                                                                |
+-------------------------+------------------------------------------------------------------------------------------------------+
| dns_assignment          | fqdn='host-192-168-0-236.openstacklocal.', hostname='host-192-168-0-236', ip_address='192.168.0.236' |
| dns_domain              |                                                                                                      |
| dns_name                |                                                                                                      |
| id                      | 5fb61ab1-a9dd-4470-8d01-8baaecf08e68                                                                 |
| name                    | testgsRH5                                                                                            |
| network_id              | deaf5cf3-364a-4c3a-9b5c-de99ea6a7278                                                                 |
+-------------------------+------------------------------------------------------------------------------------------------------
2. (overcloud) [stack@underadmin ~]$ openstack floating ip create 1f893c50-8533-49f5-b946-2b6585585f4a --port testgsRH5
3. (overcloud) [stack@underadmin ~]$ openstack recordset list test.prod.iaas.xxx.fr. |grep -i testgsrh

Actual results:
No recordset on dns

Expected results:
testgsRH5.test.prod.iaas.xxx.fr. should be present on dns

Additional info:


Note You need to log in before you can comment on or make changes to this bug.