Description of problem:
I have tried to provision 2 virt systems (Xen PV & FV guests) from the Satellite 5.3.0 at the +-same time and obtained tracebacks /var/log/up2date.
Version-Release number of selected component (if applicable):
Satellite 5.3.0 synced to Stage
1 of 1 attept
Steps to Reproduce:
1. I do not know how to reproduce this
2. Only not standard thing I have done was I have scheduled that PV and FV guest installation on the Satellite while Host system was rebooting
Traceback recorded in the log (2 times):
[Wed Sep 9 08:31:46 2009] up2date updateLoginInfo() login info
[Wed Sep 9 08:31:46 2009] up2date logging into up2date server
[Wed Sep 9 08:31:46 2009] up2date successfully retrieved authentication token from up2date server
[Wed Sep 9 08:31:47 2009] up2date Updating package profile
[Wed Sep 9 08:31:51 2009] up2date updateLoginInfo() login info
[Wed Sep 9 08:31:51 2009] up2date logging into up2date server
[Wed Sep 9 08:31:51 2009] up2date successfully retrieved authentication token from up2date server
[Wed Sep 9 08:31:52 2009] up2date
Traceback (most recent call last):
File "/usr/sbin/rhn_check", line 276, in __run_action
(status, message, data) = CheckCli.__do_call(method, params)
File "/usr/sbin/rhn_check", line 269, in __do_call
retval = method(*params)
File "/usr/share/rhn/actions/kickstart_guest.py", line 50, in initiate
virt_type, name, mem_kb, vcpus, disk_gb, virt_bridge, disk_path, extra_append, log_notify_handler)
File "/usr/share/rhn/spacewalkkoan/spacewalkkoan.py", line 201, in initiate_guest
exceptions.AttributeError: NameError instance has no attribute 'get_error_message'
Installation should start
This was discovered while RHEL5-U4 KS trees validation.
This is not a releng bug.
Changing product to RHN Satellite.