Bug 1074654 - SAM does not support nested virt guests
Summary: SAM does not support nested virt guests
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: katello
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tom McKay
QA Contact: SAM QE List
URL:
Whiteboard:
Depends On:
Blocks: sam20-tracker
TreeView+ depends on / blocked
 
Reported: 2014-03-10 18:38 UTC by Chris Duryee
Modified: 2016-03-11 03:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-11 03:33:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Chris Duryee 2014-03-10 18:38:00 UTC
Description of problem:

SAM does not support the concept of systems that are both guests and hosts. This causes issues when running nested guests (i.e., guests inside of guests). The "middle" guest and most-nested guest do not show the correct host/guest relationship in the SAM UI.

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


Steps to Reproduce:
1. create a guest system G1, register it to SAM
2. on the guest system G1, create a new guest, G2. Start virt-who on G1
3. Register G2 to SAM

Actual results: The host/guest relationship between G1 and G2 does not appear in the system details page for either system.

Expected results: host/guest relationship is shown in SAM UI


Additional info: You can override the facts for G1 to get the host/guest map to appear like so:

{"virt.is_guest": false, "virt.uuid": ""}

I think candlepin has the correct data in its DB but is not sending it up via the /consumer/uuid/host API call. There may also be some katello changes needed as well.


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