Tomas,
It should be fixed with commit 9d4a84d50842a03f61fd2496cb5b5af922c58c47. Sorry
for that,
I was rushing things along at the end of the day when I pushed those commits.
/aron
----- Original Message -----
From: "Tomas Lestach" <tlest...@redhat.com>
To: "Aron Parsons" <apars...@redhat.com>
Cc: spacewalk-devel@redhat.com
Sent: Wednesday, December 15, 2010 1:08:02 PM GMT -05:00 US/Canada Eastern
Subject: SystemManagerTest.testSystemSearch junit test
Hello Aron,
I saw, one of our junit tests failed:
====================================================================================================
com.redhat.rhn.manager.system.test.SystemManagerTest.testSystemSearch
...
systemsearch_uuid is empty with value: e280ccb0-1f31-11dc-9c52-00425200ea2f
Stacktrace
junit.framework.AssertionFailedError: systemsearch_uuid is empty with
value: e280ccb0-1f31-11dc-9c52-00425200ea2f
at
com.redhat.rhn.manager.system.test.SystemManagerTest.testSystemSearch(SystemManagerTest.java:793)
====================================================================================================
It looks it's caused by the commit
f4ec077413cf6d5b1510ff58d81560272ed453ff
especially:
+ /* UUID setup */
+ ServerUuid uuid = ServerUuidTest.createTestServerUuid();
+ uuid.setServer(s);
+ s.setServerUuid(uuid);
+
If you check the createTestServerUuid method, you'll find out that the
method creates a new org, new user, new server and associated the server
with an UUID. The server-uuid association gets stored into the DB. So,
if you then update the server, the change won't get reflected into the
DB as well. That causes later search to fail.
At the first look, I'd say, it's not appropriate to call this method to
get an UUID.
Could you check the issue, please?
Regards,
Tomas
--
Tomas Lestach
RHN Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
