On Wed, Oct 5, 2011 at 7:15 AM, David Lee <David.Lee(a)ecmwf.int> wrote:
Scott Henson wrote:
> On 12 Jul 2011 11:33:44 -0400, "Ronald J. Yacketta"
<yacketrj(a)potsdam.edu> wrote:
>> Trying to replicate from cobbler 2.0.3.1 to cobbler 2.0.11 and keep
>> running into the following:
>>
>> cobbler replicate --master=_MASTER_SERVER_ --distros=* --profiles=*
>> --systems=* --sync-all
> [...]
>
> It seems you've found two bugs. The traceback you see above is from the
> except statement. The real bug that you are seeing is that cobbler can't
> create a symlink that it is expecting to be able to create. What does
> 'ls -l /var/www/cobbler/links' say?
>
> I've got the first bug fixed now, but it won't fix your replicate until
> I see what is in /var/www/cobbler/links/ Thanks.
> [...]
Is there an update on this, please?
I didn't see this before, so I'll take a look at it tonight or
tomorrow. Did you ever provide the info requested above? If not,
please post the data in your pastebin of choice and send the link in
reply.
We have a cobbler server hosted on one machine, which we would like to
keep replicated on another machine. But there seems little point in us
trying to do this at present if this bug is present. (In our case, both
servers would be the most recent cobbler release (which I understand is
still 2.0.11).
Is there a release planned soon, with at least this issue fixed?
(Might an element of "release early, release often" be useful here?)
I'm trying to find out what's going on with the release. We should be
in somewhat good shape for one, just need to tag the release and get
RPMs pushed to EPEL. In the meantime, you can clone the git tree and
do a "make rpms" to build them yourself for a hotfix. For the last two
months, the only patches going in have primarily been bug fixes and
optional features, nothing in the core feature set should have
changed.