Bug 1971293 - [4.8.0] Deleting agent from one namespace causes all agents with the same name to be deleted from all namespaces
Summary: [4.8.0] Deleting agent from one namespace causes all agents with the same nam...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: assisted-installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.8.0
Assignee: Rom Freiman
QA Contact: Chad Crum
URL:
Whiteboard: KNI-EDGE-JUKE-4.8 AI-Team-Hive
Depends On: 1969974
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-13 12:09 UTC by Michael Filanov
Modified: 2021-07-27 23:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1969974
Environment:
Last Closed: 2021-07-27 23:12:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift assisted-service pull 2063 0 None open [ocm-2.3] Bug 1971293: Delete unregistered hosts agents by namespace 2021-06-23 12:04:59 UTC
Red Hat Bugzilla 1969974 1 high CLOSED [master] Deleting agent from one namespace causes all agents with the same name to be deleted from all namespaces 2022-08-28 08:47:34 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:13:09 UTC

Description Michael Filanov 2021-06-13 12:09:37 UTC
+++ This bug was initially created as a clone of Bug #1969974 +++

Description of problem:
Deleting agent from one namespace causes all agents with the same name to be deleted from all namespaces

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


How reproducible:


Steps to Reproduce:
1. Create bmh/infraenv in one namespace
2. Wait for agent
3. recreate bmh/infraenv in another namespace
4. Wait for agent
5. Delete old agent

Actual results:
All agents with the same name will be deleted not matter in which namespace

Expected results:
One agent deleted and new one stays alive

Additional info:

Comment 1 Michael Filanov 2021-06-13 13:40:12 UTC
caused by https://issues.redhat.com/browse/MGMT-6006

Comment 2 Michael Filanov 2021-06-13 13:42:57 UTC
Once https://bugzilla.redhat.com/show_bug.cgi?id=1968043 is in we can get the host by both id and namepsace and it will resolve this issue.

Comment 8 Chad Crum 2021-07-09 16:17:20 UTC
Validated bug is fixed in OCM DS snapshot 2.3.0-DOWNSTREAM-2021-07-06-05-34-53

Validation steps:
- Create cluster sno-test-vm in ns sno-test-vm - wait for agent to be created
- Create cluster sno-test-vm in ns sno-test-vm-2, using the same CR values + names (aci / cd / infraenv / bmh)
- Wait for sno-test-vm in sno-test-vm-2 to have agent created
- Delete agent in sno-test-vm ns
- Confirm agent in sno-test-vm-2 ns still exists

Comment 11 errata-xmlrpc 2021-07-27 23:12:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2438


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