On 14/10/08 17:00, Michael DeHaan wrote:
  

The solution (and I'll admit the serializer's depth sorting should have 
avoided this to begin with), seems to be that we should not be enforcing 
the parent assignment rules at the time when we create the objects in 
memory, only when we change the parentage of the subprofile. Apologies 
if that sounds too complicated (it is complicated), but it's just a one 
line patch:

http://git.fedorahosted.org/git/cobbler?p=cobbler;a=commitdiff;h=cc6d9e986235ff07aa8453212d5edf33918790bd;hp=ed17a402d932fbf2cbcf01fc76aafd29a3f5f5d6

I'd be interested to know if others are seeing similar or not. I 
reviewed the diffs between 1.2.5 and 1.2.6 and there's nothing that 
would cause this, but somehow if the depth numbers got out of line it's 
possible.

I tried your config files and "cobbler list" prints the right tree. I 
think this possiblity was always there but it's not serious, if anyone 
hits this error they can apply the above patch.

If we get anyone else saying they hit this we can think about doing an 
update later.
    

Michael,

This bit me earlier today.

I fixed it by manually modifying the depth field in the .json files.

I'm not sure how it occurred in the first place.

R.

_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler