Lukas,

As I've mentioned, auto-provisioning works on other servers.  So I took a 
step back and started testing on a server with two interfaces and no IPMI.
What I've discovered is that dependent on the server's interface used for 
provisioning, auto-provisioning will fail or succeed.

Thoughts?

On Thursday, April 13, 2017 at 8:09:23 AM UTC-5, Lukas Zapletal wrote:
>
> Chad, any updates? 
>
> LZ 
>
> On Tue, Apr 11, 2017 at 10:27 AM, Lukas Zapletal <[email protected] 
> <javascript:>> wrote: 
> > TFTP orchestration is not being triggered. It can be only performed 
> > when all of these conditions are met: 
> > 
> > - host is managed 
> > - provision method is "build" and not "image" 
> > - host has operating system set 
> > - host has pxe loader flag present (not set to blank or None) 
> > - host has one provisioning NIC with valid MAC address 
> > - a subnet is associated with the provisioning NIC 
> > - the subnet has TFTP feature turned on 
> > 
> > Visit a host which failed provisioning and do this checklist please. 
> > 
> > LZ 
> > 
> > 
> > On Mon, Apr 10, 2017 at 2:33 PM, Chad Schroeder 
> > <[email protected] <javascript:>> wrote: 
> >> Debug log attached 
> >> 
> >> On Monday, April 10, 2017 at 2:31:43 AM UTC-5, Lukas Zapletal wrote: 
> >>> 
> >>> I can't reproduce, please enable SQL and DEBUG log levels: 
> >>> 
> >>> 
> >>> 
> http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#How-do-I-enable-debugging
>  
> >>> 
> >>> Make sure you enable SQL logging endpoint so all SQL messages are 
> >>> present, this is needed in order to catch the error. Restart foreman. 
> >>> 
> >>> Then autoprovision with foreman-tail command running and pastebin the 
> >>> output. I hope to get an error there. 
> >>> 
> >>> LZ 
> >>> 
> >>> On Fri, Apr 7, 2017 at 3:17 PM, Chad Schroeder 
> >>> <[email protected]> wrote: 
> >>> > Lukas, 
> >>> > 
> >>> > Attached: discovered host facts 
> >>> > 
> >>> > On Friday, April 7, 2017 at 7:45:37 AM UTC-5, Chad Schroeder wrote: 
> >>> >> 
> >>> >> I guess I'm not sure on what you're asking for.  Please describe 
> how I 
> >>> >> can 
> >>> >> extract the information you need. 
> >>> >> 
> >>> >> Verified.  I only have one organization and location.  The domain, 
> >>> >> hostgroup, and discovery rule are assigned to the org and location. 
> >>> >> As I've mentioned, this setup works when auto-provisioning other 
> >>> >> bare-metal hosts. 
> >>> >> 
> >>> >> On Friday, April 7, 2017 at 7:33:12 AM UTC-5, Lukas Zapletal wrote: 
> >>> >>> 
> >>> >>> Oh no this is not the output, this is not facter-compatible JSON, 
> can 
> >>> >>> you get me output of facter from that host? I need verbose copy so 
> I 
> >>> >>> can send it to my instance and discover the very same entry. 
> >>> >>> 
> >>> >>> One idea - can you check organization and location of discovered 
> host 
> >>> >>> and your hostgroup, rule and domain? Is it possible it gets 
> discovered 
> >>> >>> into different organization with domain not belonging into? 
> >>> >>> 
> >>> >>> LZ 
> >>> >>> 
> >>> >>> On Fri, Apr 7, 2017 at 2:22 PM, Chad Schroeder 
> >>> >>> <[email protected]> wrote: 
> >>> >>> > Lukas, 
> >>> >>> > 
> >>> >>> > Yes, the PXEGrbu2 template is associated with the hostgroup and 
> the 
> >>> >>> > discovery rule is triggered.  This has been verified multiple 
> times 
> >>> >>> > and 
> >>> >>> > works on other servers. 
> >>> >>> > Yes, the domain is missing.  On servers that do auto-provision 
> >>> >>> > correctly, 
> >>> >>> > this is always set.  It is not set when trying to auto-provision 
> the 
> >>> >>> > server 
> >>> >>> > I described (4 nics + ipmi). 
> >>> >>> > 
> >>> >>> > JSON-formatted facts attached. 
> >>> >>> > 
> >>> >>> > C 
> >>> >>> 
> >>> >>> 
> >>> >>> 
> >>> >>> -- 
> >>> >>> Later, 
> >>> >>>   Lukas @lzap Zapletal 
> >>> 
> >>> 
> >>> 
> >>> -- 
> >>> Later, 
> >>>   Lukas @lzap Zapletal 
> > 
> > 
> > 
> > -- 
> > Later, 
> >   Lukas @lzap Zapletal 
>
>
>
> -- 
> Later, 
>   Lukas @lzap Zapletal 
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to