Bug 507097 - Memory, Virtual CPU, and Disk Image size options for virtual guests not applied when virtual guest provisioned
Memory, Virtual CPU, and Disk Image size options for virtual guests not appli...
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Partha Aji
Brad Buckingham
Depends On:
Blocks: 457075
  Show dependency treegraph
Reported: 2009-06-20 16:38 EDT by Steve Salevan
Modified: 2009-09-10 15:26 EDT (History)
5 users (show)

See Also:
Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-10 15:26:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steve Salevan 2009-06-20 16:38:45 EDT
Description of problem:
If a user opts to change the default Memory, Virtual CPU, and Disk Image size options in Advanced Configuration upon kickstarting a virtual guest, these settings will not be transmitted to Koan appropriately, resulting in a default guest being provisioned in spite of these non-default settings.

Version-Release number of selected component (if applicable):
530, 6/12 build

How reproducible:

Steps to Reproduce:
1. Register a Virtualized Host to a Satellite
2. Access the SDC for this system
3. Virtualization->Provisioning
4. Set a name for the new guest
5. Click 'Advanced Configuration'
6. Set the default memory, virtual CPU, and disk image settings to non-defaults
7. Run rhn_check on the virt host
8. Examine the configuration files produced in /etc/xen and the size of the produced disk image in /var/lib/xen
Actual results:
Config file and disk image size reflect defaults

Expected results:
Config file and disk image size reflect non-defaults

Additional info:
Comment 2 Partha Aji 2009-06-24 11:34:15 EDT
Moving to ON_QA
Comment 3 Brad Buckingham 2009-06-30 16:28:20 EDT

Ran the scenario described in the description and verified that the guest was provisioned with correct values for memory, cpu and disk.

Moving to VERIFIED.
Comment 4 Brad Buckingham 2009-07-29 14:03:47 EDT

Comment 5 Brandon Perkins 2009-09-10 15:26:30 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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