On Tue, Apr 17, 2012 at 12:32 PM, James Cammarata wrote:
>
> Interesting, if that's true it was changed a LONG time ago:
>
> defe28ec (Michael DeHaan 2009-02-12 18:14:24 -0500 28) \
> fd.write("%s\t%s\t%s\tstart\t%s\n" % (objtype,name,ip,time.time()))
>
> Frankly I'd just archive your existing
On Mon, Apr 16, 2012 at 9:10 PM, Gonzalo Servat
wrote:
> On Tue, Apr 17, 2012 at 12:06 PM, James Cammarata wrote:
>>
>> Yes mine looks the same, and my install.log contains the epoch time
>> stamp (not the formated one you had). Can you check the
>> cobbler/modules/install_{pre,post}_log.py files
On Tue, Apr 17, 2012 at 12:06 PM, James Cammarata wrote:
> Yes mine looks the same, and my install.log contains the epoch time
> stamp (not the formated one you had). Can you check the
> cobbler/modules/install_{pre,post}_log.py files on your system? They
> look like this in the master branch:
>
On Mon, Apr 16, 2012 at 8:53 PM, Gonzalo Servat
wrote:
> On Tue, Apr 17, 2012 at 11:40 AM, James Cammarata wrote:
>>
>>
>> Is that 2.2.1-1? I'm running of the master branch and don't see that
>> traceback:
>>
>> # cobbler status
>> ip |target |start |state
>> 1
On Tue, Apr 17, 2012 at 11:40 AM, James Cammarata wrote:
>
> Is that 2.2.1-1? I'm running of the master branch and don't see that
> traceback:
>
> # cobbler status
> ip |target |start|state
> 192.168.x.x |system:sl6test |Sun Mar 25 21:10:55 2012|finished
On Mon, Apr 16, 2012 at 7:55 PM, Gonzalo Servat
wrote:
> Hi,
>
> Not sure if anyone else has run into this issue, but I thought I'd report
> back just in case someone does.
>
> Issuing a "cobbler status" to see when systems were installed did not work
> for me with the following error:
>
> Tue Apr
Hi,
Not sure if anyone else has run into this issue, but I thought I'd report
back just in case someone does.
Issuing a "cobbler status" to see when systems were installed did not work
for me with the following error:
Tue Apr 17 10:41:09 2012 - INFO | Exception occured:
Tue Apr 17 10:41:09 2012
On Mon, Apr 16, 2012 at 7:29 PM, Gonzalo Servat
wrote:
> On Tue, Apr 17, 2012 at 10:26 AM, James Cammarata wrote:
>>
>> On Mon, Apr 16, 2012 at 7:17 PM, Gonzalo Servat
>> wrote:
>> > Hi All,
>> >
>> > I've just upgraded from 2.0.x to 2.2.x and finding a few minor issues,
>> > such
>> > as koan w
On Tue, Apr 17, 2012 at 10:26 AM, James Cammarata wrote:
> On Mon, Apr 16, 2012 at 7:17 PM, Gonzalo Servat
> wrote:
> > Hi All,
> >
> > I've just upgraded from 2.0.x to 2.2.x and finding a few minor issues,
> such
> > as koan wanting to connect by default to port 25151. Cobbler only binds
> to
>
On Mon, Apr 16, 2012 at 7:17 PM, Gonzalo Servat
wrote:
> Hi All,
>
> I've just upgraded from 2.0.x to 2.2.x and finding a few minor issues, such
> as koan wanting to connect by default to port 25151. Cobbler only binds to
> 127.0.0.1:25151, so the only way to get koan to work is by specifying "-t
Hi All,
I've just upgraded from 2.0.x to 2.2.x and finding a few minor issues, such
as koan wanting to connect by default to port 25151. Cobbler only binds to
127.0.0.1:25151, so the only way to get koan to work is by specifying "-t
80". In Koan/Cobbler 2.0.x, this was not the case.
Did something
On Mon, Apr 16, 2012 at 5:01 PM, Colin Leavett-Brown wrote:
> On Scientific Linux 6.2. Under cobbler-2.0.11-2.el6.noarch, with a
> setting of "pxe_just_once: 1", and kiskstart entries of
> "%pre\n$kickstart_start" and "%post\n$kickstart_done" worked perfectly;
> "--netboot-enabled=true" did not re
I believe pxelinux.0 will do the same thing regardless. Is the DHCP server
Linux too? Can you do a trace to confirm the correct offer is being given and
accepted?
The process is like so:
1) PXE BIOS sends DHCP request
2) DHCP server replies with IP address, bootfile-name [i.e. "/pxelinux.0"],
ne
On Scientific Linux 6.2. Under cobbler-2.0.11-2.el6.noarch, with a
setting of "pxe_just_once: 1", and kiskstart entries of
"%pre\n$kickstart_start" and "%post\n$kickstart_done" worked perfectly;
"--netboot-enabled=true" did not result in a pxe boot/install loop.
However, after upgrading to cobble
Not sure why you got put in my spam box, but you did :(... Anyway, the
pxelinux.0 file are the same across all of the cobbler servers per an md5sum
check.
- Original Message -
From: "Mann, Owen"
To: cobbler mailing list
Cc:
Sent: Monday, March 26, 2012 3:49 PM
Subject: Re: [cobble
Hello,
I have the following setup with cobbler. "QA" which servers the QA and
testing environments which once approved goes to "PROD" which is the master for
all other locations to replicate from.
Here is my issue.
My QA machine is replicating repos as it has been for quite some time without
16 matches
Mail list logo
