[foreman-users] Re: Foreman/Katello 1.14, Roles setting for "Content Source"?

[Mike Wilson]

This is probably the cause but I've been having trouble nailing it 
down...also did not want to have duplicate content views of the same thing 
and couldn't see how to give org/group a content view other than it's own 
(only).

On Thursday, June 29, 2017 at 9:45:04 PM UTC-5, Andrew Schofield wrote:
>
> If you're using locations and orgs then you need view / assign 
> organisations and locations too. You probably want a load of other views - 
> for operating systems etc too. 

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

[foreman-users] Re: Foreman/Katello 1.14, Roles setting for "Content Source"?

[Andrew Schofield]

Also if you trawl the production.log file too you should start to see which 
permissions are missing.

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

[foreman-users] Re: Foreman/Katello 1.14, Roles setting for "Content Source"?

[Andrew Schofield]

If you're using locations and orgs then you need view / assign organisations 
and locations too. You probably want a load of other views - for operating 
systems etc too. 

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

[foreman-users] Re: Vm creation using API fails

[bijith nair]

Hello Guru's,

Could you please look into this?

Rgds/Bijith

On Thursday, 29 June 2017 19:04:37 UTC+5:30, bijith nair wrote:
>
> Hello Team,
>
> When i try to create vm using API's, It fails with below error..
>
> [root@oel6u5 ~]# curl -X POST -s -H "Accept:application/json" -k -u 
> admin:redhat -d "host[name]=mytestdev" -d "host[hostgroup_id]=4" -d 
> "host[compute_resource_id]=1" -d "host[powerup]=1" 
> https://192.168.133.210/api/v1/hosts/ | python -mjson.tool   
>   {
> "host": {
> "errors": {
> "base": [
> "Failed to create a compute Vmware GDC - Devops (VMware) 
> instance mytestdev.testlab.local: Unknown Network ID: \n "
> ]
> },
> "full_messages": [
> "Failed to create a compute Vmware GDC - Devops (VMware) 
> instance mytestdev.testlab.local: Unknown Network ID: \n "
> ],
> "id": null
> }
> }
>
> Though Hammer cli works fine, I see same error while deploying vm via UI 
> but  sumitting the job again fixes it but not happening with API
>
> Rgds/Bijith
>

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

[foreman-users] Re: [foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Eric D Helms]

Thanks for setting this up Greg.

I wanted to send out a few notes ahead of time so that folks can do any
background reading, using the work I'll be presenting or think about
questions they might have. If you want to send along questions ahead of
time you'd like addressed (or to ensure I cover) please feel free to reply
here and I'll do my best to work them into the presentation.

Rough Topics I'll be covering:

 * Brief presentation on why containers, the technologies involved in build
and deploy
 * Architecture presentation of service breakdown
 * How the PR[1] works
 * Current state and future Roadmap


Thanks,
Eric


[1] https://github.com/theforeman/forklift/pull/424

On Thu, Jun 29, 2017 at 10:15 AM, Greg Sutcliffe 
wrote:

> Hi all,
>
> Running Foreman in a container is a question that comes up from time to
> time in the Foreman community. Eric Helms has been experimenting with
> running the whole Foreman stack (core, proxies, plugins) inside
> Kubernetes, and wants to show you how it looks. We'll be holding a deep
> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
> here:
>
> https://www.youtube.com/watch?v=mPjUvNAYp1c
>
> As always, we welcome your contributions to the video - do join us live
> on YouTube Live chat or in our IRC channel to put your questions to
> Eric!
>
> Cheers,
> Greg
> --
> IRC / Twitter: @gwmngilfen
> Diaspora: gwmngil...@joindiaspora.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Network provisioning failing

[Renig Tra]

Hi,

I have found the problem. It was that in the server BIOS we had enabled an 
option for "USB Virtual NIC" and that was creating a network interface call 
idrac that was stealing the IP of the provisioning interface (I don't know 
why).
After disabling that feature the server gets installed as expected.

Thanks

El miércoles, 28 de junio de 2017, 14:27:05 (UTC+2), Lukas Zapletal 
escribió:
>
> Hey, 
>
> can you provide more details? Extract the boot configuration files 
> from the ISO and attach, pastebin output of host detail CLI or 
> screenshots of the host itself including NIC screen. 
>
> LZ 
>
> On Tue, Jun 27, 2017 at 6:57 PM, Renig Tra  > wrote: 
> > Hi all, 
> > 
> > I'm trying to install a host with CentOS 7.3 using foreman 1.15.0 but 
> when 
> > booting using a "Full image", the specified network configuration 
> created in 
> > the host is not applied because a new network interface called idrac has 
> > appeared with the same IP configured for the real network interface em1. 
> Do 
> > you know what could be the problem? In the host network configuration 
> there 
> > is only one interface configured, however the boot process it seems is 
> > trying to configured all the physical interfaces with the same IP. 
> > 
> > Thanks 
> > 
> > -- 
> > 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 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Greg Sutcliffe]

