Bug 1189368 - when guests are removed from ESX, they are not removed from Satellite 5
Summary: when guests are removed from ESX, they are not removed from Satellite 5
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Li Bin Liu
URL:
Whiteboard:
Depends On:
Blocks: 1263533
TreeView+ depends on / blocked
 
Reported: 2015-02-05 06:52 UTC by Jan Hutař
Modified: 2015-09-17 09:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1263533 (view as bug list)
Environment:
Last Closed: 2015-09-17 09:13:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Hutař 2015-02-05 06:52:36 UTC
Description of problem:
When guests are removed from ESX, they are not removed from Satellite 5


Version-Release number of selected component (if applicable):
virt-who-0.11-5.el7.noarch


How reproducible:
1 of 1


Steps to Reproduce:
1. # virt-who --one-shot --satellite --satellite-server=<sat_fqdn> --satellite-username=<sat_user> --satellite-password=<sat_pass> -d --esx --esx-owner=aaa --esx-env=bbb --esx-server <esx_ip> --esx-username <esx_user> --esx-password <esx_pass>
2. Install guest on ESX and register it to the Satellite
3. # virt-who --one-shot --satellite --satellite-server=<sat_fqdn> --satellite-username=<sat_user> --satellite-password=<sat_pass> -d --esx --esx-owner=aaa --esx-env=bbb --esx-server <esx_ip> --esx-username <esx_user> --esx-password <esx_pass>
4. Make sure new guest appears in Satellite 5 webUI
5. Remove guest from ESX (delete from disk using flash-based vCenter app)
6. # virt-who --one-shot --satellite --satellite-server=<sat_fqdn> --satellite-username=<sat_user> --satellite-password=<sat_pass> -d --esx --esx-owner=aaa --esx-env=bbb --esx-server <esx_ip> --esx-username <esx_user> --esx-password <esx_pass>


Actual results:
System profiles, although guests were removed from ESX hypervisor, are kept on Satellite 5 consuming entitlements


Expected results:
System profiles of removed guests should be removed.


Additional info:
Maybe this is known limitation or design decision, but I would expect it to work as described in "Expected results"

Comment 2 Radek Novacek 2015-02-05 07:10:59 UTC
Please attach the output from virt-who command. virt-who prints out the host/guest association.

Comment 4 Radek Novacek 2015-02-09 07:20:41 UTC
Jan,

sorry to bother you. I would need to see the log before and after removing the guest in order to see whether the guest really stopped being reported.

Thanks

Comment 5 Jan Hutař 2015-02-09 07:56:53 UTC
No problem at all. Are we talking about `virt-who -d ...` output before and after I remove the guest?

Comment 6 Radek Novacek 2015-02-09 08:12:44 UTC
Yes, exactly. Same as in comment 3, but before and after removing.

Comment 8 Radek Novacek 2015-05-28 11:44:51 UTC
virt-who correctly removed the deleted guest from the list of guests that is sent to the Satellite 5.

I think that guests are not removed from Satellite 5 when they disappear because we don't know if they're really gone (like deleted) or just stopped (some hypervisors doesn't report stopped guests) or even migrated to some machine that is not monitored by virt-who.

Moving this bug to Satellite 5, please confirm my assumptions and close this bug or correct me if I'm wrong.

Comment 11 Radek Novacek 2015-09-17 08:14:50 UTC
Tomas,

please tell us what Satellite 5 does when the guest is no longer reported by virt-who (system is no longer reported by virt_notify xmlrpc call). Does it remove the system?

Comment 12 Tomas Lestach 2015-09-17 09:06:34 UTC
Satellite 5 doesn't remove systems by its own.

Comment 13 Radek Novacek 2015-09-17 09:13:31 UTC
Ok, thank you. I think we can close this bug as NOTABUG.

Comment 14 Jan Hutař 2015-09-17 09:16:48 UTC
Mine thinking here was that when virt-who created the guest, it should remove it when the guest gets removed (contrary to normal situation when admin manually or using script e.g. in KS profile registers system and then manually deletes the profile when the system is not required any more). If that is not possible, please feel free to close this appropriately.

Comment 15 Radek Novacek 2015-09-17 09:28:19 UTC
Well, we can't possibly tell, if the guest is really deleted or just migrated somewhere. Some hypervisors doesn't even report the guest if it's not running (because it's not assigned to any particular host).


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