Bug 2076169 - trunk/subports not being deleted from platform after node deletion
Summary: trunk/subports not being deleted from platform after node deletion
Keywords:
Status: CLOSED DUPLICATE of bug 2028274
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Maysa Macedo
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-18 06:18 UTC by Arnab Ghosh
Modified: 2022-05-30 18:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-30 18:46:14 UTC
Target Upstream Version:
Embargoed:
mdemaced: needinfo-


Attachments (Terms of Use)

Description Arnab Ghosh 2022-04-18 06:18:20 UTC
Description of problem:
trunk/subports remains in DOWN after the node they belong to got removed. This issue was fixed earlier in Openshift version 4.6 via https://bugzilla.redhat.com/show_bug.cgi?id=1883166. 

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

How reproducible:
Not Sure

Steps to Reproduce:
1.
2.
3.

Actual results:
subports are remaining in Down state after node removal.

Expected results:
Stale subports should be deleted after a node has been deleted.

Additional info:

Comment 7 Maysa Macedo 2022-05-30 18:46:14 UTC
Hello,

In case the OpenStack Servers of the worker Nodes were somehow removed, but the corresponding Trunk remained there, those subports wouldn't be cleaned up because the 4.8.18 version does not contain the fix[1] that detaches those leftover Ports from the trunk and finally allow the deletion of them. The 4.8.25 version has the fix for that.

It would be interesting to know which operation was performed that enabled the Server to be deleted and the Trunk not. Since the last question is unrelated to this specific bug, I'm closing it.

Thanks,
Maysa.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2028274

*** This bug has been marked as a duplicate of bug 2028274 ***


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