Trouble with Solaris Installations

Luke_Kearney · April 18, 2013, 3:59am

Hello,

I am having some troubles installing Solaris 10, not sure where the problems are as I suspect there is more than one. I see the host pxeboot and then it appears to mount its NFS directory fine and then hangs - wondering if it is looking for templates. When I try to inspect any of the templates via the host page I only get errors.

Where would I go to start debugging and fixing this?

There was an error rendering the Jumpstart default PXEGrub template: undefined method `multiboot' for #<#<Class:0x7ff22ab4cc78>:0x7ff22a7e8f78>

There was an error rendering the Jumstart Default Finish template: undefined method 'root_pass' for Host::Jail (Host)

There was an error rendering the Jumpstart Default template: undefined method 'use_image' for Host::Jail (Host)

Kind Regards,

Sean_Alderman · May 31, 2013, 8:52pm

Were you able to get this resolved?

I'm having similar behaviour in my lab, I just started playing with Solaris
today.

The /var/log/foreman/production.log file shows:
Started GET "/unattended/PXEGrub?spoof=192.168.100.19" for 192.168.100.100
at Fri May 31 16:26:55 -0400 2013
Processing by UnattendedController#PXEGrub as HTML
Parameters: {"spoof"=>"192.168.100.19"}
Found solaris1.int.localnet
Rendered inline template (45.3ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 107ms (Views: 1.1ms | ActiveRecord:
0.0ms)

Not quite sure how to get more info about the 500 error.

I also had issues with using NFS as the media source. I have logs from the
Smart-Proxy about failing to copy the multiboot and miniroot files over to
the tfptroot because wget doesn't like nfs://<server>/<path> as Install
Media Path.

I'll dig more on Monday.

···

On Wednesday, April 17, 2013 11:59:17 PM UTC-4, lu...@kearney.jp wrote: > > > Hello, > > I am having some troubles installing Solaris 10, not sure where > the problems are as I suspect there is more than one. I see the host > pxeboot and then it appears to mount its NFS directory fine and then hangs > - wondering if it is looking for templates. When I try to inspect any of > the templates via the host page I only get errors. > > Where would I go to start debugging and fixing this? > > > There was an error rendering the Jumpstart default PXEGrub template: > undefined method `multiboot' for #<#:0x7ff22a7e8f78> > > > There was an error rendering the Jumstart Default Finish template: undefined method 'root_pass' for Host::Jail (Host) > > > > There was an error rendering the Jumpstart Default template: undefined method 'use_image' for Host::Jail (Host) > > > Kind Regards, >

lzap · June 12, 2013, 11:08am

Hey!

Would you mind providing us full stack traces? Best with foreman-debug
tool which is present in 1.2 RC2+ or can be downloaded from our git:

http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#How-to-provide-enough-info-to-get-help

Thanks!

LZ

···

