Bug 246720 - Cannot register guest on old host
Cannot register guest on old host
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Virtualization (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Miroslav Suchý
Milan Zázrivec
Depends On:
Blocks: 456985 507280
  Show dependency treegraph
Reported: 2007-07-04 08:46 EDT by Miroslav Suchý
Modified: 2009-09-10 14:29 EDT (History)
3 users (show)

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

Attachments (Terms of Use)
Traceback (19.56 KB, application/octet-stream)
2007-07-04 08:46 EDT, Miroslav Suchý
no flags Details
Traceback from 421 upgraded to 500 (18.90 KB, application/octet-stream)
2007-08-01 05:49 EDT, Miroslav Suchý
no flags Details

  None (edit)
Description Miroslav Suchý 2007-07-04 08:46:18 EDT
Description of problem:
I have XEN host. It was registered to Satellite (4.9). Satellite was then
upgraded to 500 and when I try to register new guest running on thist host, I
got traceback.

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

How reproducible:
done twice

Steps to Reproduce:
1. take older satellite < 500
2. register XEN host to this satellite
3. upgrade satellite
4. register guest to this satellite
Actual results:
Traceback (see attachment)

Expected results:
register system

Additional info:
If I delete profile and reregister host, the guest is registered without problem.
Comment 1 Miroslav Suchý 2007-07-04 08:46:18 EDT
Created attachment 158517 [details]
Comment 3 Miroslav Suchý 2007-08-01 05:49:25 EDT
Created attachment 160402 [details]
Traceback from 421 upgraded to 500

I installed satellite 4.2.1, register host, upgraded sat to 5.0.0, register
guest on the same host. And still got traceback (but registration proceed ok
from client side).
Comment 4 Miroslav Suchý 2007-08-01 06:00:25 EDT
Due to BZ 245311 I need to post another comment to change status back from NEEDINFO.
Comment 5 Miroslav Suchý 2007-08-01 08:33:35 EDT
With this patch it works:

--- /usr/share/rhn/server/rhnVirtualization.py.orig     2007-08-01
14:14:45.000000000 +0200
+++ /usr/share/rhn/server/rhnVirtualization.py  2007-08-01 14:18:26.000000000 +0200
@@ -594,7 +594,7 @@
         new_values_array = []
         bindings = {}

-        if not existing_row['confirmed']:
+        if not existing_row.has_key('confirmed'):

         if existing_row['host_system_id'] != host_id:
Comment 7 Fedora Update System 2008-01-31 12:51:46 EST
system-config-firewall-1.0.12-4.fc8 has been submitted as an update for Fedora 8
Comment 8 Fedora Update System 2008-02-01 20:18:14 EST
system-config-firewall-1.0.12-4.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update system-config-firewall'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-1200
Comment 9 Brandon Perkins 2008-04-09 22:33:28 EDT
Changed status to ASSIGNED as Fedora Update System should not have changed this.
Comment 10 Nick Strugnell 2008-07-04 10:36:02 EDT
note that the following syntax:

if not existing_row['confirmed']:

is used a few times, not just here. We should really check the code throughout
as this is a python coding error.

Should be:

if not existing_row.has_key('confirmed'):
if not existing_row.get('confirmed'):
Comment 11 Miroslav Suchý 2008-08-15 08:49:19 EDT
Fixed in Spacewlk bug 459254.
Comment 12 Brandon Perkins 2008-08-27 23:10:19 EDT
Removing bug 459254 blocks bug 246720.
Comment 13 Milan Zázrivec 2009-07-08 10:37:45 EDT
Registered host, upgraded satellite, registered guest, no traceback, verified.
Comment 14 Brandon Perkins 2009-09-10 14:29:23 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.