I should've added that I tried this on:
2.2.3-2
then upgraded to:
2.4.0-beta6.el6 

problem persists across upgrade.



On Tue, Jun 4, 2013 at 10:26 PM, David Birdsong <david.birdsong@gmail.com> wrote:
I've had to give up on using ec2 for my cobbler server given that TFTPD over VPN is a nightmare.

I'm having a hell of time moving my cobbler server over.

replicate led nowhere since it expected a bunch of rsync modules that I didn't have installed and didn't want installed (on the original cobblerd server.)

I've manually rsync'd over:

/var/lib/cobbler
/var/www/cobbler
/etc/cobbler

...everything is fine except for profiles. None of the profiles will list, this returns nothing:
[root@ops-1 ~]# cobbler profile list


and yet all of the profiles are here:
/var/lib/cobbler/config/profiles.d/empty.json
/var/lib/cobbler/config/profiles.d/base-with-network-console.json
/var/lib/cobbler/config/profiles.d/test.json
/var/lib/cobbler/config/profiles.d/empty-with-nameservers.json
/var/lib/cobbler/config/profiles.d/base-with-network.json

strace on both old and new cobblerd's shows no activity on those files during the XML-RPC call, is cobbler loading these into memory on startup?

could the new cobblerd be rejecting these profile json files?