Bug 2143874

Summary: Designate ports are not deleted by "openstack overcloud delete" and "openstack overcloud node unprovision"
Product: Red Hat OpenStack Reporter: yatanaka
Component: tripleo-ansibleAssignee: Brent Eagles <beagles>
Status: ASSIGNED --- QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: beagles, egarciar, gregraka, jelynch, jslagle
Target Milestone: gaKeywords: Triaged
Target Release: 17.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
In RHOSP 17.1, when the DNS service (designate) is deployed, Networking service (neutron) ports created on the undercloud are not deleted when the overcloud is deleted. These ports do not cause operational problems when the overcloud is recreated with or without the DNS service. + Workaround: After the overcloud has been deleted, manually remove the ports by using the `openstack port delete` command.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description yatanaka 2022-11-18 07:37:06 UTC
Description of problem:

I deployed RHOSP 17.0 with Designate.
I can see three designate-overcloud-controller-X-integration-port ports.

~~~
(undercloud) [stack@undercloud ~]$ openstack port list 
+--------------------------------------+---------------------------------------------------+-------------------+------------------------------------------------------------------------------+--------+
| ID                                   | Name                                              | MAC Address       | Fixed IP Addresses                                                           | Status |
+--------------------------------------+---------------------------------------------------+-------------------+------------------------------------------------------------------------------+--------+
| 02600448-e522-4878-8b4a-99ec9aec8c16 | overcloud-controller-0_ovn_physnet_datacentre     | fa:16:3e:c4:81:f7 |                                                                              | DOWN   |
       :
| 63b3ac02-54d9-4d20-80ca-c83ac0c039c0 | overcloud-controller-1_Tenant                     | fa:16:3e:10:86:08 | ip_address='172.16.0.169', subnet_id='ffb1bbed-bc91-4878-857a-dd93e2ac5105'  | DOWN   |
| 6a965b17-8d56-4fab-88f1-4b2b0cde1366 | designate-overcloud-controller-0-integration-port | fa:16:3e:44:1b:c2 | ip_address='10.0.0.212', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'    | DOWN   | <===(*)
| 78d518a7-9f1f-4bcd-a1e3-f6ca9f7a81a7 | overcloud-novacompute-1-ctlplane                  | 52:54:00:62:c5:10 | ip_address='192.168.24.7', subnet_id='9ba40c59-755c-4ce8-a74a-5c8c0d757fa1'  | ACTIVE |
| 8162eeac-ceb4-41f4-af57-2c18e4424f80 | designate-overcloud-controller-2-integration-port | fa:16:3e:d2:f4:8c | ip_address='10.0.0.178', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'    | DOWN   | <===(*)
| 89badfcd-9e90-4648-bfd0-db0c57f5b5cc | overcloud-novacompute-0_InternalApi               | fa:16:3e:50:ef:14 | ip_address='172.16.2.202', subnet_id='3cc6134d-99f4-4603-a8ee-d8febdffc84c'  | DOWN   |
       :
| b7ccca44-cc49-4e8f-b3ce-d1cc76095c35 | overcloud-novacompute-0_Storage                   | fa:16:3e:93:d6:ed | ip_address='172.16.1.106', subnet_id='f860b830-22b3-4250-a465-18221312bc01'  | DOWN   |
| ba48b39b-9d87-4f54-8647-4c9f6b465d91 | designate-overcloud-controller-1-integration-port | fa:16:3e:89:d5:b4 | ip_address='10.0.0.84', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'     | DOWN   | <===(*)
| bd923165-117a-4d37-a182-080a4d0ca712 | overcloud-controller-1_External                   | fa:16:3e:e4:81:dd | ip_address='10.0.0.155', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'    | DOWN   |
~~~

Then I deleted the overcloud by "openstack overcloud delete" and "openstack overcloud node unprovision" command.

~~~
(undercloud) [stack@undercloud ~]$ openstack overcloud delete overcloud
(undercloud) [stack@undercloud ~]$ openstack overcloud node unprovision --all   --stack overcloud   --network-ports   /home/stack/templates/overcloud-baremetal-deploy.yaml
~~~

