Hey,
I pushed new minor version of FDI yesterday. It includes one annoying bug fix:
Fixes #20603 - Disable kernel messages on tty1
It also adds small package called "kbd" which will be used in the
future to switch overe to tty2 during kexec to prevent terminal
freezing.
Fixes #20548 - added kbd
Thanks lol
https://www.theforeman.org/plugins/foreman_discovery/9.1/index.html#3.1.4Globalsettings
On Wednesday, 11 October 2017 19:48:04 UTC+1, Lukas Zapletal wrote:
>
> https://www.theforeman.org/plugins/foreman_discovery/
>
> It is all there. LZ
>
> On Wed, Oct 11, 2017 at 6:40 PM, Conor Mc
https://www.theforeman.org/plugins/foreman_discovery/
It is all there. LZ
On Wed, Oct 11, 2017 at 6:40 PM, Conor Mc Garvey wrote:
> Hey,
>
> I'm looking to change the name of the discovered host to something more
> recognisable.
>
> For the name I plan to combine the MAC with another fact (lldp
Hey,
I'm looking to change the name of the discovered host to something more
recognisable.
For the name I plan to combine the MAC with another fact (lldp port
description).
Where in the foreman discovery code does the discovered host name get sent
to foreman?
Thanks
--
You received this me
Im interested in this. Let me know if you can get a working setup. Thanks!
-- gracie mobile
> On Sep 9, 2017, at 11:40 AM, Mrinmoy Acharya wrote:
>
>
> Next i need to install ESXi and Windowsusing same FDI on
--
You received this message because you are subscribed to the Google Groups
Thanks Lukas...
Issue resolvednow i am able to install CentOS 7 and RHEL7.3 on UEFI
system with FDI
Next i need to install ESXi and Windowsusing same FDI on UEFI.
Will keep you postedthanks a lot again :)
Regards.
Mrinmoy Acharya
On Monday, September 4, 2017 at 1:06:49 PM UTC
Hello,
there is no stable build of PXELinux EFI yet, we do not recommend
using that. For UEFI we do recommend Grub2. Therefore by default we
build into Grub2 for PC with UEFI enabled, see dhcpd.conf:
if option architecture = 00:06 {
filename "grub2/shim.efi";
} elsif option architecture = 00:07
Hi Lukas ,
The error is the black grub screen again after the change
it does not boot up the foreman discovery image.
i boot up the client in uefi mode ==> it goes till " fetching netboot
image==> then the black grub screen.
one thing i would like to know where in the grub.cfg it is pointi
Sorry please remove the test
if [ -f "$configfile" ]; then
source "$configfile"
fi
to
source "$configfile"
It was not working properly. Then watch system journal and boot the
file, paste what Grub2 was searching for.
On Wed, Aug 30, 2017 at 2:24 PM, Mrinmoy Acharya
wrote:
> Hi Lukas,
>
> Th
Hi Lukas,
Thanks alot for your help.
Following is my currentgrub2/grub.cfg edited after checking the
github link however, after EFI boot the screen i am geeting is a
black grub prompt screenPlease let me know which line to correct.
==
What is the error message in the VM again?
This is caused by
commit 0363223abbb14a53771181062cc37d94fd3c4b4e
Author: Pavel Matěja
AuthorDate: Wed Jun 7 13:05:36 2017 +0200
Commit: Lukáš Zapletal
CommitDate: Wed Jun 7 13:05:36 2017 +0200
Include grub.cfg-01-$mac files in global temp
I figured out this api, and its mandatory facts:
/api/v2/discovered_hosts/facts
I assumed, that it is only for creating new hosts.
I now understand that it is also to update or add custom facts if needed.
I think this should answer my question.
I will come back with a question, if i still face
This is the workflow that i am trying with hooks and foreman discovery
VM/baremetal gets discovered -> after_create hook gets triggered -> Hook
use the discovery api to get more facts from discovered host -> facts are
used to gather more custom Facts from CMDB and they get uploaded to foreman.
Hi Lukas,
Thanks for the response. Following are the answers:
1. grub2-tools-2.02-0.44.el7.centos.x86_64
grub2-efi-2.02-0.44.el7.centos.x86_64
grub2-2.02-0.44.el7.centos.x86_64
grub2-efi-modules-2.02-0.44.el7.centos.x86_64
2. [root@foreman grub2]# cat grub.cfg
insmod regexp
set net_pxe_mac=$n
Hello,
1) What version of grub2 have you deployed on your TFTP server? Which
distribution?
2) What is inside of /var/lib/tftpboot/grub2/grub.cfg config?
3) When you boot the host that does not work, find TFTP xfer messages
in system journal and paste them here.
LZ
On Sat, Aug 26, 2017 at 9:01
Dear friends,
i have set up Foreman discovery Image 9.1 plugin in one VM workstation
running Foreman server 1.15.0...i am trying to dicover UEFI hosts in
Fooreman gui for further provisioning.
issue: I have to bootup one client node (VM) in Legacy BIOS firmware mode
to get the grub-mac.cfg fil
Hello,
Discovery 9.1.1 is now available in the 1.15 and nightly repositories,
containing the following (more or less) user visible bug fixes since the
9.0.0 release:
#19231 - Better error for refresh fact
#19402 - Correct method for bulk host actions
#19409 - Auto provision now uses anonymous adm
Lukas,
Sorry I didn't see this sooner. Wow, totally missed that var in the
template. That was it. That did the trick. Thank you.
On Wednesday, April 12, 2017 at 4:51:51 AM UTC-4, Lukas Zapletal wrote:
>
> Hey Robert,
>
> welcome to the Foreman community!
>
> So I assume you are using PXEGr
Hey Robert,
welcome to the Foreman community!
So I assume you are using PXEGrub2 (default) template to PXE-boot
discovery. We have this default template snippet:
https://github.com/theforeman/community-templates/blob/develop/provisioning_templates/snippet/pxegrub2_discovery.erb
can you pastebin
I am new to Foreman and am trying to use the Discovery plugin with Smart
Proxy. PXE boot to legacy BIOS works fine and auto-continues, gathers
facts and the node gets discovered. However, when shifting to UEFI boot
mode and booting to the Foreman Discovery image using the same kernel
paramete
Hello,
Discovery 9.0 is ready in the repositories, compatible with 1.15
series. New features:
* UI notifications on discovered nodes
* "Sorry but no templates were configured" on preview finally fixed
* improved UI around discovered node detail page
* other bugfixes
Fixes #17959 - add plugin per
Hello,
better later then never, I am finally announcing 8.0.1 bugfix minor
release which contains two important changes:
Fixes #18106 - Attribute Error when provisioning with Katello plugin installed
Fixes #16890 - Prevent discovery of managed hosts
It took a little bit longer to release this du
I am sorry but I don't understand your last comment there. Not sure
what is wrong, what your expectations and behavior are. Be more
verbose, reply to the list.
LZ
On Tue, Feb 21, 2017 at 7:24 PM, Ido Kaplan wrote:
> Hi,
>
> Can someone help me please with the issue?
> http://projects.theforeman.
Hi,
Can someone help me please with the issue?
http://projects.theforeman.org/issues/18415
Thanks!
Ido
--
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
Hello all,
Foreman Discovery 8.0 compatible with Foreman 1.14 is ready to be
tested with the latest Release Candidates. Following the steps of
previous version, 8.0 is a bugfix release. There is more than 20 bug
fixed in this release. Deface is no longer used in the plugin thanks
to refactoring, t
Hello everyone,
with Foreman 1.14 approaching, we are giving out updated FDI version 3.3.1.
This will be followed by Foreman Discovery 7.1, but version 7.0.x is
compatible with Foreman 1.14 and fully supported.
There are no changes from 3.2 other than this was build against CentOS 7.3
and Foreman
Hello,
Foreman Discovery 7.0.1 was made available during Christmas for Foreman
1.13 and 1.14 (RC). This minor version includes four changes: two
regressions in regular provisioning (architecture, OS, bond NIC), upgrade
path from 1.11 or older version and regression in 1.14 RC version.
Bug #16750:
Hello,
I am late on the announcement due to my week off, but the packages were already
in our repos: Foreman Discovery 7.0.0 and Foreman Discovery Image 3.2.0.
These are Foreman 1.13+ compatible.
Foreman Discovery 7.0 is mostly a bugfix release with some refactoring around
strong parameters and
Hopefully i'll have some time to improve my ruby non-existence skills ;),
if only it was written in python (django) it could be easier for me.
But i think i figured out a few things by your reply :)
Than you for the warm welcome, i'm getting foreman+puppet into our
environment, I am also going t
> It looks like the reboot calls goes to the smart_proxy_discovery_image
> plugin which is installed in the discovery image.
> I created a hack that allows me to set a kernel command line "bootpxe=1"
> (any value though should work) and it will set the bootdev to pxe before
> the reboot.
> In th
I created a small hack, my ruby skills are way off, it's the first time i
code anything in ruby :)
It looks like the reboot calls goes to the smart_proxy_discovery_image
plugin which is installed in the discovery image.
I created a hack that allows me to set a kernel command line "bootpxe=1"
(a
I also use it to provision ESXi hosts, I saw the PXEless discovery option,
i'm not after it.
I will probably generate my own modified image as a fast workaround.
The ideal will be to add an option to let the "reboot" command know we also
want to set bootdev to PXE
On Monday, June 20, 2016 at 3:3
> But why don't you simply use PXE-less discovery mode? Just boot the
> server from the discovery ISO (attach it via your IPMI) and it will then
> start provisioning without rebooting the system (via kexec).
>
> https://theforeman.org/plugins/foreman_discovery/5.0/index.html#5.3PXE-lessdiscovery
> I can think of many way to implement it, another way will be to create a
> custom discovery image (hack it in some way) but wonders if i am missing
> anything before i go this route
You can indeed create a foreman discovery image extension. Perhaps hack
the "poweroff" command which is called f
My servers primary boot device is not PXE, if i provision a server with the
discovery plugin (I do restart the server into PXE mode using IPMI, not
from Foreman), then when i Provision the server through the Discovery
plugin, The server reboots as expected but it doesn't go into PXE, Is there
a
35 matches
Mail list logo
