We have some temporary solution (and bugreport): https://bugzilla.redhat.com/show_bug.cgi?id=1443690
Op woensdag 19 april 2017 13:23:43 UTC+2 schreef Lukas Zapletal: > > Oh I see, you need to replace everything in > /var/lib/tftpboot/pxelinux.cfg/01-MAC_ADDRESS files. > > Foreman do not have an option to redeploy templates I believe, that > would be useful feature. > > LZ > > On Wed, Apr 19, 2017 at 10:56 AM, Matt <[email protected] <javascript:>> > wrote: > > It could be, but I'm not able to find where to set it. I have checked > all > > templates, maybe you can point me into the right direction. > > > > As this is a temporary fix I think we need to know exactly why this > happens > > and what the best fix is in the future. My old VM's don't have this > > chainloader and use the same PXE loader. > > > > Op woensdag 19 april 2017 10:45:40 UTC+2 schreef Lukas Zapletal: > >> > >> You just said that the alternative loading works, that's the fix I > >> believe. Set it as the default loader for all systems. > >> > >> LZ > >> > >> On Tue, Apr 18, 2017 at 10:18 PM, Matt <[email protected]> wrote: > >> > Hi Lukas, > >> > > >> > Yes happened on new provisioned VM's on oVirt 4.1 lately, this with > >> > Ubuntu, > >> > CentOS and so on are fine. > >> > > >> > Is there a temporary fix while we try to figure it out what the best > way > >> > is > >> > ? > >> > > >> > Cheers, > >> > > >> > Matt > >> > > >> > > >> > Op dinsdag 18 april 2017 13:44:37 UTC+2 schreef Lukas Zapletal: > >> >> > >> >> Just at once? Not following. > >> >> > >> >> Anyway, some BIOSes have problems chain loading into installed > system > >> >> and alternative method via SYSLINUX module can help, which is > exactly > >> >> what you did. > >> >> > >> >> It started to happen on some oVirt/libvirt KVM BIOSes recently but > we > >> >> haven't reported this upstream. > >> >> > >> >> LZ > >> >> > >> >> On Tue, Apr 18, 2017 at 2:47 AM, Matt <[email protected]> wrote: > >> >> > attachement added. > >> >> > > >> >> > -- > >> >> > 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. > >> >> > >> >> > >> >> > >> >> -- > >> >> 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. > >> > >> > >> > >> -- > >> 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] <javascript:>. > > To post to this group, send email to [email protected] > <javascript:>. > > Visit this group at https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > > > -- > 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.