However, these designate ports were not deleted.

~~~
(undercloud) [stack@undercloud ~]$ openstack port list --long
+--------------------------------------+---------------------------------------------------+-------------------+-----------------------------------------------------------------------------+--------+-----------------+--------------+------+
| ID                                   | Name                                              | MAC Address       | Fixed IP Addresses                                                          | Status | Security Groups | Device Owner | Tags |
+--------------------------------------+---------------------------------------------------+-------------------+-----------------------------------------------------------------------------+--------+-----------------+--------------+------+
| 6a965b17-8d56-4fab-88f1-4b2b0cde1366 | designate-overcloud-controller-0-integration-port | fa:16:3e:44:1b:c2 | ip_address='10.0.0.212', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'   | DOWN   | None            |              |      |
| 8162eeac-ceb4-41f4-af57-2c18e4424f80 | designate-overcloud-controller-2-integration-port | fa:16:3e:d2:f4:8c | ip_address='10.0.0.178', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'   | DOWN   | None            |              |      |
| ba48b39b-9d87-4f54-8647-4c9f6b465d91 | designate-overcloud-controller-1-integration-port | fa:16:3e:89:d5:b4 | ip_address='10.0.0.84', subnet_id='62177a39-ca4a-475b-8e00-5bcf9222f894'    | DOWN   | None            |              |      |
| e94076dc-ff21-46e3-8095-9f34f4c8c068 |                                                   | fa:16:3e:5c:51:b8 | ip_address='192.168.24.5', subnet_id='9ba40c59-755c-4ce8-a74a-5c8c0d757fa1' | ACTIVE | None            | network:dhcp |      |
+--------------------------------------+---------------------------------------------------+-------------------+-----------------------------------------------------------------------------+--------+-----------------+--------------+------+
~~~



Version-Release number of selected component (if applicable):

RHOSP 17.0
TripleO Packages:
  [stack@undercloud ~]$ rpm -qa |grep tripleo
  ansible-tripleo-ipsec-11.0.1-0.20210910011424.b5559c8.el9ost.noarch
  openstack-tripleo-common-containers-15.4.1-0.20220705010409.51f6577.el9ost.noarch
  puppet-tripleo-14.2.3-0.20220718160753.41752a3.el9ost.noarch
  ansible-tripleo-ipa-0.2.3-0.20220301190452.6b0ed82.el9ost.noarch
  ansible-role-tripleo-modify-image-1.3.1-0.20220216001439.30d23d5.el9ost.noarch
  python3-tripleo-common-15.4.1-0.20220705010409.51f6577.el9ost.noarch
  openstack-tripleo-common-15.4.1-0.20220705010409.51f6577.el9ost.noarch
  tripleo-ansible-3.3.1-0.20220720020866.fa5422f.el9ost.noarch
  openstack-tripleo-heat-templates-14.3.1-0.20220719171727.feca772.el9ost.noarch
  openstack-tripleo-validations-14.2.2-0.20220728100828.37bfae3.el9ost.noarch
  python3-tripleoclient-16.4.1-0.20220705111521.23dbe54.el9ost.noarch


How reproducible:

Steps to Reproduce:
1. Deploy RHOSP 17 with designate
   https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/using_designate_for_dns-as-a-service/deploy-rhosp-dns-service_rhosp-dnsaas#deploy-the-dns-service_deploy-rhosp-dns-service
2. run "openstack overcloud delete overcloud"
3. run "openstack overcloud node unprovision --all --stack overcloud --network-ports /home/stack/templates/overcloud-baremetal-deploy.yaml"


Actual results:
designate-overcloud-controller-x-integration-port ports remain


Expected results:
designate-overcloud-controller-x-integration-port ports are deleted

Comment 1 James Slagle 2022-11-18 14:06:19 UTC
The port is created by tripleo-ansible (tripleo_ansible/roles/designate_bind_config/tasks/create_collocated_ips.yml), so it won't be deleted by node unprovision.

Comment 2 Elvira 2022-11-21 15:27:36 UTC
Assigning to VANS squad. Reach back if you need anything