10:33 a.m.
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
...
Updating Objects Newer On Remote
Linking Distro f14-i386
Exception occured: exceptions.NameError
Exception value: global name 'base' is not defined
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 95,
in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 210,
in runner
self.logger
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 782, in
replicate
sync_all = sync_all
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 342, in run
self.link_distros()
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 193, in link_distros
print _("- symlink creation failed: %(base)s, %(dest)s") % {
"base"
: base, "dest" : dest_link }
!!! TASK FAILED !!!
distro report on the 2.0.3.1 shows
cobbler distro report --name=f14-i386
Name : f14-i386
Architecture : i386
Breed : redhat
Comment :
Initrd : /mnt/iso/f14/images/pxeboot/initrd.img
Kernel : /mnt/iso/f14/images/pxeboot/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {}
Management Classes : []
OS Version : fedora14
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
I had to modify codes.py to add fedora14 and fedora15 and restart cobbler
Thoughts?
-Ron
5:28 p.m.
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
You should just be able to say sync-all and not distros=*, etc. But that
is new in 2.0.11 I believe.
...
Updating Objects Newer On Remote
Linking Distro f14-i386
Exception occured: exceptions.NameError
Exception value: global name 'base' is not defined
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 95,
in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 210,
in runner
self.logger
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 782, in
replicate
sync_all = sync_all
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 342, in run
self.link_distros()
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 193, in link_distros
print _("- symlink creation failed: %(base)s, %(dest)s") % {
"base"
: base, "dest" : dest_link }
!!! TASK FAILED !!!
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.
--
Scott Henson
Red Hat SOC Operator
WVU Alum BSAE/BSME
7:15 a.m.
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?
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?)
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: david.lee(a)ecmwf.int
6:47 p.m.
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.
3:10 a.m.
James Cammarata wrote:
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.
I was not a participant in the events above. I merely observed the mail
thread, because it was something that I knew we would eventually want to
be doing.
If you are "on the case" with this issue, then that sounds good, and it
gives me an incentive at least to try this technique in our environment,
see what happens and report back. I'll try (but cannot promise) to do
that in the next few days.
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. [...]
Sounds good. Thanks.
[...] 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.
We're not really in a position to be cloning the git tree. (That's
something I need to take up locally. In the future I would like to be
in such a position.)
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: david.lee(a)ecmwf.int
4587
days inactive
4673
days old
cobbler@lists.fedorahosted.org
4 comments
4 participants
participants (4)
-
David Lee -
James Cammarata -
Ronald J. Yacketta -
Scott Henson