Hi all,

Running Foreman in a container is a question that comes up from time to
time in the Foreman community. Eric Helms has been experimenting with
running the whole Foreman stack (core, proxies, plugins) inside
Kubernetes, and wants to show you how it looks. We'll be holding a deep
dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
here:

https://www.youtube.com/watch?v=mPjUvNAYp1c

As always, we welcome your contributions to the video - do join us live
on YouTube Live chat or in our IRC channel to put your questions to
Eric!

Cheers,
Greg
-- 
IRC / Twitter: @gwmngilfen
Diaspora: gwmngil...@joindiaspora.com

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

[foreman-users] Vm creation using API fails

[bijith nair]

Hello Team,

When i try to create vm using API's, It fails with below error..

[root@oel6u5 ~]# curl -X POST -s -H "Accept:application/json" -k -u 
admin:redhat -d "host[name]=mytestdev" -d "host[hostgroup_id]=4" -d 
"host[compute_resource_id]=1" -d "host[powerup]=1" 
https://192.168.133.210/api/v1/hosts/ | python -mjson.tool 
{
"host": {
"errors": {
"base": [
"Failed to create a compute Vmware GDC - Devops (VMware) 
instance mytestdev.testlab.local: Unknown Network ID: \n "
]
},
"full_messages": [
"Failed to create a compute Vmware GDC - Devops (VMware) 
instance mytestdev.testlab.local: Unknown Network ID: \n "
],
"id": null
}
}

Though Hammer cli works fine, I see same error while deploying vm via UI 
but  sumitting the job again fixes it but not happening with API

Rgds/Bijith

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

[foreman-users] Re: Pupet-4 on provisioned hosts

[Akash Kaveti]

I have tried by adding enable-puppet-4 to host parameters. But puppet is 
not installed on the provisioned host.

On Thursday, June 29, 2017 at 1:49:41 PM UTC+2, Akash Kaveti wrote:
>
> Hello,
>
> How can I make sure that puppet- 4 is installed on the hosts that are 
> provisioned with foreman? Currently I am using 1.15.1
>
> Thanks.
>

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

[foreman-users] Pupet-4 on provisioned hosts

[Akash Kaveti]

Hello,

How can I make sure that puppet- 4 is installed on the hosts that are 
provisioned with foreman? Currently I am using 1.15.1

Thanks.

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

Re: [foreman-users] execute hook script before template render

[Adam Winberg]

Thanks for the pointers, much appreciated! I'll give the template ruby
interpreter a go. Plugin is nicer of course, so I'll look into that as
well.

//Adam

On Thu, Jun 29, 2017 at 12:08 PM, Lukas Zapletal  wrote:

> You can turn off safemode and then you have full Ruby interpreter at
> your hands in your template, just do <% anything_you_want_here %>, so
> you can make HTTP request or call an external script to generate the
> token for you (just make sure you update SELinux policy if on Red Hat
> to allow this). You can also install additional gems.
>
> Cleaner way is to write your own plugin, we have an example template,
> generator and docs. Such a plugin can add a new function into ERB
> (even in safemode) that will do the job for you. Example how to do
> this is here:
>
> http://projects.theforeman.org/projects/foreman/wiki/How_
> to_Create_a_Plugin#Extend-safemode-access
>
> Hooks is not the way to do it. Good luck and share your plugin with us!
>
> On Wed, Jun 21, 2017 at 2:18 PM, Adam Winberg 
> wrote:
> > Hi all,
> >
> > I want to place an encrypted one-time-password in my provisioning
> template.
> > This is then used to request a certificate at install time. This OTP is
> only
> > valid for 1 hour, so my idea was to create a host parameter containing
> the
> > OTP right before the provisioning template is requested/rendered, and let
> > the template get the OTP from that host parameter.
> >
> > This is bare-metal installations so I cant set the OTP parameter in
> Foreman
> > at host creation since the actual OS install might happen some time
> later,
> > and then the OTP is invalid.
> >
> > Q1: Is there any way to run a foreman hook script at the time of
> provision
> > template rendering?
> > Q2: Any other suggestions on how to do this?
> >
> > Regards
> > Adam
> >
> > --
> > 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+unsubscr...@googlegroups.com.
> > To post to this group, send email to foreman-users@googlegroups.com.
> > 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 foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [foreman-users] Re: Domain is not set from a host group

[Lukas Zapletal]

Hey,

I hope it solved all your problems, I will work on docs this week.

LZ

