-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/13/2009 05:04 PM, Paul Company wrote:
> I'm trying to replicate from cobbler1 (my master server) to cobbler2
> (a non-master server).
> 
> The problem seems to be that
> cobbler1:/var/lib/cobbler/config/distros.d/5Server-x86_64.json
> is not being rsync'ed over to cobbler2.
> 
> Some background information:
> I created the distro on cobbler1 by doing the following:
> # mkdir -p /usr/distros/5Server-x86_64
> # cd /usr/distros/5Server-x86_64
> # wget http://myrepo/mrepo/5Server-x86_64/disc1/images/pxeboot/vmlinuz
> # wget http://myrepo/mrepo/5Server-x86_64/disc1/images/pxeboot/initrd.img
> # cobbler distro add --name=5Server-x86_64 \
>                    --kernel=/usr/distros/5Server-x86_64/vmlinuz \
>                    --initrd=/usr/distros/5Server-x86_64/initrd.img \
>                    --ksmeta="tree=http://myrepo/mrepo/5Server-x86_64";
> 
> I don't use "cobbler import" because it copies over the entire
> distribution content and I have limited HDD space.
> 
> Is there a workaround for this issue?
> 


I don't expect the above to work, nor will the new replicate code work
with this.  Basically what is happening is that you are putting files in
places that cobbler doesn't expect them to be.  The replicate feature
only really works if you used import to add the distro.  Even in 2.0,
this would fail because we don't go out of band (rsync is used for full
data sync) to get the kernel and initrd.  So basically when the
replicate code goes looking for them (really it only looks for the
kernel), it doesn't find it since it wasn't brought over with the data
sync.

I think we can get replicate to bring things over like you want, but I
don't think it will be accepted for 2.0.  I can see a relatively simple
patch to fix this and get it in 2.2.  But I would have to actually look
at the code to be sure.  Basically if we don't find the kernel and we
are in full data sync mode, go out of band (http) to get them from the
remote system.  That should generally be good enough in most cases.
Though I have a strange feeling this could get us in trouble in other
places.  I'll have to play with it (unless you beat me to it... :-D)

- -- 
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJKrnjYAAoJEN/U2xG4t+kAIAYP/1xbJxPCJQXsX4H198qA+fJq
NcCZOVjCIKmlz1T4UYNjVPvvhYjW7IT0slLeYH9hwHPNzaqv6sITKarZ0MbRheNs
vBiO5RzK1xc0z9ocfhPhTqaL+VeYV/VfnbPDq3g9e804RPjF6+al991iE7/KRyRO
/TA0hwpE/ZB0qSSdajbN5ed1T8YS1V3CjQc9Gb2mcml5+dIoVrpCVCsdzKRN+sTG
aXXVow88mWJCoP6qLSv7WD/Jy8aD95Ex+ASk15n2PeG/q7/PyQxT3Pr3dfKRcciV
6HPvrZXfVBbjEyJ6xxcCanMhVzhwyfhnNNEpWHa45irHI6R5cBgLrmSUIrDhjJgG
3ZUJc3rSYC83mLfbacbtbVhjn6/D9tAUOB9+Ng4iURHAnyord+hqGiTvU1eTGB6J
mR7vdsvBmh7Xi7QPkkvPWiYUpQgabmBwwGMFepIL1FzqBAoFesEU2gPmX72wx/bY
GBpneWaLjlrDihbjz/zLMZKLThGqkz/+AVskfoAEG5XUu4JcWl2w7fKDN2Zb0bJz
CcA2uO1dMaZHW5CaeTcHxz4lPzgfu2G7Ot28Z8KY0CbqyZEdnlVX50eCkv5cl1Ev
LiCkJB/4RXgTbh89XAdpNuGdm1v0KWChBGYWLEs3yhFk4DFTrICISsVl3CI7wtRQ
myFOVQFPDHOZHazOnfOt
=g+Q5
-----END PGP SIGNATURE-----
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to