Bug 239074 - Virt Guests Provisioned Through Proxy Do Not Register With RHN Properly
Summary: Virt Guests Provisioned Through Proxy Do Not Register With RHN Properly
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Virtualization (Show other bugs)
(Show other bugs)
Version: 500
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2007-05-04 18:58 UTC by Devan Goodwin
Modified: 2014-05-09 10:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-09 10:03:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Devan Goodwin 2007-05-04 18:58:29 UTC
Description of problem:

When creating a new guest and selecting a proxy to use for the provisioning, the
guest is created but does not register itself to the satellite as it does when
no proxy is selected. After provisioning completes the guest will only be listed
on the virtualization page for the host system and show a hostname of
"Unregistered System".


How reproducible:

Every time on my configuration, haven't tested under other setups yet.

Steps to Reproduce:
1. Install RHN Satellite 500 build.
2. Register a second system and install RHN proxy through the satellite UI.
3. Register a third system running RHEL 5 server and capable of doing paravirt.
4. Create a guest on the third system through the system's virtualization
provisioning tab.
5. Specify the proxy in step 2 before scheduling the kickstart.
6. Run rhn_check on the third system.
  
Actual results:

Provisioning completes, guest created, but guest is not registered to RHN.

Expected results:

Guest should register as it's own profile in RHN.

Additional info:


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