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 gr
Some error. Katello 3.4.1, upgrade 3.4.0
--
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
Hello,
We are installing Foreman 1.15 with Katello 3.4 and we have found a very
strange issue. When synchronizing the repositories the rpms are not
actually downloaded to the server even though synchronization status is
successful.
This is the configuration of our repository:
ID:
Hello,
according to the pulp docs[1] on-demand download policy (which you're
obviously using for that repository) means: "A download policy that only
saves a content unit locally after a client has requested that content
unit.". So it seems you don't have any rpms locally because they were not
requ
Ups, my old Foreman was 1.9 and it didn't have that option =S Thanks a lot!
El lunes, 19 de junio de 2017, 13:32:20 (UTC+2), Adam Ruzicka escribió:
>
> Hello,
> according to the pulp docs[1] on-demand download policy (which you're
> obviously using for that repository) means: "A download policy t
Thank you for response!
I'm starting to getting this together in my head.
I'm installing Foreman on Ubuntu 16.10.
So basically the flow is following (grub2):
- DHCP exchange, get filename
- Download grubx64.efi that got generated during foreman installation
- As grubx64.efi got generated with
3) To be honest I don't understand this *grub.cfg* trick. It looks like
sourcing *locally available **grub.cfg-01-MAC *whereas it should be
downloaded from foreman's tftp.
Only way for this to work would be regenerating grubx64.efi on each host
creation (with this grub.cfg-01-MAC embedded) but h
Howdy All,
A team of us does release, continuous integration and delivery work and in
the process has started developing a set of Ansible modules designed to
manage entities or perform actions against a Foreman server along with
plugins, namely Katello at present. To that end, we started a reposi
>
> Hello,
>
I have exactly the same request. I want to use Foreman/Katello on Linux
server like we use WSUS on Windows server, to update security errata. We
can do that manually but I don't find how to schedule it.
--
You received this message because you are subscribed to the Google Groups
Hello,
I'm a new user of Foreman/Katello. We want to use this tool on Lunix server
like we use WSUS on Windows server i.e. we want to schedule installation
patch security. I discover how to manually install errata but I don't find
how to schedule.
Is it possible please ? With plugins Tasks may
Updating here for posterity in the list:
I ultimately had to go nuclear and destroy all the tasks using pulp-admin.
This got me unstuck enough to be able to go in and take care of the rest of
the 'stuck' tasks (orphaned stuff from hosts now deleted, etc).
On Thu, Jun 15, 2017 at 10:26 AM John Mit
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_d
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:
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:
>
You want to associate "Preseed default PXEGrub2" for debian distros or
"Kickstart default PXEGrub2" for redhat distros not the "default" or
"local boot" ones, that is not correct.
Default - template that renders to default menu (grub.cfg)
Local boot - template used when host is in production mode
15 matches
Mail list logo
