I've setup a repo in foreman on the same host as forman, but with a
different port (8080). When I assign an os using this installation media,
build fails with the following error:
Failed to enable client.test.com for installation: Failed to fetch boot
files: invalid medium for CentOS 5.6
The logs do not show what it is trying to fetch or what the actual failure
is. Why does this happen and how do I find out what it was trying to fetch?
> I've setup a repo in foreman on the same host as forman, but with a
> different port (8080). When I assign an os using this installation media,
> build fails with the following error:
>
> Failed to enable client.test.com for installation: Failed to fetch boot
> files: invalid medium for CentOS 5.6
>
> The logs do not show what it is trying to fetch or what the actual failure
> is. Why does this happen and how do I find out what it was trying to fetch?
>
Look at the proxy log files.
Ohad
···
On Thu, Sep 1, 2011 at 9:46 PM, lavaman wrote:
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
08:00:27:f5:5b:f3 created successfully
D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
08:00:27:f5:5b:f3 removed successfully
I’ve setup a repo in foreman on the same host as forman, but with a
different port (8080). When I assign an os using this installation
media,
build fails with the following error:
Failed to enable client.test.com for installation: Failed to fetch boot
files: invalid medium for CentOS 5.6
The logs do not show what it is trying to fetch or what the actual
failure
is. Why does this happen and how do I find out what it was trying to
fetch?
> All I see come up is this:
>
> I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
> 08:00:27:f5:5b:f3 created successfully
> D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
> 08:00:27:f5:5b:f3 removed successfully
>
> This is what's in the foreman log:
>
> Processing HostsController#setBuild (for 192.168.2.4 at 2011-08-31 21:58:20)
> [GET]
> Parameters: {"action"=>"setBuild", "id"=>"client.test.com",
> "controller"=>"hosts"}
> Add the TFTP configuration for client.test.com
> Fetching required TFTP boot files for client.test.com
> Failed to fetch boot files: invalid medium for CentOS 5.6
> Delete the TFTP configuration for client.test.com
> Redirected to http://192.168.2.14/hosts/client.test.com
> Completed in 169ms (DB: 49) | 302 Found
> [http://192.168.2.14/hosts/client.test.com/setBuild]
Hmm… according to the code, your media does not belong to the OS in
question, I guess you removed one of the check boxes.
Ohad
···
On Thu, Sep 1, 2011 at 9:56 PM, lavaman wrote:
>
>
> On Thu, Sep 1, 2011 at 12:47 PM, Ohad Levy wrote:
>>
>> On Thu, Sep 1, 2011 at 9:46 PM, lavaman wrote:
>> > I've setup a repo in foreman on the same host as forman, but with a
>> > different port (8080). When I assign an os using this installation
>> > media,
>> > build fails with the following error:
>> >
>> > Failed to enable client.test.com for installation: Failed to fetch boot
>> > files: invalid medium for CentOS 5.6
>> >
>> > The logs do not show what it is trying to fetch or what the actual
>> > failure
>> > is. Why does this happen and how do I find out what it was trying to
>> > fetch?
>> >
>> Look at the proxy log files.
>>
>> Ohad
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Foreman users" group.
>> > To post to this group, send email to foreman-users@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > foreman-users+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/foreman-users?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
08:00:27:f5:5b:f3 created successfully
D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
08:00:27:f5:5b:f3 removed successfully
I’ve setup a repo in foreman on the same host as forman, but with a
different port (8080). When I assign an os using this installation
media,
build fails with the following error:
Failed to enable client.test.com for installation: Failed to fetch
boot
files: invalid medium for CentOS 5.6
The logs do not show what it is trying to fetch or what the actual
failure
is. Why does this happen and how do I find out what it was trying to
fetch?
> It's checked and it's the only media checked on the os page…
>
You should double check, the code simply check if the media select
belongs to the OS allowed mediums… whicn in you case does not.
(e…g it make no sense to deploy Ubuntu with a suse media).
Ohad
···
On Thu, Sep 1, 2011 at 10:38 PM, lavaman wrote:
> On Thu, Sep 1, 2011 at 12:59 PM, Ohad Levy wrote:
>>
>> On Thu, Sep 1, 2011 at 9:56 PM, lavaman wrote:
>> > All I see come up is this:
>> >
>> > I, [2011-08-31T21:58:21.013411 #8214] INFO -- : TFTP: entry for
>> > 08:00:27:f5:5b:f3 created successfully
>> > D, [2011-08-31T21:58:21.042760 #8214] DEBUG -- : TFTP: entry for
>> > 08:00:27:f5:5b:f3 removed successfully
>> >
>> > This is what's in the foreman log:
>> >
>> > Processing HostsController#setBuild (for 192.168.2.4 at 2011-08-31
>> > 21:58:20)
>> > [GET]
>> > Parameters: {"action"=>"setBuild", "id"=>"client.test.com",
>> > "controller"=>"hosts"}
>> > Add the TFTP configuration for client.test.com
>> > Fetching required TFTP boot files for client.test.com
>> > Failed to fetch boot files: invalid medium for CentOS 5.6
>> > Delete the TFTP configuration for client.test.com
>> > Redirected to http://192.168.2.14/hosts/client.test.com
>> > Completed in 169ms (DB: 49) | 302 Found
>> > [http://192.168.2.14/hosts/client.test.com/setBuild]
>>
>> Hmm.. according to the code, your media does not belong to the OS in
>> question, I guess you removed one of the check boxes.
>>
>>
>> Ohad
>> >
>> >
>> > On Thu, Sep 1, 2011 at 12:47 PM, Ohad Levy wrote:
>> >>
>> >> On Thu, Sep 1, 2011 at 9:46 PM, lavaman wrote:
>> >> > I've setup a repo in foreman on the same host as forman, but with a
>> >> > different port (8080). When I assign an os using this installation
>> >> > media,
>> >> > build fails with the following error:
>> >> >
>> >> > Failed to enable client.test.com for installation: Failed to fetch
>> >> > boot
>> >> > files: invalid medium for CentOS 5.6
>> >> >
>> >> > The logs do not show what it is trying to fetch or what the actual
>> >> > failure
>> >> > is. Why does this happen and how do I find out what it was trying to
>> >> > fetch?
>> >> >
>> >> Look at the proxy log files.
>> >>
>> >> Ohad
>> >> > --
>> >> > You received this message because you are subscribed to the Google
>> >> > Groups
>> >> > "Foreman users" group.
>> >> > To post to this group, send email to foreman-users@googlegroups.com.
>> >> > To unsubscribe from this group, send email to
>> >> > foreman-users+unsubscribe@googlegroups.com.
>> >> > For more options, visit this group at
>> >> > http://groups.google.com/group/foreman-users?hl=en.
>> >> >
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Foreman users" group.
>> >> To post to this group, send email to foreman-users@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>> >> foreman-users+unsubscribe@googlegroups.com.
>> >> For more options, visit this group at
>> >> http://groups.google.com/group/foreman-users?hl=en.
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "Foreman users" group.
>> > To post to this group, send email to foreman-users@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > foreman-users+unsubscribe@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/foreman-users?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> foreman-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
If I edit the installation media, the proper OS is checked (I only have one
OS configured). If I edit the OS, the proper media is checked (and it's the
only one checked).
···
On Thu, Sep 1, 2011 at 1:47 PM, Ohad Levy wrote:
I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
08:00:27:f5:5b:f3 created successfully
D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
08:00:27:f5:5b:f3 removed successfully
I’ve setup a repo in foreman on the same host as forman, but with a
different port (8080). When I assign an os using this installation
media,
build fails with the following error:
Failed to enable client.test.com for installation: Failed to fetch
boot
files: invalid medium for CentOS 5.6
The logs do not show what it is trying to fetch or what the actual
failure
is. Why does this happen and how do I find out what it was trying
to
fetch?
Look at the proxy log files.
Ohad
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
It looks like I might have found a bug. It would seem that if the
installation media is created after the OS is created, the OS cannot use
it. If you create the OS after the installation media is created, it
doesn't complain…
···
On Thu, Sep 1, 2011 at 1:53 PM, lavaman wrote:
If I edit the installation media, the proper OS is checked (I only have one
OS configured). If I edit the OS, the proper media is checked (and it’s the
only one checked).
I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
08:00:27:f5:5b:f3 created successfully
D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
08:00:27:f5:5b:f3 removed successfully
I’ve setup a repo in foreman on the same host as forman, but with
a
different port (8080). When I assign an os using this
installation
media,
build fails with the following error:
Failed to enable client.test.com for installation: Failed to
fetch
boot
files: invalid medium for CentOS 5.6
The logs do not show what it is trying to fetch or what the actual
failure
is. Why does this happen and how do I find out what it was trying
to
fetch?
Look at the proxy log files.
Ohad
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com
.
> It looks like I might have found a bug. It would seem that if the
> installation media is created after the OS is created, the OS cannot use
> it. If you create the OS after the installation media is created, it
> doesn't complain…
I just tried and I cant reproduce this… can you provide a step by
step example of how it fails?
thanks,
Ohad
···
On Fri, Sep 2, 2011 at 10:35 PM, lavaman wrote:
>
> On Thu, Sep 1, 2011 at 1:53 PM, lavaman wrote:
>>
>> If I edit the installation media, the proper OS is checked (I only have
>> one OS configured). If I edit the OS, the proper media is checked (and it's
>> the only one checked).
>>
>> On Thu, Sep 1, 2011 at 1:47 PM, Ohad Levy wrote:
>>>
>>> On Thu, Sep 1, 2011 at 10:38 PM, lavaman wrote:
>>> > It's checked and it's the only media checked on the os page...
>>> >
>>> You should double check, the code simply check if the media select
>>> belongs to the OS allowed mediums... whicn in you case does not.
>>>
>>> (e..g it make no sense to deploy Ubuntu with a suse media).
>>>
>>> Ohad
>>> > On Thu, Sep 1, 2011 at 12:59 PM, Ohad Levy wrote:
>>> >>
>>> >> On Thu, Sep 1, 2011 at 9:56 PM, lavaman wrote:
>>> >> > All I see come up is this:
>>> >> >
>>> >> > I, [2011-08-31T21:58:21.013411 #8214] INFO -- : TFTP: entry for
>>> >> > 08:00:27:f5:5b:f3 created successfully
>>> >> > D, [2011-08-31T21:58:21.042760 #8214] DEBUG -- : TFTP: entry for
>>> >> > 08:00:27:f5:5b:f3 removed successfully
>>> >> >
>>> >> > This is what's in the foreman log:
>>> >> >
>>> >> > Processing HostsController#setBuild (for 192.168.2.4 at 2011-08-31
>>> >> > 21:58:20)
>>> >> > [GET]
>>> >> > Parameters: {"action"=>"setBuild", "id"=>"client.test.com",
>>> >> > "controller"=>"hosts"}
>>> >> > Add the TFTP configuration for client.test.com
>>> >> > Fetching required TFTP boot files for client.test.com
>>> >> > Failed to fetch boot files: invalid medium for CentOS 5.6
>>> >> > Delete the TFTP configuration for client.test.com
>>> >> > Redirected to http://192.168.2.14/hosts/client.test.com
>>> >> > Completed in 169ms (DB: 49) | 302 Found
>>> >> > [http://192.168.2.14/hosts/client.test.com/setBuild]
>>> >>
>>> >> Hmm.. according to the code, your media does not belong to the OS in
>>> >> question, I guess you removed one of the check boxes.
>>> >>
>>> >>
>>> >> Ohad
>>> >> >
>>> >> >
>>> >> > On Thu, Sep 1, 2011 at 12:47 PM, Ohad Levy >>> >> > wrote:
>>> >> >>
>>> >> >> On Thu, Sep 1, 2011 at 9:46 PM, lavaman wrote:
>>> >> >> > I've setup a repo in foreman on the same host as forman, but with
>>> >> >> > a
>>> >> >> > different port (8080). When I assign an os using this
>>> >> >> > installation
>>> >> >> > media,
>>> >> >> > build fails with the following error:
>>> >> >> >
>>> >> >> > Failed to enable client.test.com for installation: Failed to
>>> >> >> > fetch
>>> >> >> > boot
>>> >> >> > files: invalid medium for CentOS 5.6
>>> >> >> >
>>> >> >> > The logs do not show what it is trying to fetch or what the
>>> >> >> > actual
>>> >> >> > failure
>>> >> >> > is. Why does this happen and how do I find out what it was
>>> >> >> > trying to
>>> >> >> > fetch?
>>> >> >> >
>>> >> >> Look at the proxy log files.
>>> >> >>
>>> >> >> Ohad
>>> >> >> > --
>>> >> >> > You received this message because you are subscribed to the
>>> >> >> > Google
>>> >> >> > Groups
>>> >> >> > "Foreman users" group.
>>> >> >> > To post to this group, send email to
>>> >> >> > foreman-users@googlegroups.com.
>>> >> >> > To unsubscribe from this group, send email to
>>> >> >> > foreman-users+unsubscribe@googlegroups.com.
>>> >> >> > For more options, visit this group at
>>> >> >> > http://groups.google.com/group/foreman-users?hl=en.
>>> >> >> >
>>> >> >>
>>> >> >> --
>>> >> >> You received this message because you are subscribed to the Google
>>> >> >> Groups
>>> >> >> "Foreman users" group.
>>> >> >> To post to this group, send email to
>>> >> >> foreman-users@googlegroups.com.
>>> >> >> To unsubscribe from this group, send email to
>>> >> >> foreman-users+unsubscribe@googlegroups.com.
>>> >> >> For more options, visit this group at
>>> >> >> http://groups.google.com/group/foreman-users?hl=en.
>>> >> >>
>>> >> >
>>> >> > --
>>> >> > You received this message because you are subscribed to the Google
>>> >> > Groups
>>> >> > "Foreman users" group.
>>> >> > To post to this group, send email to foreman-users@googlegroups.com.
>>> >> > To unsubscribe from this group, send email to
>>> >> > foreman-users+unsubscribe@googlegroups.com.
>>> >> > For more options, visit this group at
>>> >> > http://groups.google.com/group/foreman-users?hl=en.
>>> >> >
>>> >>
>>> >> --
>>> >> You received this message because you are subscribed to the Google
>>> >> Groups
>>> >> "Foreman users" group.
>>> >> To post to this group, send email to foreman-users@googlegroups.com.
>>> >> To unsubscribe from this group, send email to
>>> >> foreman-users+unsubscribe@googlegroups.com.
>>> >> For more options, visit this group at
>>> >> http://groups.google.com/group/foreman-users?hl=en.
>>> >>
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> > Groups
>>> > "Foreman users" group.
>>> > To post to this group, send email to foreman-users@googlegroups.com.
>>> > To unsubscribe from this group, send email to
>>> > foreman-users+unsubscribe@googlegroups.com.
>>> > For more options, visit this group at
>>> > http://groups.google.com/group/foreman-users?hl=en.
>>> >
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Foreman users" group.
>>> To post to this group, send email to foreman-users@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> foreman-users+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/foreman-users?hl=en.
>>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
Well, whatever was happening I can't reproduce in any way now. Now any
sensible combination of install media and os works fine. Not sure what was
going on.
I am running into another issue occasionally, which is sometimes when I try
to save a host (usually after changing the os setting), it tells me that the
puppetmaster must be puppet or an fqdn and won't recognize the proxy that is
set. If i manually enter puppet it will save and if i go back and change it
back to the proxy (without changing anything else) it will save fine. Any
idea why that happens?
···
On Fri, Sep 2, 2011 at 1:42 PM, Ohad Levy wrote:
It looks like I might have found a bug. It would seem that if the
installation media is created after the OS is created, the OS cannot use
it. If you create the OS after the installation media is created, it
doesn’t complain…
I just tried and I cant reproduce this… can you provide a step by
step example of how it fails?
I, [2011-08-31T21:58:21.013411 #8214] INFO – : TFTP: entry for
08:00:27:f5:5b:f3 created successfully
D, [2011-08-31T21:58:21.042760 #8214] DEBUG – : TFTP: entry for
08:00:27:f5:5b:f3 removed successfully
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com.
–
You received this message because you are subscribed to the Google
Groups
"Foreman users" group.
To post to this group, send email to foreman-users@googlegroups.com
.