On Tue, Jun 20, 2017 at 7:01 PM, Ido Kaplan  wrote:
> I see now that 9.1.1-1 version was released - thank you!
> I recommend to update also plugin documentation.
>
> On Tuesday, June 20, 2017 at 6:20:46 PM UTC+3, Ido Kaplan wrote:
>>
>> Not sure that I understand your reply.
>> Is discovery plugin was released officially today?
>> With a patch that solving the domain host group issue?
>>
>> Ido
>>
>>
>> On 19 Jun 2017, at 23:56, Lukas Zapletal  wrote:
>>
>> Scratchbuild link (built against 1.16-develop but that should not be
>> problem for a quick test):
>>
>>
>> http://koji.katello.org/kojifiles/work/tasks/7487/7487/tfm-rubygem-foreman_discovery-9.1.1-1.fm1_16.git.9.bd67811.git.9.bd67811.el7.noarch.rpm
>>
>> LZ
>>
>> On Mon, Jun 19, 2017 at 10:09 PM, Ido Kaplan  wrote:
>>
>> Nice!, Foreman is loading and it looks like that domain is set correctly
>>
>> from a host group.
>>
>> I will wait for the fix and will execute some more tests again.
>>
>> Where can I subscribe to hear that foreman discovery 9.1.0 was released?
>>
>>
>> On Monday, June 19, 2017 at 10:00:57 PM UTC+3, Michael Moll wrote:
>>
>>
>> Hi,
>>
>>
>> On Mon, Jun 19, 2017 at 09:54:39AM -0700, Ido Kaplan wrote:
>>
>> Foreman is not loading after installing the RPM.
>>
>> Web application could not be started
>>
>>
>> uninitialized constant ApplicationRecord (NameError)
>>
>>
>> Please *revert* the following patch: https://git.io/vQvRe
>>
>>
>> As it turns out, foreman_docivery 9.1.0 is not compatible with Foreman
>>
>> 1.15.x as-is, we're working on a fix now that should be out tomorrow.
>>
>>
>> Regards
>>
>> --
>>
>> Michael Moll
>>
>>
>> --
>>
>> 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+unsubscr...@googlegroups.com.
>>
>> To post to this group, send email to foreman-users@googlegroups.com.
>>
>> 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 a topic in the
>> Google Groups "Foreman users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/foreman-users/qEKYMNDhq1w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] execute hook script before template render

[Lukas Zapletal]

You can turn off safemode and then you have full Ruby interpreter at
your hands in your template, just do <% anything_you_want_here %>, so
you can make HTTP request or call an external script to generate the
token for you (just make sure you update SELinux policy if on Red Hat
to allow this). You can also install additional gems.

Cleaner way is to write your own plugin, we have an example template,
generator and docs. Such a plugin can add a new function into ERB
(even in safemode) that will do the job for you. Example how to do
this is here:

http://projects.theforeman.org/projects/foreman/wiki/How_to_Create_a_Plugin#Extend-safemode-access

Hooks is not the way to do it. Good luck and share your plugin with us!

On Wed, Jun 21, 2017 at 2:18 PM, Adam Winberg  wrote:
> Hi all,
>
> I want to place an encrypted one-time-password in my provisioning template.
> This is then used to request a certificate at install time. This OTP is only
> valid for 1 hour, so my idea was to create a host parameter containing the
> OTP right before the provisioning template is requested/rendered, and let
> the template get the OTP from that host parameter.
>
> This is bare-metal installations so I cant set the OTP parameter in Foreman
> at host creation since the actual OS install might happen some time later,
> and then the OTP is invalid.
>
> Q1: Is there any way to run a foreman hook script at the time of provision
> template rendering?
> Q2: Any other suggestions on how to do this?
>
> Regards
> Adam
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> 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 foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] UEFI PXEBoot not downloading config file

[Lukas Zapletal]

Hello,

I just found that our Preseed template has incorect kind associated,
filed bug and fixed it, we will push an update for 1.15:

http://projects.theforeman.org/issues/20143

In the meantime you can fix this by executing this:

foreman-rake console
> kind = TemplateKind.find_by_name(:PXEGrub2)
> tmpl = ProvisioningTemplate.unscoped.find_by_name("Preseed default PXEGrub2")
> tmpl.update_attribute(:template_kind, kind) if tmpl && kind
> exit

And then you can associate it correctly with your OS.

On Wed, Jun 21, 2017 at 10:10 AM, Stanisław Jakiel
 wrote:
> I've tried loaders from:
> http://downloads.theforeman.org/foreman-bootloaders/
> by putting them under tftp dir
>
> And they behave the same way as stock grubx64.efi from foreman-installer -
> so no luck
> I'll give it a shot with some qemu uefi env.
>
> Please advise about previous question about templates.
>
> Regards
>
> On Monday, June 19, 2017 at 9:27:36 AM UTC+2, Lukas Zapletal wrote:
>>
>> Foreman now supports Grub1, Grub2 and PXELinux templates, you can pick
>> anything you want. Note that Grub1 does not support UEFI.
>>
>> If you install Smart Proxy on a system where Grub1 or Grub2 is
>> available, we generate the bootloader via the installer using mkgrub
>> command. Usually only one of these grubs are available depending on
>> your OS version (e.g. RHEL6 = Grub1, RHEL7 = Grub2, the same for
>> Debians etc). If you want to use let's say PXELinux EFI, you need to
>> deploy pxelinux.efi file yourself. The following snippet comes from
>> our docs:
>>
>> ~~~
>> When creating a new Host, the PXE Loader option must be selected in
>> order to pass the correct DHCP filename option to the client. One
>> option out of the following must be chosen:
>>
>> PXELinux BIOS (loads pxelinux.0 filename from TFTP)
>> PXELinux UEFI (loads pxelinux.efi filename from TFTP)
>> PXEGrub UEFI (loads grub/bootx64.efi filename from TFTP)
>> PXEGrub UEFI SecureBoot (loads grub/shim.efi filename from TFTP)
>> PXEGrub2 UEFI (loads grub2/grubx64.efi filename from TFTP)
>> PXEGrub2 UEFI SecureBoot (loads grub2/shim.efi filename from TFTP)
>> None - no filename passed (e.g. for HTTP booting via iPXE)
>>
>> Grub filenames are different for each individual architecture
>> associated with the Host:
>>
>> grub/bootia32.efi (for Intel named "i*86" where * can be any character)
>> grub/bootx64.efi (for Intel named "x86-64")
>> grub2/grubia32.efi (for Intel named "i*86" where * can be any character)
>> grub2/grubx64.efi (for Intel named "x86-64")
>> grub2/grubaa64.efi (for ARM 64 named either "aa64" or "aarch64")
>> grub2/grubppc64.efi (for IBM POWER named "ppc64”)
>> grub2/grubppc64le.efi (for IBM POWER Little Endian named "ppc64le")
>> grub2/grubXYZ.efi (for arbitrary Architecture named "XYZ")
>>
>> Foreman installer only installs pxelinux.0 and grub2/grubx64.efi (if
>> grub2 is available). In order to boot systems via other loaders like
>> PXELinux EFI or Grub 1 (legacy), deploy the required bootloader files
>> in the TFTP directory.
>>
>> Some operating systems use a “shim” loader for SecureBoot (e.g. Red
>> Hat Enterprise Linux and clones). To use SecureBoot with an operating
>> system that does not use a shim chainloader, make a copy of the signed
>> EFI loader named shim.efi or make a symlink in order to do secure
>> boot.
>> ~~~
>>
>> Now, initially I've implemented this on Red Hat systems and I haven't
>> realized that Red Hat patches Grub2 in order to read configuration
>> files according to MAC address. Debian family does not do that, this
>> results in only reading grub.cfg which does not work. There is one
>> trick you can do in your grub.cfg (this is for Grub2):
>>
>> regexp --set=1:m1 --set=2:m2 --set=3:m3 --set=4:m4 --set=5:m5
>> --set=6:m6
>> '^([[:xdigit:]]{1,2})\:([[:xdigit:]]{1,2})\:([[:xdigit:]]{1,2})\:([[:xdigit:]]{1,2})\:([[:xdigit:]]{1,2})\:([[:xdigit:]]{1,2})'
>> "$net_default_mac"
>> mac=${m1}-${m2}-${m3}-${m4}-${m5}-${m6}
>> configfile=/grub2/grub.cfg-01-$mac
>> source "$configfile"
>>
>> We have recently patched our installer to set this for you by default
>> if you are on non-redhat system so starting from 1.15 this should be
>> in.
>>
>> Second option is to use foreman-bootloaders package which we plan to
>> provide in our repositories which ships builds from RHEL and Fedora.
>> This way you will have all bootloaders installed no matter if you are
>> on older or newer OS. Note it does not ship PXELinux EFI yet as there
>> is no stable release yet. We will add this later.
>>
>> For more details read this chapter:
>> https://theforeman.org/manuals/1.15/index.html#4.4.3ProvisioningTemplates
>> and feel free to improve our docs if you think it's not clear. E.g.
>> the info about non-redhats would be nice to have there.
>>
>> On Sat, Jun 17, 2017 at 5:12 PM, Stanisław Jakiel
>>  wrote:
>> > Hello,
>> >
>> > I've read some posts/issues about UEFI support for foreman:
>> >  -