Back to bug 2143874
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat One Jira (issues.redhat.com) | 2022-11-18 07:46:46 UTC | Link ID | Red Hat Issue Tracker OSP-20282 | |
| James Slagle | 2022-11-18 14:06:19 UTC | CC | jslagle | |
| Elvira | 2022-11-21 15:27:36 UTC | CC | egarciar | |
| Brent Eagles | 2022-11-22 14:36:58 UTC | Target Milestone | --- | zstream |
| Target Release | --- | 17.0 | ||
| Priority | unspecified | medium | ||
| CC | beagles | |||
| Assignee | rhos-maint | beagles | ||
| RHEL Program Management | 2022-11-22 14:37:06 UTC | Target Release | 17.0 | --- |
| Brent Eagles | 2022-11-22 14:38:17 UTC | Keywords | Triaged | |
| Brent Eagles | 2022-11-22 14:38:33 UTC | Status | NEW | ASSIGNED |
| RHEL Program Management | 2022-11-22 14:38:40 UTC | Target Release | --- | 17.0 |
| Brent Eagles | 2023-01-25 12:59:00 UTC | Target Release | 17.0 | 17.1 |
| Target Milestone | zstream | ga | ||
| RHEL Program Management | 2023-01-25 12:59:10 UTC | Target Release | 17.1 | 17.0 |
| RHEL Program Management | 2023-01-25 12:59:48 UTC | Target Release | 17.0 | 17.1 |
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(beagles) | |
| Brent Eagles | 2023-08-07 15:08:10 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Flags | needinfo?(beagles) | |||
| Doc Text | Neutron ports created on the undercloud when deploying designate are not deleted when deleting the overcloud. They do not cause operational problems when the overcloud is recreated with or without designate. However, if desired they can be safely removed manually after the overcloud has been deleted using the "openstack port delete" command. | |||
| Roger Heslop | 2023-08-08 17:39:50 UTC | Doc Text | Neutron ports created on the undercloud when deploying designate are not deleted when deleting the overcloud. They do not cause operational problems when the overcloud is recreated with or without designate. However, if desired they can be safely removed manually after the overcloud has been deleted using the "openstack port delete" command. | Currently, neutron ports created on director when deploying designate are not deleted when you delete the overcloud. There are no scenarios in which this causes operational problems, and can be safely ignored. Workaround: You can safely remove the ports manually after the overcloud has been deleted using the `openstack port delete` command. |
| CC | rheslop | |||
| Greg Rakauskas | 2023-08-08 19:51:15 UTC | Doc Text | Currently, neutron ports created on director when deploying designate are not deleted when you delete the overcloud. There are no scenarios in which this causes operational problems, and can be safely ignored. Workaround: You can safely remove the ports manually after the overcloud has been deleted using the `openstack port delete` command. | In RHOSP 17.1 GA when the DNS service (designate) is deployed, there is currently a known issue where 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. |
| CC | rheslop | gregraka | ||
| Jenny-Anne Lynch | 2023-08-15 10:00:36 UTC | CC | jelynch | |
| Doc Text | In RHOSP 17.1 GA when the DNS service (designate) is deployed, there is currently a known issue where 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. | 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. |
Back to bug 2143874