Strange behaviour after cobbler import

[Mark Brandis]

Hi!

I have a strange problem after a cobbler import. I do the following:

cobbler import --arch=i386 --path=/mnt/cdrom --name=foo

This works without problems. When I want to install with pxe after that command finishes
the boot stops after the pxe lines with the error:

unable to locate configuration file

A "cobber sync" on the command line does not help, a sync in the webui makes the
problem go away.

Strange!?!

Mark

[Michael DeHaan]

mark.brandis(a)gmx.de wrote:
>  Hi!
>
>  I have a strange problem after a cobbler import. I do the following:
>
>  cobbler import --arch=i386 --path=/mnt/cdrom --name=foo
>
>  This works without problems. When I want to install with pxe after that command finishes
> the boot stops after the pxe lines with the error:
>
>  unable to locate configuration file
>
>  A "cobber sync" on the command line does not help, a sync in the webui makes
> the problem go away.
>
>  Strange!?!
>
>  Mark
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
What version of cobbler are you running?

# rpm -q cobbler

A web app sync is the same as the command line sync.

[Mark Brandis]

>  mark.brandis(a)gmx.de wrote:
>  > I have a strange problem after a cobbler import. I do the following:
>  >
>  > cobbler import --arch=i386 --path=/mnt/cdrom --name=foo
>  >
>  > This works without problems. When I want to install with pxe after that
>  command finishes the boot stops after the pxe lines with the error:
>  >
>  > unable to locate configuration file
>  >
>  > A "cobber sync" on the command line does not help, a sync in the webui
>  makes the problem go away.
>  
>  What version of cobbler are you running?
>  
>  # rpm -q cobbler 
cobbler-1.0.3-1.fc9.noarch

>  A web app sync is the same as the command line sync. 
That I know.

Mark

[Michael DeHaan]

mark.brandis(a)gmx.de wrote:
> > mark.brandis(a)gmx.de wrote:
> >     
> >> I have a strange problem after a cobbler import. I do the following:
> >>
> >> cobbler import --arch=i386 --path=/mnt/cdrom --name=foo
> >>
> >> This works without problems. When I want to install with pxe after that
> >>       
> > command finishes the boot stops after the pxe lines with the error:
> >     
> >> unable to locate configuration file
> >>
> >> A "cobber sync" on the command line does not help, a sync in the webui
> >>       
> > makes the problem go away.
> >
> > What version of cobbler are you running?
> >
> > # rpm -q cobbler
> >     
>
>  cobbler-1.0.3-1.fc9.noarch
>
>     
The latest version is 1.2.5, which contains many code changes both in 
terms of features and fixes.    If you upgrade and still have this 
problem with a new import we can address that with 1.2.X (and also 
1.3.X), though we're not going to make changes to 1.0.X

> > A web app sync is the same as the command line sync.
> >     
>
>  That I know.
>
>     
You indicated they performed differently?   This also could be a 1.0.X 
related item.

>  Mark
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Mark Brandis]

Hi!

I'm now running cobbler-1.2.8-1.fc9.noarch and still have the
"configuration file not found" problem after an import. And still the
"cobbler sync" on the command line does not fix the problem, but the web
sync does.

Mark

