+++ This bug was initially created as a clone of Bug #607379 +++
Description of problem:
org.migrateSystems API call fails on Xen hosts
Version-Release number of selected component (if applicable):
Any use of org.migrateSystems using a Xen host's system ID results in an internal systems error.
Steps to Reproduce:
$client = new Frontier::Client(url => "http://$HOST/rpc/api");
$session = $client->call('auth.login', $user, $pass);
@list = ( 1000011023 );
$client->call('org.migrateSystems', $session, 122, \@list);
500 Internal Server Error
No error. System 1000011023 should have been migrated from org 1 to org 122.
Extract from /var/log/tomcat5/catalina.out is attached.
--- Additional comment from email@example.com on 2010-06-23 20:21:16 EDT ---
Created attachment 426420 [details]
The solution for the problem is not to try to untie virtual guests from
their virtualization host during host migration as it's OK to have
host and guests in different organizations.
spacewalk.git master: 11008f331eee08c7999008d4e76345e7dfeefdc0
removing MigrationManagerTest.testRemoveVirtualGuestAssociations test
(test doesn't make sence, since we support having host and virt guests in different orgs)
Moving ON_QA ...
This bug has been fixed in Spacewalk 1.3.