Bug 1037622

Summary: Virtual host profile removal leaves irrelevant entries in the DB.
Product: Red Hat Satellite 5 Reporter: Dimitar Yordanov <dyordano>
Component: ServerAssignee: Jan Dobes <jdobes>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 560CC: tlestach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-09 11:05:13 UTC 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:
Bug Depends On:    
Bug Blocks: 924189    

Description Dimitar Yordanov 2013-12-03 13:45:25 UTC 
Description of problem:
Irrelevant entries are left behind in the DB after Virtual host profile is removed from Satellite.

Version-Release number of selected component (if applicable):
spacewalk-java-2.0.2-48

How reproducible:
100%

Steps to Reproduce:
1. Create KVM Host - VHost.
2. Create several KVM guests on VHost.
3. Register VHost to Satellite.
4. Add Tools Channel to VHost.
5. yum install rhn-virtualization-host.
6. Check the DB entries.

rhnschema=# select * from rhnVirtualInstance;
 id | host_system_id | virtual_system_id | uuid | confirmed | created | modified 
----+----------------+-------------------+------+-----------+---------+----------
(0 rows)


7. rhn-profile-sync 
Updating package profile...
Updating hardware profile...
Updating virtualization profile...

8. Check the DB entries.

rhnschema=# select * from rhnVirtualInstance;
 id  | host_system_id | virtual_system_id |               uuid               | confirmed
 |            created            |           modified            
-----+----------------+-------------------+----------------------------------+----------
-+-------------------------------+-------------------------------
 136 |     1000010237 |                   | 9372d0be65ef83bc96b840e8c8d7f726 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:24:37.481866-05
 135 |     1000010237 |                   | cf14fad371587b97701b5e3c399ce481 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:24:37.481866-05
 134 |     1000010237 |                   | 8615fc78b7de569932036c5128cd6836 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:24:37.481866-05
 133 |     1000010237 |                   | 2dc191d964d071b288c01329129ce270 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:24:37.481866-05
 132 |     1000010237 |                   |                                  |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:24:37.481866-05
(5 rows)

9. Unregister the VHost from Satellite.

10. Check the DB entries.

rhnschema=# select * from rhnVirtualInstance;
 id  | host_system_id | virtual_system_id |               uuid               | confirmed
 |            created            |           modified            
-----+----------------+-------------------+----------------------------------+----------
-+-------------------------------+-------------------------------
 136 |                |                   | 9372d0be65ef83bc96b840e8c8d7f726 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:27:55.108796-05
 135 |                |                   | cf14fad371587b97701b5e3c399ce481 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:27:55.108796-05
 134 |                |                   | 8615fc78b7de569932036c5128cd6836 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:27:55.108796-05
 133 |                |                   | 2dc191d964d071b288c01329129ce270 |         1
 | 2013-12-03 08:24:37.481866-05 | 2013-12-03 08:27:55.108796-05
(4 rows)

Actual results:
Some entries left behind in the DB that are not to be used if VHost is not to be registered to Satellite again.

Expected results:
The DB is cleaned up from the irrelevant entries.
Comment 2 Tomas Lestach 2018-04-09 11:05:13 UTC 
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.