Am Thursday 09 October 2008 schrieb Michael DeHaan:
>  mark.brandis(a)gmx.de wrote:
>  >> mark.brandis(a)gmx.de wrote:
>  >>> I have a strange problem after a cobbler import. I do the following:
>  >>>
>  >>> cobbler import --arch=i386 --path=/mnt/cdrom --name=foo
>  >>>
>  >>> This works without problems. When I want to install with pxe after that
>  >>
>  >> command finishes the boot stops after the pxe lines with the error:
>  >>> unable to locate configuration file
>  >>>
>  >>> A "cobber sync" on the command line does not help, a sync in the
> webui
>  >>
>  >> makes the problem go away.
>  >>
>  >> What version of cobbler are you running?
>  >>
>  >> # rpm -q cobbler
>  >
>  > cobbler-1.0.3-1.fc9.noarch
>
>  The latest version is 1.2.5, which contains many code changes both in
>  terms of features and fixes.    If you upgrade and still have this
>  problem with a new import we can address that with 1.2.X (and also
>  1.3.X), though we're not going to make changes to 1.0.X
>
>  >> A web app sync is the same as the command line sync.
>  >
>  > That I know.
>
>  You indicated they performed differently?   This also could be a 1.0.X
>  related item.
>
>  > Mark
>  > _______________________________________________
>  > cobbler mailing list
>  > cobbler(a)lists.fedorahosted.org
>  > https://fedorahosted.org/mailman/listinfo/cobbler
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler 
-- 
And ever has it been known that love knows not its own depth until the
hour of separation.
		-- Kahlil Gibran

[Michael DeHaan]

Mark Brandis wrote:
>  Hi!
>
>  I'm now running cobbler-1.2.8-1.fc9.noarch and still have the
>  "configuration file not found" problem after an import. And still the
>  "cobbler sync" on the command line does not fix the problem, but the web
>  sync does.
>
>     
I'm pretty sure they are the same. You may have some intermittent 
problem being caused by other factors. That all being said, I'm not 
exactly sure what the problem is either.

It /almost/ sounds like you might have dualing DHCP servers on your 
network and the other isn't set up for PXE, so things are just coming 
down to chance as to which one you are trying to install from.

Does "After the PXE lines" mean "inside of syslinux" ?

--Michael





>  Mark
>
>  Am Thursday 09 October 2008 schrieb Michael DeHaan:
>    
> > mark.brandis(a)gmx.de wrote:
> >     
> >>> mark.brandis(a)gmx.de wrote:
> >>>         
> >>>> I have a strange problem after a cobbler import. I do the following:
> >>>>
> >>>> cobbler import --arch=i386 --path=/mnt/cdrom --name=foo
> >>>>
> >>>> This works without problems. When I want to install with pxe after that
> >>>>           
> >>> command finishes the boot stops after the pxe lines with the error:
> >>>         
> >>>> unable to locate configuration file
> >>>>
> >>>> A "cobber sync" on the command line does not help, a sync in
> the webui
> >>>>           
> >>> makes the problem go away.
> >>>
> >>> What version of cobbler are you running?
> >>>
> >>> # rpm -q cobbler
> >>>         
> >> cobbler-1.0.3-1.fc9.noarch
> >>       
> > The latest version is 1.2.5, which contains many code changes both in
> > terms of features and fixes.    If you upgrade and still have this
> > problem with a new import we can address that with 1.2.X (and also
> > 1.3.X), though we're not going to make changes to 1.0.X
> >
> >     
> >>> A web app sync is the same as the command line sync.
> >>>         
> >> That I know.
> >>       
> > You indicated they performed differently?   This also could be a 1.0.X
> > related item.
> >
> >     
> >> Mark
> >> _______________________________________________
> >> cobbler mailing list
> >> cobbler(a)lists.fedorahosted.org
> >> https://fedorahosted.org/mailman/listinfo/cobbler
> >>       
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >

Strange behavior after cobbler import

[Mark Brandis]

Am Wednesday 05 November 2008 schrieb Michael DeHaan:
>  Does "After the PXE lines" mean "inside of
> syslinux" ? 
I have the following configuration:
- MS DHCP Server (can't do anything about that)
- F9 Cobbler and tftp Server, this server is configured to show a prompt 
before installing to prevent accidental installations.

The computer to be installed starts into network boot, tries to get a IP from 
the DHCP Server and does this successfully. Then the DHCP Server gives the IP 
of the tftp server to the computer and the computer receives the first data 
from the tftp server (at least I think so).

You can see something like this on the screen:

/tftp/pxelinux...

And directly before the prompt should be shown (it is really only the prompt 
that is missing) the error shows.

Mark