On Thu, Apr 18, 2013 at 12:59:17PM +0900, Luke Kearney wrote: > > Hello, > > I am having some troubles installing Solaris 10, not sure where the problems are as I suspect there is more than one. I see the host pxeboot and then it appears to mount its NFS directory fine and then hangs - wondering if it is looking for templates. When I try to inspect any of the templates via the host page I only get errors. > > Where would I go to start debugging and fixing this? > > > There was an error rendering the Jumpstart default PXEGrub template: undefined method `multiboot' for #<#:0x7ff22a7e8f78> > > There was an error rendering the Jumstart Default Finish template: undefined method 'root_pass' for Host::Jail (Host) > > There was an error rendering the Jumpstart Default template: undefined method 'use_image' for Host::Jail (Host) > > Kind Regards, > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > >

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

Dominic_Cleal1 · June 1, 2013, 11:11am

> Were you able to get this resolved?
>
> I'm having similar behaviour in my lab, I just started playing with
> Solaris today.
>
> The /var/log/foreman/production.log file shows:
> Started GET "/unattended/PXEGrub?spoof=192.168.100.19" for
> 192.168.100.100 at Fri May 31 16:26:55 -0400 2013
> Processing by UnattendedController#PXEGrub as HTML
> Parameters: {"spoof"=>"192.168.100.19"}
> Found solaris1.int.localnet
> Rendered inline template (45.3ms)
> Rendered text template (0.0ms)
> Completed 500 Internal Server Error in 107ms (Views: 1.1ms |
> ActiveRecord: 0.0ms)
>
> Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a rendering
error that you can reproduce from there.

> I also had issues with using NFS as the media source. I have logs from
> the Smart-Proxy about failing to copy the multiboot and miniroot files
> over to the tfptroot because wget doesn't like nfs://<server>/<path> as
> Install Media Path.

Perhaps just provide the media over HTTP, then if you create a Solaris
OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

···

On 31/05/13 21:52, Sean Alderman wrote:

–
Dominic Cleal
Red Hat Engineering

Sean_Alderman · June 3, 2013, 5:05pm

Dominic,
Thanks for your thoughts! I appreciate the ideas, I hope this post will
provide more relevant information now that I've had a change to investigate
some more.

> Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a rendering
error that you can reproduce from there.

The error I pasted was generated from previewing the host template. When
the target system boots it gets passed the PXEGrub loader and pulls the
install kernel from the tftp server. After loading that kernel it ends
during Foreman's rendering of the PXEGrub Jumpstart Provisioning Template
(as shown in the screen shot attached). This "There" is also the first
word presented in the browser when previewing the template from the Host.
Foreman responds to the browser with:

There was an error rendering the Jumpstart Default template: undefined
method 'use_image' for Host::Jail (Host)

> Install Media Path.

Perhaps just provide the media over HTTP, then if you create a Solaris
OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

I'm not as interested in this issue since I've worked around it by manually
copying the boot files into /var/lib/tftpboot. I just wanted to bring it
into the light.

Using NFS is clearly an option for the Media URL, the helps in the
GUI suggest how to accomplish it. Is this a possible Smart Proxy Bug?
Following the Solaris Unattended Install Wiki to the letter and
setting the media path to the HTTP URL, where "server" is my Foreman
server, produces a 404 with 0 byte tftp kernel files. So I tried NFS and
found that wget doesn't like NFS URI's.

Thanks for your help!

Kind regards,

···

-- Sean M. Alderman Senior Engineer, UDit Systems Integration and Engineering University of Dayton

On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal dcleal@redhat.com wrote:

On 31/05/13 21:52, Sean Alderman wrote:

Were you able to get this resolved?

I’m having similar behaviour in my lab, I just started playing with
Solaris today.

The /var/log/foreman/production.log file shows:
Started GET “/unattended/PXEGrub?spoof=192.168.100.19” for
192.168.100.100 at Fri May 31 16:26:55 -0400 2013
Processing by UnattendedController#PXEGrub as HTML
Parameters: {“spoof”=>“192.168.100.19”}
Found solaris1.int.localnet
Rendered inline template (45.3ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 107ms (Views: 1.1ms |
ActiveRecord: 0.0ms)

Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a rendering
error that you can reproduce from there.

I also had issues with using NFS as the media source. I have logs from
the Smart-Proxy about failing to copy the multiboot and miniroot files
over to the tfptroot because wget doesn’t like nfs:/// as
Install Media Path.

Perhaps just provide the media over HTTP, then if you create a Solaris
OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google Groups
“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Sean_Alderman · June 11, 2013, 2:11pm

Circling back on this one… I still can't seem to get a Solaris build
happening.

Pasted here are the outputs from logs on my
Foreman/DHCP/TFTP/DNS/PuppetMaster server named firewall from powering the
Solaris Target Host on through its failure noted by the image posted in the
previous message, to an attempt to preview the template via the Foreman UI
:
==> /var/log/messages <==
Jun 11 10:03:22 firewall dhcpd: DHCPDISCOVER from 08:00:27:7e:27:fe via eth2
Jun 11 10:03:22 firewall dhcpd: DHCPOFFER on 192.168.100.19 to
08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall dhcpd: DHCPREQUEST for 192.168.100.19
(192.168.100.1) from 08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall dhcpd: DHCPACK on 192.168.100.19 to
08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall in.tftpd[2965]: RRQ from 192.168.100.19 filename
Solaris-5.10-hw0811-pxegrub
Jun 11 10:03:29 firewall in.tftpd[2967]: RRQ from 192.168.100.19 filename
menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2968]: RRQ from 192.168.100.19 filename
menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2969]: RRQ from 192.168.100.19 filename
menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2970]: RRQ from 192.168.100.19 filename
menu.lst.010800277E27FE
Jun 11 10:03:30 firewall in.tftpd[2973]: RRQ from 192.168.100.19 filename
boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2974]: RRQ from 192.168.100.19 filename
boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2975]: RRQ from 192.168.100.19 filename
boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2976]: RRQ from 192.168.100.19 filename
boot/Solaris-5.10-hw0811-x86.miniroot
Jun 11 10:03:49 firewall in.tftpd[2984]: RRQ from 192.168.100.19 filename
boot/Solaris-5.10-hw0811-x86.miniroot
Jun 11 10:04:22 firewall dhcpd: DHCPREQUEST for 192.168.100.19 from
08:00:27:7e:27:fe via eth2
Jun 11 10:04:22 firewall dhcpd: DHCPACK on 192.168.100.19 to
08:00:27:7e:27:fe via eth2

==> /var/log/foreman-proxy/proxy.log <==
D, [2013-06-11T10:04:48.270726 #1984] DEBUG – : Found puppetca at
/usr/bin/puppet
D, [2013-06-11T10:04:48.271333 #1984] DEBUG – : Found sudo at /usr/bin/sudo
D, [2013-06-11T10:04:48.271547 #1984] DEBUG – : Executing /usr/bin/sudo -S
/usr/bin/puppet cert --clean solaris1.int.localnet
I, [2013-06-11T10:04:50.005855 #1984] INFO – : Attempt to remove
nonexistant client certificate for solaris1.int.localnet
E, [2013-06-11T10:04:50.006451 #1984] ERROR – : Attempt to remove
nonexistant client certificate for solaris1.int.localnet
I, [2013-06-11T10:04:50.130226 #1984] INFO – : Added
solaris1.int.localnet to autosign

==> /var/log/foreman/production.log <==

Started GET "/unattended/provision" for 192.168.100.19 at Tue Jun 11
10:04:48 -0400 2013
Processing by UnattendedController#provision as
Found solaris1.int.localnet
Remove puppet certificate for solaris1.int.localnet
Adding autosign entry for solaris1.int.localnet
Rendered inline template (19.2ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 2163ms (Views: 0.9ms | ActiveRecord:
0.0ms)

==> /var/log/httpd/access_log <==
192.168.100.19 - - [11/Jun/2013:10:04:48 -0400] "GET /unattended/provision
HTTP/1.1" 500 111 "-" "curl/7.19.6 (i386-pc-solaris2.10) libcurl/7.19.6
OpenSSL/0.9.7g"

==> /var/log/foreman/production.log <==

Started GET "/unattended/provision?spoof=192.168.100.19" for
192.168.100.100 at Tue Jun 11 10:05:22 -0400 2013
Processing by UnattendedController#provision as HTML
Parameters: {"spoof"=>"192.168.100.19"}
Found solaris1.int.localnet
Rendered inline template (19.7ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 68ms (Views: 1.6ms | ActiveRecord:
0.0ms)

==> /var/log/httpd/access_log <==
192.168.100.100 - - [11/Jun/2013:10:05:22 -0400] "GET
/unattended/provision?spoof=192.168.100.19 HTTP/1.1" 500 111
"https://firewall/hosts/solaris1.int.localnet" "Mozilla/5.0 (Windows NT
6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110
Safari/537.36"

The browser output from the template view is:

There was an error rendering the Jumpstart Default template: undefined
method 'use_image' for Host::Jail (Host)

This matches what the Solaris Target Host sees in referencing "There" being
an invalid keyword.

Is it possible to get more detail about this 500 error that appears in the
/var/log/foreman/production.log file?..am I just looking in the wrong log
file?

Thanks.

···

On Monday, June 3, 2013 1:05:32 PM UTC-4, Sean Alderman wrote: > > Dominic, > Thanks for your thoughts! I appreciate the ideas, I hope this post will > provide more relevant information now that I've had a change to investigate > some more. > > > Not quite sure how to get more info about the 500 error. > > Try previewing the template from the host page, it might be a rendering > error that you can reproduce from there. > > The error I pasted was generated from previewing the host template. When > the target system boots it gets passed the PXEGrub loader and pulls the > install kernel from the tftp server. After loading that kernel it ends > during Foreman's rendering of the PXEGrub Jumpstart Provisioning Template > (as shown in the screen shot attached). This "There" is also the first > word presented in the browser when previewing the template from the Host. > Foreman responds to the browser with: > > There was an error rendering the Jumpstart Default template: undefined > method 'use_image' for Host::Jail (Host) > > > Install Media Path. > > Perhaps just provide the media over HTTP, then if you create a Solaris > OS and associate it with the mirror, I believe you can enter the NFS > paths as well. > > I'm not as interested in this issue since I've worked around it by > manually copying the boot files into /var/lib/tftpboot. I just wanted to > bring it into the light. > > 1. Using NFS is clearly an option for the Media URL, the helps in the > GUI suggest how to accomplish it. Is this a possible Smart Proxy Bug? > 2. Following the Solaris Unattended Install Wiki to the letter and > setting the media path to the HTTP URL, where "server" is my Foreman > server, produces a 404 with 0 byte tftp kernel files. So I tried NFS and > found that wget doesn't like NFS URI's. > > Thanks for your help! > > Kind regards, > -- > Sean M. Alderman > Senior Engineer, UDit Systems Integration and Engineering > University of Dayton > > > On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal wrote: > >> On 31/05/13 21:52, Sean Alderman wrote: >> > Were you able to get this resolved? >> > >> > I'm having similar behaviour in my lab, I just started playing with >> > Solaris today. >> > >> > The /var/log/foreman/production.log file shows: >> > Started GET "/unattended/PXEGrub?spoof=192.168.100.19" for >> > 192.168.100.100 at Fri May 31 16:26:55 -0400 2013 >> > Processing by UnattendedController#PXEGrub as HTML >> > Parameters: {"spoof"=>"192.168.100.19"} >> > Found solaris1.int.localnet >> > Rendered inline template (45.3ms) >> > Rendered text template (0.0ms) >> > Completed 500 Internal Server Error in 107ms (Views: 1.1ms | >> > ActiveRecord: 0.0ms) >> > >> > Not quite sure how to get more info about the 500 error. >> >> Try previewing the template from the host page, it might be a rendering >> error that you can reproduce from there. >> >> > I also had issues with using NFS as the media source. I have logs from >> > the Smart-Proxy about failing to copy the multiboot and miniroot files >> > over to the tfptroot because wget doesn't like nfs:/// as >> > Install Media Path. >> >> Perhaps just provide the media over HTTP, then if you create a Solaris >> OS and associate it with the mirror, I believe you can enter the NFS >> paths as well. >> >> -- >> Dominic Cleal >> Red Hat Engineering >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-users+unsubscribe@googlegroups.com. >> To post to this group, send email to foreman-users@googlegroups.com. >> Visit this group at http://groups.google.com/group/foreman-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >

ohadlevy · June 11, 2013, 6:30pm

> Circling back on this one… I still can't seem to get a Solaris build
> happening.
>
> Pasted here are the outputs from logs on my
> Foreman/DHCP/TFTP/DNS/PuppetMaster server named firewall from powering the
> Solaris Target Host on through its failure noted by the image posted in the
> previous message, to an attempt to preview the template via the Foreman UI
> :
> ==> /var/log/messages <==
> Jun 11 10:03:22 firewall dhcpd: DHCPDISCOVER from 08:00:27:7e:27:fe via
> eth2
> Jun 11 10:03:22 firewall dhcpd: DHCPOFFER on 192.168.100.19 to
> 08:00:27:7e:27:fe via eth2
> Jun 11 10:03:25 firewall dhcpd: DHCPREQUEST for 192.168.100.19
> (192.168.100.1) from 08:00:27:7e:27:fe via eth2
> Jun 11 10:03:25 firewall dhcpd: DHCPACK on 192.168.100.19 to
> 08:00:27:7e:27:fe via eth2
> Jun 11 10:03:25 firewall in.tftpd[2965]: RRQ from 192.168.100.19 filename
> Solaris-5.10-hw0811-pxegrub
> Jun 11 10:03:29 firewall in.tftpd[2967]: RRQ from 192.168.100.19 filename
> menu.lst.010800277E27FE
> Jun 11 10:03:29 firewall in.tftpd[2968]: RRQ from 192.168.100.19 filename
> menu.lst.010800277E27FE
> Jun 11 10:03:29 firewall in.tftpd[2969]: RRQ from 192.168.100.19 filename
> menu.lst.010800277E27FE
> Jun 11 10:03:29 firewall in.tftpd[2970]: RRQ from 192.168.100.19 filename
> menu.lst.010800277E27FE
> Jun 11 10:03:30 firewall in.tftpd[2973]: RRQ from 192.168.100.19 filename
> boot/Solaris-5.10-hw0811-multiboot
> Jun 11 10:03:30 firewall in.tftpd[2974]: RRQ from 192.168.100.19 filename
> boot/Solaris-5.10-hw0811-multiboot
> Jun 11 10:03:30 firewall in.tftpd[2975]: RRQ from 192.168.100.19 filename
> boot/Solaris-5.10-hw0811-multiboot
> Jun 11 10:03:30 firewall in.tftpd[2976]: RRQ from 192.168.100.19 filename
> boot/Solaris-5.10-hw0811-x86.miniroot
> Jun 11 10:03:49 firewall in.tftpd[2984]: RRQ from 192.168.100.19 filename
> boot/Solaris-5.10-hw0811-x86.miniroot
> Jun 11 10:04:22 firewall dhcpd: DHCPREQUEST for 192.168.100.19 from
> 08:00:27:7e:27:fe via eth2
> Jun 11 10:04:22 firewall dhcpd: DHCPACK on 192.168.100.19 to
> 08:00:27:7e:27:fe via eth2
>
> ==> /var/log/foreman-proxy/proxy.log <==
> D, [2013-06-11T10:04:48.270726 #1984] DEBUG – : Found puppetca at
> /usr/bin/puppet
> D, [2013-06-11T10:04:48.271333 #1984] DEBUG – : Found sudo at
> /usr/bin/sudo
> D, [2013-06-11T10:04:48.271547 #1984] DEBUG – : Executing /usr/bin/sudo
> -S /usr/bin/puppet cert --clean solaris1.int.localnet
> I, [2013-06-11T10:04:50.005855 #1984] INFO – : Attempt to remove
> nonexistant client certificate for solaris1.int.localnet
> E, [2013-06-11T10:04:50.006451 #1984] ERROR – : Attempt to remove
> nonexistant client certificate for solaris1.int.localnet
> I, [2013-06-11T10:04:50.130226 #1984] INFO – : Added
> solaris1.int.localnet to autosign
>
> ==> /var/log/foreman/production.log <==
>
> Started GET "/unattended/provision" for 192.168.100.19 at Tue Jun 11
> 10:04:48 -0400 2013
> Processing by UnattendedController#provision as
> Found solaris1.int.localnet
> Remove puppet certificate for solaris1.int.localnet
> Adding autosign entry for solaris1.int.localnet
> Rendered inline template (19.2ms)
> Rendered text template (0.0ms)
> Completed 500 Internal Server Error in 2163ms (Views: 0.9ms |
> ActiveRecord: 0.0ms)
>
> ==> /var/log/httpd/access_log <==
> 192.168.100.19 - - [11/Jun/2013:10:04:48 -0400] "GET /unattended/provision
> HTTP/1.1" 500 111 "-" "curl/7.19.6 (i386-pc-solaris2.10) libcurl/7.19.6
> OpenSSL/0.9.7g"
>
> ==> /var/log/foreman/production.log <==
>
> Started GET "/unattended/provision?spoof=192.168.100.19" for
> 192.168.100.100 at Tue Jun 11 10:05:22 -0400 2013
> Processing by UnattendedController#provision as HTML
>
> Parameters: {"spoof"=>"192.168.100.19"}
> Found solaris1.int.localnet
> Rendered inline template (19.7ms)
> Rendered text template (0.0ms)
> Completed 500 Internal Server Error in 68ms (Views: 1.6ms | ActiveRecord:
> 0.0ms)
>
> ==> /var/log/httpd/access_log <==
> 192.168.100.100 - - [11/Jun/2013:10:05:22 -0400] "GET
> /unattended/provision?spoof=192.168.100.19 HTTP/1.1" 500 111 "
> https://firewall/hosts/solaris1.int.localnet" "Mozilla/5.0 (Windows NT
> 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110
> Safari/537.36"
>
> The browser output from the template view is:
>
>
> There was an error rendering the Jumpstart Default template: undefined
> method 'use_image' for Host::Jail (Host)
>
> This matches what the Solaris Target Host sees in referencing "There"
> being an invalid keyword.
>
> Is it possible to get more detail about this 500 error that appears in the
> /var/log/foreman/production.log file?..am I just looking in the wrong log
> file?
>
> Thanks.
>
>
>>
>> Dominic,
>> Thanks for your thoughts! I appreciate the ideas, I hope this post
>> will provide more relevant information now that I've had a change to
>> investigate some more.
>>
>> > Not quite sure how to get more info about the 500 error.
>>
>> Try previewing the template from the host page, it might be a rendering
>> error that you can reproduce from there.
>>
>> The error I pasted was generated from previewing the host template. When
>> the target system boots it gets passed the PXEGrub loader and pulls the
>> install kernel from the tftp server. After loading that kernel it ends
>> during Foreman's rendering of the PXEGrub Jumpstart Provisioning Template
>> (as shown in the screen shot attached). This "There" is also the first
>> word presented in the browser when previewing the template from the Host.
>> Foreman responds to the browser with:
>>
>> There was an error rendering the Jumpstart Default template: undefined
>> method 'use_image' for Host::Jail (Host)
>>
>
Hmm… can you try disabling safe mode rendering and see if that solves the
issue? it might that use_image is simply not on the whitelist.

Ohad

···

On Tue, Jun 11, 2013 at 5:11 PM, Sean Alderman wrote: > On Monday, June 3, 2013 1:05:32 PM UTC-4, Sean Alderman wrote:

Install Media Path.

Perhaps just provide the media over HTTP, then if you create a Solaris
OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

I’m not as interested in this issue since I’ve worked around it by
manually copying the boot files into /var/lib/tftpboot. I just wanted to
bring it into the light.

Using NFS is clearly an option for the Media URL, the helps in the
GUI suggest how to accomplish it. Is this a possible Smart Proxy Bug?

Following the Solaris Unattended Install Wiki to the letter and
setting the media path to the HTTP URL, where “server” is my Foreman
server, produces a 404 with 0 byte tftp kernel files. So I tried NFS and
found that wget doesn’t like NFS URI’s.

Thanks for your help!

Kind regards,

Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton

On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal dcleal@redhat.com wrote:

On 31/05/13 21:52, Sean Alderman wrote:

Were you able to get this resolved?

I’m having similar behaviour in my lab, I just started playing with
Solaris today.

The /var/log/foreman/production.**log file shows:
Started GET “/unattended/PXEGrub?spoof=**192.168.100.19” for
192.168.100.100 at Fri May 31 16:26:55 -0400 2013
Processing by UnattendedController#PXEGrub as HTML
Parameters: {“spoof”=>“192.168.100.19”}
Found solaris1.int.localnet
Rendered inline template (45.3ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 107ms (Views: 1.1ms |
ActiveRecord: 0.0ms)

Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a rendering
error that you can reproduce from there.

I also had issues with using NFS as the media source. I have logs from
the Smart-Proxy about failing to copy the multiboot and miniroot files
over to the tfptroot because wget doesn’t like nfs:/// as
Install Media Path.

Perhaps just provide the media over HTTP, then if you create a Solaris
OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-users+unsubscribe@googlegroups.com foreman-users%2Bunsubscribe@googlegroups.com
.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/**group/foreman-users?hl=en http://groups.google.com/group/foreman-users?hl=en
.
For more options, visit https://groups.google.com/**groups/opt_out https://groups.google.com/groups/opt_out
.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Sean_Alderman · June 11, 2013, 8:58pm

Ohad, wonderful! I had no idea about this setting. I'm onto the next error

literally. It appears to be an install media issue, but that will have
to wait for tomorrow.

Thanks!

···

On Tuesday, June 11, 2013 2:30:09 PM UTC-4, ohad wrote: > > > > On Tue, Jun 11, 2013 at 5:11 PM, Sean Alderman <salde...@udayton.edu > > wrote: > >> Circling back on this one... I still can't seem to get a Solaris build >> happening. >> >> Pasted here are the outputs from logs on my >> Foreman/DHCP/TFTP/DNS/PuppetMaster server named firewall from powering the >> Solaris Target Host on through its failure noted by the image posted in the >> previous message, to an attempt to preview the template via the Foreman UI >> : >> ==> /var/log/messages <== >> Jun 11 10:03:22 firewall dhcpd: DHCPDISCOVER from 08:00:27:7e:27:fe via >> eth2 >> Jun 11 10:03:22 firewall dhcpd: DHCPOFFER on 192.168.100.19 to >> 08:00:27:7e:27:fe via eth2 >> Jun 11 10:03:25 firewall dhcpd: DHCPREQUEST for 192.168.100.19 >> (192.168.100.1) from 08:00:27:7e:27:fe via eth2 >> Jun 11 10:03:25 firewall dhcpd: DHCPACK on 192.168.100.19 to >> 08:00:27:7e:27:fe via eth2 >> Jun 11 10:03:25 firewall in.tftpd[2965]: RRQ from 192.168.100.19 filename >> Solaris-5.10-hw0811-pxegrub >> Jun 11 10:03:29 firewall in.tftpd[2967]: RRQ from 192.168.100.19 filename >> menu.lst.010800277E27FE >> Jun 11 10:03:29 firewall in.tftpd[2968]: RRQ from 192.168.100.19 filename >> menu.lst.010800277E27FE >> Jun 11 10:03:29 firewall in.tftpd[2969]: RRQ from 192.168.100.19 filename >> menu.lst.010800277E27FE >> Jun 11 10:03:29 firewall in.tftpd[2970]: RRQ from 192.168.100.19 filename >> menu.lst.010800277E27FE >> Jun 11 10:03:30 firewall in.tftpd[2973]: RRQ from 192.168.100.19 filename >> boot/Solaris-5.10-hw0811-multiboot >> Jun 11 10:03:30 firewall in.tftpd[2974]: RRQ from 192.168.100.19 filename >> boot/Solaris-5.10-hw0811-multiboot >> Jun 11 10:03:30 firewall in.tftpd[2975]: RRQ from 192.168.100.19 filename >> boot/Solaris-5.10-hw0811-multiboot >> Jun 11 10:03:30 firewall in.tftpd[2976]: RRQ from 192.168.100.19 filename >> boot/Solaris-5.10-hw0811-x86.miniroot >> Jun 11 10:03:49 firewall in.tftpd[2984]: RRQ from 192.168.100.19 filename >> boot/Solaris-5.10-hw0811-x86.miniroot >> Jun 11 10:04:22 firewall dhcpd: DHCPREQUEST for 192.168.100.19 from >> 08:00:27:7e:27:fe via eth2 >> Jun 11 10:04:22 firewall dhcpd: DHCPACK on 192.168.100.19 to >> 08:00:27:7e:27:fe via eth2 >> >> ==> /var/log/foreman-proxy/proxy.log <== >> D, [2013-06-11T10:04:48.270726 #1984] DEBUG -- : Found puppetca at >> /usr/bin/puppet >> D, [2013-06-11T10:04:48.271333 #1984] DEBUG -- : Found sudo at >> /usr/bin/sudo >> D, [2013-06-11T10:04:48.271547 #1984] DEBUG -- : Executing /usr/bin/sudo >> -S /usr/bin/puppet cert --clean solaris1.int.localnet >> I, [2013-06-11T10:04:50.005855 #1984] INFO -- : Attempt to remove >> nonexistant client certificate for solaris1.int.localnet >> E, [2013-06-11T10:04:50.006451 #1984] ERROR -- : Attempt to remove >> nonexistant client certificate for solaris1.int.localnet >> I, [2013-06-11T10:04:50.130226 #1984] INFO -- : Added >> solaris1.int.localnet to autosign >> >> ==> /var/log/foreman/production.log <== >> >> Started GET "/unattended/provision" for 192.168.100.19 at Tue Jun 11 >> 10:04:48 -0400 2013 >> Processing by UnattendedController#provision as >> Found solaris1.int.localnet >> Remove puppet certificate for solaris1.int.localnet >> Adding autosign entry for solaris1.int.localnet >> Rendered inline template (19.2ms) >> Rendered text template (0.0ms) >> Completed 500 Internal Server Error in 2163ms (Views: 0.9ms | >> ActiveRecord: 0.0ms) >> >> ==> /var/log/httpd/access_log <== >> 192.168.100.19 - - [11/Jun/2013:10:04:48 -0400] "GET >> /unattended/provision HTTP/1.1" 500 111 "-" "curl/7.19.6 >> (i386-pc-solaris2.10) libcurl/7.19.6 OpenSSL/0.9.7g" >> >> ==> /var/log/foreman/production.log <== >> >> Started GET "/unattended/provision?spoof=192.168.100.19" for >> 192.168.100.100 at Tue Jun 11 10:05:22 -0400 2013 >> Processing by UnattendedController#provision as HTML >> >> Parameters: {"spoof"=>"192.168.100.19"} >> Found solaris1.int.localnet >> Rendered inline template (19.7ms) >> Rendered text template (0.0ms) >> Completed 500 Internal Server Error in 68ms (Views: 1.6ms | ActiveRecord: >> 0.0ms) >> >> ==> /var/log/httpd/access_log <== >> 192.168.100.100 - - [11/Jun/2013:10:05:22 -0400] "GET >> /unattended/provision?spoof=192.168.100.19 HTTP/1.1" 500 111 " >> https://firewall/hosts/solaris1.int.localnet" "Mozilla/5.0 (Windows NT >> 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 >> Safari/537.36" >> >> The browser output from the template view is: >> >> >> There was an error rendering the Jumpstart Default template: undefined >> method 'use_image' for Host::Jail (Host) >> >> This matches what the Solaris Target Host sees in referencing "There" >> being an invalid keyword. >> >> Is it possible to get more detail about this 500 error that appears in >> the /var/log/foreman/production.log file?...am I just looking in the wrong >> log file? >> >> Thanks. >> >> >> On Monday, June 3, 2013 1:05:32 PM UTC-4, Sean Alderman wrote: >>> >>> Dominic, >>> Thanks for your thoughts! I appreciate the ideas, I hope this post >>> will provide more relevant information now that I've had a change to >>> investigate some more. >>> >>> > Not quite sure how to get more info about the 500 error. >>> >>> Try previewing the template from the host page, it might be a rendering >>> error that you can reproduce from there. >>> >>> The error I pasted was generated from previewing the host template. >>> When the target system boots it gets passed the PXEGrub loader and pulls >>> the install kernel from the tftp server. After loading that kernel it ends >>> during Foreman's rendering of the PXEGrub Jumpstart Provisioning Template >>> (as shown in the screen shot attached). This "There" is also the first >>> word presented in the browser when previewing the template from the Host. >>> Foreman responds to the browser with: >>> >>> There was an error rendering the Jumpstart Default template: undefined >>> method 'use_image' for Host::Jail (Host) >>> >> > Hmm... can you try disabling safe mode rendering and see if that solves > the issue? it might that use_image is simply not on the whitelist. > > Ohad > >> >>> > Install Media Path. >>> >>> Perhaps just provide the media over HTTP, then if you create a Solaris >>> OS and associate it with the mirror, I believe you can enter the NFS >>> paths as well. >>> >>> I'm not as interested in this issue since I've worked around it by >>> manually copying the boot files into /var/lib/tftpboot. I just wanted to >>> bring it into the light. >>> >>> 1. Using NFS is clearly an option for the Media URL, the helps in >>> the GUI suggest how to accomplish it. Is this a possible Smart Proxy Bug? >>> 2. Following the Solaris Unattended Install Wiki to the letter and >>> setting the media path to the HTTP URL, where "server" is my Foreman >>> server, produces a 404 with 0 byte tftp kernel files. So I tried NFS and >>> found that wget doesn't like NFS URI's. >>> >>> Thanks for your help! >>> >>> Kind regards, >>> -- >>> Sean M. Alderman >>> Senior Engineer, UDit Systems Integration and Engineering >>> University of Dayton >>> >>> >>> On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal <dcl...@redhat.com >>> > wrote: >>> >>>> On 31/05/13 21:52, Sean Alderman wrote: >>>> > Were you able to get this resolved? >>>> > >>>> > I'm having similar behaviour in my lab, I just started playing with >>>> > Solaris today. >>>> > >>>> > The /var/log/foreman/production.**log file shows: >>>> > Started GET "/unattended/PXEGrub?spoof=**192.168.100.19" for >>>> > 192.168.100.100 at Fri May 31 16:26:55 -0400 2013 >>>> > Processing by UnattendedController#PXEGrub as HTML >>>> > Parameters: {"spoof"=>"192.168.100.19"} >>>> > Found solaris1.int.localnet >>>> > Rendered inline template (45.3ms) >>>> > Rendered text template (0.0ms) >>>> > Completed 500 Internal Server Error in 107ms (Views: 1.1ms | >>>> > ActiveRecord: 0.0ms) >>>> > >>>> > Not quite sure how to get more info about the 500 error. >>>> >>>> Try previewing the template from the host page, it might be a rendering >>>> error that you can reproduce from there. >>>> >>>> > I also had issues with using NFS as the media source. I have logs >>>> from >>>> > the Smart-Proxy about failing to copy the multiboot and miniroot files >>>> > over to the tfptroot because wget doesn't like nfs:/// >>>> as >>>> > Install Media Path. >>>> >>>> Perhaps just provide the media over HTTP, then if you create a Solaris >>>> OS and associate it with the mirror, I believe you can enter the NFS >>>> paths as well. >>>> >>>> -- >>>> Dominic Cleal >>>> Red Hat Engineering >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Foreman users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to foreman-user...@**googlegroups.com . >>>> To post to this group, send email to forema...@googlegroups.com >>>> **. >>>> Visit this group at http://groups.google.com/** >>>> group/foreman-users?hl=en >>>> . >>>> For more options, visit https://groups.google.com/**groups/opt_out >>>> . >>>> >>>> >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

lzap · June 12, 2013, 11:09am

Oh the tread got stuck in my MUA for some reason, ignore my previous
mail

Glad you got it rolling.

LZ

···

On Tue, Jun 11, 2013 at 01:58:31PM -0700, Sean Alderman wrote: > Ohad, wonderful! I had no idea about this setting. I'm onto the next error > - literally. It appears to be an install media issue, but that will have > to wait for tomorrow. > > Thanks! > > On Tuesday, June 11, 2013 2:30:09 PM UTC-4, ohad wrote: > > > > > > > > On Tue, Jun 11, 2013 at 5:11 PM, Sean Alderman <salde...@udayton.edu > > > wrote: > > > >> Circling back on this one... I still can't seem to get a Solaris build > >> happening. > >> > >> Pasted here are the outputs from logs on my > >> Foreman/DHCP/TFTP/DNS/PuppetMaster server named firewall from powering the > >> Solaris Target Host on through its failure noted by the image posted in the > >> previous message, to an attempt to preview the template via the Foreman UI > >> : > >> ==> /var/log/messages <== > >> Jun 11 10:03:22 firewall dhcpd: DHCPDISCOVER from 08:00:27:7e:27:fe via > >> eth2 > >> Jun 11 10:03:22 firewall dhcpd: DHCPOFFER on 192.168.100.19 to > >> 08:00:27:7e:27:fe via eth2 > >> Jun 11 10:03:25 firewall dhcpd: DHCPREQUEST for 192.168.100.19 > >> (192.168.100.1) from 08:00:27:7e:27:fe via eth2 > >> Jun 11 10:03:25 firewall dhcpd: DHCPACK on 192.168.100.19 to > >> 08:00:27:7e:27:fe via eth2 > >> Jun 11 10:03:25 firewall in.tftpd[2965]: RRQ from 192.168.100.19 filename > >> Solaris-5.10-hw0811-pxegrub > >> Jun 11 10:03:29 firewall in.tftpd[2967]: RRQ from 192.168.100.19 filename > >> menu.lst.010800277E27FE > >> Jun 11 10:03:29 firewall in.tftpd[2968]: RRQ from 192.168.100.19 filename > >> menu.lst.010800277E27FE > >> Jun 11 10:03:29 firewall in.tftpd[2969]: RRQ from 192.168.100.19 filename > >> menu.lst.010800277E27FE > >> Jun 11 10:03:29 firewall in.tftpd[2970]: RRQ from 192.168.100.19 filename > >> menu.lst.010800277E27FE > >> Jun 11 10:03:30 firewall in.tftpd[2973]: RRQ from 192.168.100.19 filename > >> boot/Solaris-5.10-hw0811-multiboot > >> Jun 11 10:03:30 firewall in.tftpd[2974]: RRQ from 192.168.100.19 filename > >> boot/Solaris-5.10-hw0811-multiboot > >> Jun 11 10:03:30 firewall in.tftpd[2975]: RRQ from 192.168.100.19 filename > >> boot/Solaris-5.10-hw0811-multiboot > >> Jun 11 10:03:30 firewall in.tftpd[2976]: RRQ from 192.168.100.19 filename > >> boot/Solaris-5.10-hw0811-x86.miniroot > >> Jun 11 10:03:49 firewall in.tftpd[2984]: RRQ from 192.168.100.19 filename > >> boot/Solaris-5.10-hw0811-x86.miniroot > >> Jun 11 10:04:22 firewall dhcpd: DHCPREQUEST for 192.168.100.19 from > >> 08:00:27:7e:27:fe via eth2 > >> Jun 11 10:04:22 firewall dhcpd: DHCPACK on 192.168.100.19 to > >> 08:00:27:7e:27:fe via eth2 > >> > >> ==> /var/log/foreman-proxy/proxy.log <== > >> D, [2013-06-11T10:04:48.270726 #1984] DEBUG -- : Found puppetca at > >> /usr/bin/puppet > >> D, [2013-06-11T10:04:48.271333 #1984] DEBUG -- : Found sudo at > >> /usr/bin/sudo > >> D, [2013-06-11T10:04:48.271547 #1984] DEBUG -- : Executing /usr/bin/sudo > >> -S /usr/bin/puppet cert --clean solaris1.int.localnet > >> I, [2013-06-11T10:04:50.005855 #1984] INFO -- : Attempt to remove > >> nonexistant client certificate for solaris1.int.localnet > >> E, [2013-06-11T10:04:50.006451 #1984] ERROR -- : Attempt to remove > >> nonexistant client certificate for solaris1.int.localnet > >> I, [2013-06-11T10:04:50.130226 #1984] INFO -- : Added > >> solaris1.int.localnet to autosign > >> > >> ==> /var/log/foreman/production.log <== > >> > >> Started GET "/unattended/provision" for 192.168.100.19 at Tue Jun 11 > >> 10:04:48 -0400 2013 > >> Processing by UnattendedController#provision as > >> Found solaris1.int.localnet > >> Remove puppet certificate for solaris1.int.localnet > >> Adding autosign entry for solaris1.int.localnet > >> Rendered inline template (19.2ms) > >> Rendered text template (0.0ms) > >> Completed 500 Internal Server Error in 2163ms (Views: 0.9ms | > >> ActiveRecord: 0.0ms) > >> > >> ==> /var/log/httpd/access_log <== > >> 192.168.100.19 - - [11/Jun/2013:10:04:48 -0400] "GET > >> /unattended/provision HTTP/1.1" 500 111 "-" "curl/7.19.6 > >> (i386-pc-solaris2.10) libcurl/7.19.6 OpenSSL/0.9.7g" > >> > >> ==> /var/log/foreman/production.log <== > >> > >> Started GET "/unattended/provision?spoof=192.168.100.19" for > >> 192.168.100.100 at Tue Jun 11 10:05:22 -0400 2013 > >> Processing by UnattendedController#provision as HTML > >> > >> Parameters: {"spoof"=>"192.168.100.19"} > >> Found solaris1.int.localnet > >> Rendered inline template (19.7ms) > >> Rendered text template (0.0ms) > >> Completed 500 Internal Server Error in 68ms (Views: 1.6ms | ActiveRecord: > >> 0.0ms) > >> > >> ==> /var/log/httpd/access_log <== > >> 192.168.100.100 - - [11/Jun/2013:10:05:22 -0400] "GET > >> /unattended/provision?spoof=192.168.100.19 HTTP/1.1" 500 111 " > >> https://firewall/hosts/solaris1.int.localnet" "Mozilla/5.0 (Windows NT > >> 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 > >> Safari/537.36" > >> > >> The browser output from the template view is: > >> > >> > >> There was an error rendering the Jumpstart Default template: undefined > >> method 'use_image' for Host::Jail (Host) > >> > >> This matches what the Solaris Target Host sees in referencing "There" > >> being an invalid keyword. > >> > >> Is it possible to get more detail about this 500 error that appears in > >> the /var/log/foreman/production.log file?...am I just looking in the wrong > >> log file? > >> > >> Thanks. > >> > >> > >> On Monday, June 3, 2013 1:05:32 PM UTC-4, Sean Alderman wrote: > >>> > >>> Dominic, > >>> Thanks for your thoughts! I appreciate the ideas, I hope this post > >>> will provide more relevant information now that I've had a change to > >>> investigate some more. > >>> > >>> > Not quite sure how to get more info about the 500 error. > >>> > >>> Try previewing the template from the host page, it might be a rendering > >>> error that you can reproduce from there. > >>> > >>> The error I pasted was generated from previewing the host template. > >>> When the target system boots it gets passed the PXEGrub loader and pulls > >>> the install kernel from the tftp server. After loading that kernel it ends > >>> during Foreman's rendering of the PXEGrub Jumpstart Provisioning Template > >>> (as shown in the screen shot attached). This "There" is also the first > >>> word presented in the browser when previewing the template from the Host. > >>> Foreman responds to the browser with: > >>> > >>> There was an error rendering the Jumpstart Default template: undefined > >>> method 'use_image' for Host::Jail (Host) > >>> > >> > > Hmm... can you try disabling safe mode rendering and see if that solves > > the issue? it might that use_image is simply not on the whitelist. > > > > Ohad > > > >> > >>> > Install Media Path. > >>> > >>> Perhaps just provide the media over HTTP, then if you create a Solaris > >>> OS and associate it with the mirror, I believe you can enter the NFS > >>> paths as well. > >>> > >>> I'm not as interested in this issue since I've worked around it by > >>> manually copying the boot files into /var/lib/tftpboot. I just wanted to > >>> bring it into the light. > >>> > >>> 1. Using NFS is clearly an option for the Media URL, the helps in > >>> the GUI suggest how to accomplish it. Is this a possible Smart Proxy Bug? > >>> 2. Following the Solaris Unattended Install Wiki to the letter and > >>> setting the media path to the HTTP URL, where "server" is my Foreman > >>> server, produces a 404 with 0 byte tftp kernel files. So I tried NFS and > >>> found that wget doesn't like NFS URI's. > >>> > >>> Thanks for your help! > >>> > >>> Kind regards, > >>> -- > >>> Sean M. Alderman > >>> Senior Engineer, UDit Systems Integration and Engineering > >>> University of Dayton > >>> > >>> > >>> On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal <dcl...@redhat.com > >>> > wrote: > >>> > >>>> On 31/05/13 21:52, Sean Alderman wrote: > >>>> > Were you able to get this resolved? > >>>> > > >>>> > I'm having similar behaviour in my lab, I just started playing with > >>>> > Solaris today. > >>>> > > >>>> > The /var/log/foreman/production.**log file shows: > >>>> > Started GET "/unattended/PXEGrub?spoof=**192.168.100.19" for > >>>> > 192.168.100.100 at Fri May 31 16:26:55 -0400 2013 > >>>> > Processing by UnattendedController#PXEGrub as HTML > >>>> > Parameters: {"spoof"=>"192.168.100.19"} > >>>> > Found solaris1.int.localnet > >>>> > Rendered inline template (45.3ms) > >>>> > Rendered text template (0.0ms) > >>>> > Completed 500 Internal Server Error in 107ms (Views: 1.1ms | > >>>> > ActiveRecord: 0.0ms) > >>>> > > >>>> > Not quite sure how to get more info about the 500 error. > >>>> > >>>> Try previewing the template from the host page, it might be a rendering > >>>> error that you can reproduce from there. > >>>> > >>>> > I also had issues with using NFS as the media source. I have logs > >>>> from > >>>> > the Smart-Proxy about failing to copy the multiboot and miniroot files > >>>> > over to the tfptroot because wget doesn't like nfs:/// > >>>> as > >>>> > Install Media Path. > >>>> > >>>> Perhaps just provide the media over HTTP, then if you create a Solaris > >>>> OS and associate it with the mirror, I believe you can enter the NFS > >>>> paths as well. > >>>> > >>>> -- > >>>> Dominic Cleal > >>>> Red Hat Engineering > >>>> > >>>> -- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "Foreman users" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to foreman-user...@**googlegroups.com . > >>>> To post to this group, send email to forema...@googlegroups.com > >>>> **. > >>>> Visit this group at http://groups.google.com/** > >>>> group/foreman-users?hl=en > >>>> . > >>>> For more options, visit https://groups.google.com/**groups/opt_out > >>>> . > >>>> > >>>> > >>>> > >>> -- > >> You received this message because you are subscribed to the Google Groups > >> "Foreman users" group. > >> To unsubscribe from this group and stop receiving emails from it, send an > >> email to foreman-user...@googlegroups.com . > >> To post to this group, send email to forema...@googlegroups.com > >> . > >> Visit this group at http://groups.google.com/group/foreman-users?hl=en. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > >> > > > > > > -- > You received this message because you are subscribed to the Google Groups "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at http://groups.google.com/group/foreman-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > >

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

Sean_Alderman · June 12, 2013, 8:22pm

So, the error I finished the day with yesterday is a NFS related error I
thought I might explain here as it might be desireable to add it to the
Unattended Solaris Install Wiki.

I have built the Solaris installation media and such on my CentOS 6
server. This seems like something the wiki instructions are going after,
not just loading up a Solaris server mounting the media and running the
jump start scripts to prepare the way. Regardless I picked up a good hint
from http://hintshop.ludvig.co.nz/show/solaris-jumpstart-linux-server. The
exported Filesystems need to have the crossmnt option specified if they
overlap. With out this option set in /etc/exports, the build target would
drop out to a prompt like so:

Executing begin script "install_begin"…
Begin script install_begin execution completed.

ERROR: Could not load the media (/cdrom)

···

#

This is apparently to do with NFSv4 and nested mounts. My /etc/exports now
looks like:

[root@firewall ~]# cat /etc/exports
/export/Solaris
*(ro,sync,no_root_squash,crossmnt,no_subtree_check,anonuid=0)
/export/Solaris/jumpstart *(ro,sync,no_root_squash,crossmnt,anonuid=0)

…and all is well.

Thanks for your help!

On Wednesday, June 12, 2013 7:09:33 AM UTC-4, Lukas Zapletal wrote:

Oh the tread got stuck in my MUA for some reason, ignore my previous
mail

Glad you got it rolling.

LZ

On Tue, Jun 11, 2013 at 01:58:31PM -0700, Sean Alderman wrote:

Ohad, wonderful! I had no idea about this setting. I’m onto the next
error

literally. It appears to be an install media issue, but that will
have
to wait for tomorrow.

Thanks!

On Tuesday, June 11, 2013 2:30:09 PM UTC-4, ohad wrote:

On Tue, Jun 11, 2013 at 5:11 PM, Sean Alderman <salde...@udayton.edu<javascript:> > > > > > wrote:

Circling back on this one… I still can’t seem to get a Solaris
build

happening.

Pasted here are the outputs from logs on my
Foreman/DHCP/TFTP/DNS/PuppetMaster server named firewall from
powering the

Solaris Target Host on through its failure noted by the image posted
in the

previous message, to an attempt to preview the template via the
Foreman UI

:
==> /var/log/messages <==
Jun 11 10:03:22 firewall dhcpd: DHCPDISCOVER from 08:00:27:7e:27:fe
via

eth2
Jun 11 10:03:22 firewall dhcpd: DHCPOFFER on 192.168.100.19 to
08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall dhcpd: DHCPREQUEST for 192.168.100.19
(192.168.100.1) from 08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall dhcpd: DHCPACK on 192.168.100.19 to
08:00:27:7e:27:fe via eth2
Jun 11 10:03:25 firewall in.tftpd[2965]: RRQ from 192.168.100.19
filename

Solaris-5.10-hw0811-pxegrub
Jun 11 10:03:29 firewall in.tftpd[2967]: RRQ from 192.168.100.19
filename

menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2968]: RRQ from 192.168.100.19
filename

menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2969]: RRQ from 192.168.100.19
filename

menu.lst.010800277E27FE
Jun 11 10:03:29 firewall in.tftpd[2970]: RRQ from 192.168.100.19
filename

menu.lst.010800277E27FE
Jun 11 10:03:30 firewall in.tftpd[2973]: RRQ from 192.168.100.19
filename

boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2974]: RRQ from 192.168.100.19
filename

boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2975]: RRQ from 192.168.100.19
filename

boot/Solaris-5.10-hw0811-multiboot
Jun 11 10:03:30 firewall in.tftpd[2976]: RRQ from 192.168.100.19
filename

boot/Solaris-5.10-hw0811-x86.miniroot
Jun 11 10:03:49 firewall in.tftpd[2984]: RRQ from 192.168.100.19
filename

boot/Solaris-5.10-hw0811-x86.miniroot
Jun 11 10:04:22 firewall dhcpd: DHCPREQUEST for 192.168.100.19 from
08:00:27:7e:27:fe via eth2
Jun 11 10:04:22 firewall dhcpd: DHCPACK on 192.168.100.19 to
08:00:27:7e:27:fe via eth2

==> /var/log/foreman-proxy/proxy.log <==
D, [2013-06-11T10:04:48.270726 #1984] DEBUG – : Found puppetca at
/usr/bin/puppet
D, [2013-06-11T10:04:48.271333 #1984] DEBUG – : Found sudo at
/usr/bin/sudo
D, [2013-06-11T10:04:48.271547 #1984] DEBUG – : Executing
/usr/bin/sudo

-S /usr/bin/puppet cert --clean solaris1.int.localnet
I, [2013-06-11T10:04:50.005855 #1984] INFO – : Attempt to remove
nonexistant client certificate for solaris1.int.localnet
E, [2013-06-11T10:04:50.006451 #1984] ERROR – : Attempt to remove
nonexistant client certificate for solaris1.int.localnet
I, [2013-06-11T10:04:50.130226 #1984] INFO – : Added
solaris1.int.localnet to autosign

==> /var/log/foreman/production.log <==

Started GET “/unattended/provision” for 192.168.100.19 at Tue Jun 11
10:04:48 -0400 2013
Processing by UnattendedController#provision as
Found solaris1.int.localnet
Remove puppet certificate for solaris1.int.localnet
Adding autosign entry for solaris1.int.localnet
Rendered inline template (19.2ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 2163ms (Views: 0.9ms |
ActiveRecord: 0.0ms)

==> /var/log/httpd/access_log <==
192.168.100.19 - - [11/Jun/2013:10:04:48 -0400] “GET
/unattended/provision HTTP/1.1” 500 111 “-” “curl/7.19.6
(i386-pc-solaris2.10) libcurl/7.19.6 OpenSSL/0.9.7g”

==> /var/log/foreman/production.log <==

Started GET “/unattended/provision?spoof=192.168.100.19” for
192.168.100.100 at Tue Jun 11 10:05:22 -0400 2013
Processing by UnattendedController#provision as HTML

Parameters: {“spoof”=>“192.168.100.19”}
Found solaris1.int.localnet
Rendered inline template (19.7ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 68ms (Views: 1.6ms |
ActiveRecord:

0.0ms)

==> /var/log/httpd/access_log <==
192.168.100.100 - - [11/Jun/2013:10:05:22 -0400] “GET
/unattended/provision?spoof=192.168.100.19 HTTP/1.1” 500 111 “
https://firewall/hosts/solaris1.int.localnet” "Mozilla/5.0 (Windows
NT

6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/27.0.1453.110

Safari/537.36"

The browser output from the template view is:

There was an error rendering the Jumpstart Default template:
undefined

method ‘use_image’ for Host::Jail (Host)

This matches what the Solaris Target Host sees in referencing "There"
being an invalid keyword.

Is it possible to get more detail about this 500 error that appears
in

the /var/log/foreman/production.log file?..am I just looking in the
wrong

log file?

Thanks.

On Monday, June 3, 2013 1:05:32 PM UTC-4, Sean Alderman wrote:

Dominic,
Thanks for your thoughts! I appreciate the ideas, I hope this
post

will provide more relevant information now that I’ve had a change to
investigate some more.

Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a
rendering

error that you can reproduce from there.

The error I pasted was generated from previewing the host template.

When the target system boots it gets passed the PXEGrub loader and
pulls

the install kernel from the tftp server. After loading that kernel
it ends

during Foreman’s rendering of the PXEGrub Jumpstart Provisioning
Template

(as shown in the screen shot attached). This “There” is also the
first

word presented in the browser when previewing the template from the
Host.

Foreman responds to the browser with:

There was an error rendering the Jumpstart Default template:
undefined

method ‘use_image’ for Host::Jail (Host)

Hmm… can you try disabling safe mode rendering and see if that
solves

the issue? it might that use_image is simply not on the whitelist.

Ohad

Install Media Path.

Perhaps just provide the media over HTTP, then if you create a
Solaris

OS and associate it with the mirror, I believe you can enter the NFS
paths as well.

I’m not as interested in this issue since I’ve worked around it by
manually copying the boot files into /var/lib/tftpboot. I just
wanted to

bring it into the light.

Using NFS is clearly an option for the Media URL, the helps in
the GUI suggest how to accomplish it. Is this a possible Smart
Proxy Bug?

Following the Solaris Unattended Install Wiki to the letter
and

setting the media path to the HTTP URL, where “server” is my
Foreman

server, produces a 404 with 0 byte tftp kernel files. So I tried
NFS and

found that wget doesn’t like NFS URI’s.

Thanks for your help!

Kind regards,

Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton

On Sat, Jun 1, 2013 at 7:11 AM, Dominic Cleal <dcl...@redhat.com<javascript:> > > > >>> > wrote:

On 31/05/13 21:52, Sean Alderman wrote:

Were you able to get this resolved?

I’m having similar behaviour in my lab, I just started playing
with

Solaris today.

The /var/log/foreman/production.**log file shows:
Started GET “/unattended/PXEGrub?spoof=**192.168.100.19” for
192.168.100.100 at Fri May 31 16:26:55 -0400 2013
Processing by UnattendedController#PXEGrub as HTML
Parameters: {“spoof”=>“192.168.100.19”}
Found solaris1.int.localnet
Rendered inline template (45.3ms)
Rendered text template (0.0ms)
Completed 500 Internal Server Error in 107ms (Views: 1.1ms |
ActiveRecord: 0.0ms)

Not quite sure how to get more info about the 500 error.

Try previewing the template from the host page, it might be a
rendering

error that you can reproduce from there.

I also had issues with using NFS as the media source. I have
logs

from

the Smart-Proxy about failing to copy the multiboot and miniroot
files

over to the tfptroot because wget doesn’t like
nfs:///

as

Install Media Path.

Perhaps just provide the media over HTTP, then if you create a
Solaris

OS and associate it with the mirror, I believe you can enter the
NFS

paths as well.

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send

an email to foreman-user…@**googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>

.
Visit this group at http://groups.google.com/
group/foreman-users?hl=en<
http://groups.google.com/group/foreman-users?hl=en>

.
For more options, visit https://groups.google.com/**groups/opt_out<
https://groups.google.com/groups/opt_out>

.

–
You received this message because you are subscribed to the Google
Groups

“Foreman users” group.
To unsubscribe from this group and stop receiving emails from it,
send an

email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>

.
Visit this group at
http://groups.google.com/group/foreman-users?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.

–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-user...@googlegroups.com <javascript:>.
To post to this group, send email to forema...@googlegroups.com<javascript:>.

Visit this group at http://groups.google.com/group/foreman-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman