!
On Mon, Dec 18, 2017 at 10:49 AM, <rai...@ultra-secure.de> wrote:
> Am 2017-12-18 10:21, schrieb Lukas Zapletal:
>>
>> Hello,
>>
>> you are doing it right. And yes, the general advice is to setup mirror
>> (Katello/Pulp backend can help you with that a lo
Hello,
you are doing it right. And yes, the general advice is to setup mirror
(Katello/Pulp backend can help you with that a lot if you use RPMs and
there's plugin for SUSE), or you can mirror manually.
Now, Foreman is able to configure two or more ifaces, you pick one as
primary which holds the
We have several users doing that, check demos from this year, we had
one or two demos around this topic.
LZ
On Mon, Dec 11, 2017 at 8:04 AM, shrek maxi wrote:
> If it does. How?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman
Hello,
there is no contract that you are getting same numbers for IPv4 and 6.
This is not a bug, feel free to send RFE or patch to do this.
We have new Random IPAM generator that returns pseudo random IPs
seeded by MAC address of the device. Basically it will always return
you same IP address
It will be best to talk to Red Hat representative about this, but from
the project perspective - you can do whatever you want as long as this
is aligned with open source licenses we use. Check all your plugins
and backends you want to use, but the biggest ones are:
Hello,
the error message says it all. Your client does not know server's
certificate. Import it, it's available in http://katello/pub for
download.
LZ
On Tue, Dec 5, 2017 at 1:58 AM, Philippe Conway
wrote:
> Hello,
>
> I am having issues joining a server to our
gt; (auto-provision vs location).
>
> Regards!
>
> W dniu środa, 29 listopada 2017 14:47:41 UTC+1 użytkownik Lukas Zapletal
> napisał:
>>
>> Does the user who initiates the auto provisioning have "view_params"
>> permission?
>>
>> If you start fo
That is not part of hostgroup I guess, so you need to select it
everytime. That would be a RFE?
LZ
On Thu, Nov 30, 2017 at 12:11 AM, Andre Mosin wrote:
> Did anybody figure out how to change the set a default Provisioning Method?
> I am trying to change to Boot disk based
Does the user who initiates the auto provisioning have "view_params" permission?
If you start foreman-rake console and type:
Host.find(ID).host_param('param_name')
for the already provisioned host, do you get the expected result there?
Can you comment out line "return cached_host_params unless
Yeah, I was thinking something very small and grey - opposite of
distracting big blue button.
LZ
On Fri, Nov 24, 2017 at 3:44 PM, Ivan Necas <ine...@redhat.com> wrote:
>
> On Fri, 24 Nov 2017 at 10:01, Lukas Zapletal <l...@redhat.com> wrote:
>>
>> >> The
>> The most annoying is the big blue button for me, I'd prefer some
>> small light-gray link instead (if any).
>
> As I say, I only see that in HTML-view, are you definitely in plaintext
> mode?
I am not actually, I migrated from Mutt to GMail recently and I have
no option other than HTML here.
Hello,
I never heard of these and I can confirm we haven't changed much
around this in the last release, as you can see our kickstart simply
use default network configuration, thus NetworkManager. I think you
need to reach out to CentOS groups or better test on RHEL and create
Bugzilla for
e to do per-user, which is
> even better (again, flexibility to interact with the community as each
> user wants to).
>
> OK, specific answers:
>
> On 21/11/17 15:09, Lukas Zapletal wrote:
>> 1) Edits are not propagated to e-mail only users, I edited a post
>> andneve
Greg,
I gave Discourse another try via e-mail but I have some issues:
1) Edits are not propagated to e-mail only users, I edited a post and
never got an e-mail about this. If this is a feature (I don't get
notification on my own edits), that's fine, but otherwise this creates
a huge hole as you
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
I am on latest stable Fedora, haven't done anything special, but this
is my development instance, I might have some packages that clean
installation don't have. It should be as easy as:
https://github.com/theforeman/foreman-discovery-image#building
Quick look into yum/dnf database shows this
I can do the discovery part, but frankly not fully understand what
exactly how do we grab the fact value. Is that some value that needs
to be fetched from iDRAC API?
LZ
On Fri, Oct 27, 2017 at 12:47 PM, Konstantin Lepikhov
wrote:
> Hi Greg!
>
> On 10/27/2017, at 10:25:20 AM
Glad you sorted it out.
We do appreciate tutorials, blog posts, puppet PRs for the installer
or simply just community-templates you are using for provisioning.
Currently we only have this in the codebase:
n.R <subup...@gmail.com> wrote:
> Hi Lzap,
> Thanka for your reply. I'm following the same article,but not able to get
> the console for libvirt, getting the same error.can you help me to trace the
> issue?
>
> On Oct 26, 2017 7:25 PM, "Lukas Zapletal" <l..
e only thing
> worked for me so far was to periodically go through discovered hosts and
> remove duplicate entries.
>
> Thanks!
> Konstantin.
>
> On Oct 26, 2017, at 07:18, Lukas Zapletal <l...@redhat.com> wrote:
>
> Ok this confirms it. http://projects.theforeman
Ok this confirms it. http://projects.theforeman.org/issues/21479 we will
fix later.
We don't have an unique index on DB level, just in Rails level and a second
NIC with same MAC can sneak in. The relevant code in core is:
validate :mac_uniqueness, :if => Proc.new { |nic| nic.managed? &&
ger cooperating 'Can't start OMAPI protocol: address not
> available'. I've tried deleting all relevant hosts and emptying out the
> dhcpd.leases file, rebooting both Foreman master and proxy. Nothing seems to
> work. Is the information being stored somewhere else?
>
> On Wedne
SJq4WtjlD68QB9AT4ACLcBGAs/s1600/3.png>
>
>
>
>
> <https://lh3.googleusercontent.com/-0kifxZbRyaI/WfEHx9VlCRI/AFM/WczGZjTR21IxqCjx1SroBxO5mh9wriSewCLcBGAs/s1600/4.png>
>
>
>
>
>
> Thanks.
>
>
>
>
>
>
> On Wednesday, October 25
Please read:
https://theforeman.org/manuals/1.15/index.html#7.1NoVNC
and follow the instructions there.
LZ
On Thu, Oct 26, 2017 at 7:04 AM, Subramaniyan .R <subup...@gmail.com> wrote:
> i have used libvirt,
>
> On Wednesday, 25 October 2017 19:14:34 UTC+5:30, Lukas Zapletal wr
Worked for me on Fedora, do a PR and I can add those files into the
official build.
LZ
On Wed, Oct 25, 2017 at 4:16 PM, Lukas Zapletal <l...@redhat.com> wrote:
> Hello, we do only build on Fedora, the livecd tooling in RHEL7 might
> be little bit outdated.
>
> What is t
Hello, we do only build on Fedora, the livecd tooling in RHEL7 might
be little bit outdated.
What is the reason for shim/efibootloader in discovery image? You want
SecureBoot over PXE?
LZ
On Sun, Oct 22, 2017 at 3:11 PM, Oleg Mcnoleg wrote:
> Hello,
>
> I'm rolling my
Hmm is this Debian? Should work.
LLZ
On Tue, Oct 24, 2017 at 2:50 AM, 'Konstantin Orekhov' via Foreman
users wrote:
>
>> OK, thanks, Lukas! As soon as I get that duplicate entries show up again,
>> I'll run above and provide a result here. After patching for
Hey Trisha,
the error smells like a name resolution error, have you checked DNS?
Does the DHCP server provide correct DNS info, so the system can
resolve installation media or other services involved in provisioning?
Now, the DHCP is really expected to just work. Are you using the ISC
DHCP
Yep, you can also set them to be published via HTTP only (no
certificate needed).
LZ
On Mon, Oct 16, 2017 at 10:05 PM, Jasper Connery wrote:
> Looks like it is possible. Initially ran into problems due to cross-domain
> issues, but I have now got it working.
>
> Assigned the
Autoprovisioning rule lets you use ERB to construct hostname.
Normal provisioning does not. You can however change fact that
construct the name. You can create FDI extension (ZIP FILE) which will
be downloaded during discovery, that can add any fact you want using
Facter API.
All facts are
Absolutely, the API is not much documented, it is a Sinatra App so
just read the code.
LZ
On Mon, Oct 16, 2017 at 4:09 PM, xakraz wrote:
> Hello,
>
>
> I have a question regarding the usage of Foreman SmartProxies as standalone
> pieces without TheForeman.
>
> We have a setup
It is possible, read the manual.
LZ
On Fri, Oct 13, 2017 at 7:01 PM, No1 wrote:
> Hi,
>
> Is there way to alter the look/ columns that are being displayed under the
> discovered hosts?
>
> Currently, it shows the Names with Mac address of the PXE NiC Interface
> with
Ideally I would like to see DEBUG and SQL logs for that transactions, but
thats flooding your production server.
In the console with both records presnet do something like:
::Nic::Managed.where(:mac => "MA:CA:DDRESS::", :primary => true)
On Wed, Oct 11, 2017 at 9:08 PM, 'Konstantin Orekhov' via
Hello,
every puppet or rhsm fact update will add all missing NICs but never
delete existings. You can turn off this behavior, it's a global
setting not sure how its named but it will prevent from any NIC to be
created by facts.
LZ
On Thu, Oct 12, 2017 at 1:32 PM, 'Christian Schulze-Wiehenbrauk'
This patch I am working on will make this much easier!
https://github.com/theforeman/foreman/pull/4891
On Fri, Oct 13, 2017 at 4:53 AM, No1 wrote:
> The Issue is resolved.
>
> But It would be nice not to touch the custom configs that were made into the
> TFTP and DHCP
October 11, 2017 at 4:47:07 AM UTC-4, Lukas Zapletal wrote:
>>
>> No, something happened to DHCP module, check proxy.log and look into
>> initialization phase.
>>
>> Typically, when you perform upgrade of dhcp or tftp daemons (via
>> yum/apt), they will reset permissi
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
Hello,
I have zero experience with Ubuntu/Debian preseed but you need to
identify exactly at which stage you loose IP connection. My bet would
be when the installer attempts to reconfigure network? Perhaps there
is some log on virtual console 2 or higher where you can see this.
FYI Preseed
Oh now I understand, looks like a new bug. I am not able to reproduce
with FDI 3.4.1 and develop Foreman. The code responsible for finding
existing record is here:
https://github.com/theforeman/foreman_discovery/blob/develop/app/models/host/discovered.rb#L53-L62
Theoretically if you changed
No, something happened to DHCP module, check proxy.log and look into
initialization phase.
Typically, when you perform upgrade of dhcp or tftp daemons (via
yum/apt), they will reset permissions on some files or directories
which will cause DHCP module to fail to init. This will fix it:
setfacl
Hey Craig and welcome here.
Can you explain what happens in more detail? At which point you seem
to lost IP address? You say you hit kickstart that would mean Anaconda
was loaded up and initialized network, at this point there is almost
nothing which could literally stop Anaconda from completing
Hey
I did not see any 422 error before this transaction so I think this is it.
> Although I did not see any long MySQL queries, the whole transaction still
> took ~11 seconds to complete for some reason:
>
Name has already been taken - this usually means that host (either
discovered or managed
We do support one subnet per installation via installer/puppet and
multiple subnets via hiera.yaml.
LZ
On Fri, Oct 6, 2017 at 5:42 AM, Grace Thompson <barfingca...@gmail.com> wrote:
> Any plans on enabling Subnet creations?
>
> - gracie mobile
>
>> On Sep 24, 2017, at 11:
Hello,
please use git to find out which branches it landed in, I believe the
MySQL facter patch is 1.15+ only.
For 1.15.5 you need to talk with release engineer of this version
which is Daniel, if the changes are small enough I see no reason not
to include them. I think it's too late for 1.15.5
Let us know next week if this helped. I highly suggest upgrade to
1.15, it is a very solid release.
LZ
On Wed, Oct 4, 2017 at 11:04 PM, 'Konstantin Orekhov' via Foreman
users wrote:
>
>> See the comment there, do you have this in your instance? If not git
>>
Ok I can see there is a subselect, these are sometimes painful
particularly for MySQL. We fixed that already, see in fact_importer.rb
(this is develop branch):
def delete_removed_facts
ActiveSupport::Notifications.instrument
"fact_importer_deleted.foreman", :host_id => host.id, :host_name
Hello,
this page is pretty out of date (2013), you are not supposed to be
installing these services manually, we have a puppet-based installer
that does all the magic. If you do not want to use it, I recommend you
to install foreman on a test server and then investigate the
configuration files
for a long time (minutes to hours). Perhaps try to disable
all foreman jobs and re-test.
LZ
On Thu, Sep 21, 2017 at 2:27 AM, 'Konstantin Orekhov' via Foreman
users <foreman-users@googlegroups.com> wrote:
>
> On Wednesday, September 20, 2017 at 3:55:43 AM UTC-7, Lukas Zapletal wrote:
>>
A MAC address can only exist once, if you already have a
(managed/unmanaged) host and you try to discover a host with same MAC,
you will get error. Depending on Foreman discovery it is either 422 or
"Host already exists":
Well no, the biggest update was for 1.14 there:
http://projects.theforeman.org/issues/9016
That focused on memory consumption tho, there was a little speedup but
nothing big.
On Tue, Sep 19, 2017 at 10:05 PM, 'Konstantin Orekhov' via Foreman
users wrote:
> BTW,
I would rather fix importing code to be faster than doing async, that
is the last resort.
Konstantin, thanks for analysis. Our import code is slow indeed, we
improved it a bit in 1.14. Note we mostly test this on PostgreSQL. For
each import, there is a log in INFO level about how much time was
Hey,
what kind of load do you have? Puppet? Facter? Is that ENC? Something else?
Can you tell which requests are slow from logs or monitoring?
LZ
On Fri, Sep 15, 2017 at 3:35 AM, 'Konstantin Orekhov' via Foreman
users wrote:
>
> Hi, all!
>
> Under increased
/
If this is the case, I think you want to create your host in Foreman
with PXELinux BIOS flag and it will have filename option "pxelinux.0"
which should be ignored by petitboot and then it will try to load the
configuration from standard paths.
On Tue, Sep 5, 2017 at 7:52 AM, Lukas Z
Danielle,
I've talked to our Grub2/PXE/BOOTP/POWER experts, can you get us:
dhcpd.conf
grub.conf
network comm dump (wireshark or similar)
Thanks
On Mon, Sep 4, 2017 at 9:19 AM, Lukas Zapletal <l...@redhat.com> wrote:
> First of all, is your PPC CLIENT big or little endian? I see it is
=boot/fdi-image/initrd0.img ... proxy.url=<%=
> foreman_server_url %> proxy.type=foreman
> IPAPPEND 2
>
>
> thanks and regards,
>
> Mrinmoy
>
> On Thursday, August 31, 2017 at 5:49:34 PM UTC+5:30, Lukas Zapletal wrote:
>>
>> Sorry please remove t
known.
> Sep 1 10:44:32 srv-install dhcpd: none: host unknown.
> Sep 1 10:44:38 srv-install dhcpd: DHCPRELEASE of 172.16.2.207 from
> 70:e2:84:14:1c:13 via eno16780032 (not found)
>
> Without more info.
>
> From the client side I receive the messages:
>
> booting netboot enP5p7s0
Is this non-Red Hat OS? I mean the system that serves the DHCP/TFTP?
> [root@srv-install grub2]# ln -s /var/lib/tftpboot/core.elf grubppc64le.efi
TFTP runs in chroot, never do absolute symlinks, only relative. Not
sure if this is same for non-RH OS tho.
> Aug 31 17:47:54 srv-install
c
> if [ -f "$configfile" ]; then
> source "$configfile"
> fi
>
> <%= snippet "pxegrub2_chainload" %>
> =======
>
>
>
>
>
> On Tuesday, August 29, 2017 at 3:30:55 PM UTC+5:30, Lukas Zapl
Hello,
with recent versions of Foreman (1.14+) you set PXELoader to Grub2 EFI
and then the filename will be grubppc64le.efi or grubppc64.efi
depending on endian.
Note the incorrect extension (PPC is not EFI compatible), we are
tracking this under http://projects.theforeman.org/issues/16706 and
"$net_default_mac"
> mac_dashed=${m1}-${m2}-${m3}-${m4}-${m5}-${m6}
>
> mac_configfile=$prefix/grub.cfg-01-$mac_dashed
> source "$mac_configfile"
>
> 3. Please let me know how to collect this one as I am booting a VM in VMware
> workstation as UEFI client.
Hello,
facts are not reported via hooks.
LZ
On Mon, Aug 21, 2017 at 4:37 PM, wrote:
> Hello,
>
> The issue is that -> i dont see facts in input json after foreman discovers
> a VM/baremetal.
>
> This is the workflow that i am trying with hooks and foreman discovery
>
back. What kind of template should I use then for my
> needs?
>
> Some post-installation configurations? Like DNS, network, Proxy etc..?
>
> On Thursday, August 17, 2017 at 2:14:32 PM UTC+3, Lukas Zapletal wrote:
>>
>> Hello,
>>
>> finish template only trigg
Hello,
finish template only triggers when compute_attributes.present? &&
image_build? && !image.try(:user_data)
In other words, this is only meant for image based provisioning on
virt or clouds. You may want to file a RFE if there is none present
already.
LZ
On Thu, Aug 17, 2017 at 8:32 AM,
Hello,
Foreman can talk to various virtualizations like libvirt or oVirt, but
not to Oracle Virtual VM unfortunately.
What you need to do is to create new VM and write down the VM MAC
address of the interface that is connected to network with Foreman. Do
not start it.
Then Create host,
> [{"network":"192.168.196.0.0","netmask":"255.255.255.0","options":{"range":["192.168.0.201","192.168.0.254"]}}]
This means DHCP proxy module now sees your network but I do not
understand why it reads non-sense:
192.168.196.0.0
It should be:
192.168.0.0
Have you manually edited this line?
Hello,
the subnets in dhcp.yml look suspicious, why you have them there? Also
these are not valid subnet addresses if I am not mistaken. Delete,
restart foreman-proxy.
Before you re-test verify that foreman-proxy see all subnet
definitions in dhcpd.conf, that would be:
curl -kvs --cert
Conor,
to be honest, I am really not sure what you are trying to do. We do
have some iPXE support in Foreman, but this is mostly limited to iPXE
template type, so you can use Foreman to generate its contents. If
your intention is to have Foreman to supply custom DHCP filename
option (e.g.
I am shooting in the dark, but we have this cleanup cron job:
# Expire old reports
30 7 * * * foreman/usr/sbin/foreman-rake reports:expire
>>/var/log/foreman/cron.log 2>&1
It runs daily, so modify it to run weekly perhaps or schedule it into
some quiet period if you have any as an
ne more thing i want to ask is, what is recommended way for doing post
>> configuration of Atomic host, for example DNS,NTP, authentication .. can
>> anyone guide me on this please?
>>
>> I think we can not install puppet for doing post configuration.
>>
>>
an not install puppet for doing post configuration.
>
> Thanks,
> DJ
>
>
> On Monday, 31 July 2017 13:44:43 UTC+5:30, Lukas Zapletal wrote:
>>
>> Dhaval, do you have a case opened?
>>
>> Are you using on-demand download policy for kickstart or ostree?
>
Dhaval, do you have a case opened?
Are you using on-demand download policy for kickstart or ostree?
Have you added both kickstart and ostree into the same content view
which is in use?
LZ
On Thu, Jul 27, 2017 at 8:18 PM, Unix SA wrote:
> Hello,
>
> Is anyone using atomic
You are not expected to do that, RPM packages do call db migration and
seed automatically, but I always recommend to run puppet on *noop*
mode to see the drift.
foreman-installer --scenario katello -v -n
LZ
On Wed, Jul 19, 2017 at 9:24 AM, Johan Loubser wrote:
> Hello
>
>
Hello,
what exactly is your problem? Try to describe in more detail, what
you've provided is sparse. Assuming that you don't see your new plugin
on About page, you need to follow steps of adding the plugin into
Gemfile.local.rb as in
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, a
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
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 G
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
visioning then?
>
> 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
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
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
No ETA yet, you can use this scratchbuild it will work:
http://koji.katello.org/koji/taskinfo?taskID=6018
Report back if it fixes your issue.
LZ
On Tue, Jun 13, 2017 at 1:32 PM, Ido Kaplan wrote:
> Ok, thank you for the update.
> Is there a fix for this issue?
> When it
. Thank you.
>
>
> Thanks,
> Robert Anderson
>
> On Tue, Jun 13, 2017 at 6:54 AM, Lukas Zapletal <l...@redhat.com> wrote:
>>
>> This (*) will be fixed in Discovery 9.1, we are delayed with the release
>> due to issues with building infrastructure. S
>
> The fqdn is still not being tacked on after being found and put into All
> Hosts
>
>
> Thanks,
> Robert Anderson
>
> On Fri, Jun 9, 2017 at 7:02 AM, Lukas Zapletal <l...@redhat.com> wrote:
>>
>> Domain should be included automatically when hostgroup you ass
This (*) will be fixed in Discovery 9.1, we are delayed with the release
due to issues with building infrastructure. Stay tuned.
(*) It's actually similar bug
http://projects.theforeman.org/issues/19313 it's for auto-provisioning
only.
On Mon, Jun 12, 2017 at 7:50 PM, Robert Anderson
This will be fixed in Discovery 9.1, we are delayed with the release
due to issues with building infrastructure. Stay tuned.
LZ
On Tue, Jun 13, 2017 at 12:27 AM, Asher Schaffer wrote:
> Running foreman 1.15.0 on Ubuntu 16.04
>
> Currently discovered hosts are showing up
Will be fixed in Discovery 9.1, we are having some troubles with our
builder so the update is delayed.
LZ
On Mon, Jun 12, 2017 at 8:16 AM, Ido Kaplan wrote:
> Hi,
>
> Foreman version 1.14.3, Discovery plugin version 8.0.1.
>
> During provisioning a server with multiple
Domain should be included automatically when hostgroup you assign to
it has it on primary interface.
LZ
On Thu, Jun 8, 2017 at 8:12 PM, Robert Anderson wrote:
> by FQDN I mean Domain which is associated to the Host Group which is being
> applied via the Discovery rule
>
>
Hey, known error in 1.14 series. Fixed in 1.15, discovery 9.1 tomorrow.
LZ
On Wed, Jun 7, 2017 at 10:51 PM, Robert Anderson wrote:
> Alright. I got rid of it by trying to provision it and deleting it out of
> All Hosts.
>
>
> On Wednesday, June 7, 2017 at 1:34:50 PM
Hello,
Foreman 1.15 or Katello 3.4 hostgroup (combination) provisioning
allows "Satellite 5 - like" provisioning without registering hosts
into system. Although Foreman offers much more flexible and better
ways of provisioning including PXE, PXE-less, bootdisk or discovery,
this is possible.
Our API endpoint did not change, just provide CNAME type. It's in /dns
path, search in dns_api.rb.
LZ
On Tue, Jun 6, 2017 at 5:07 PM, justin parker wrote:
> Based on the issue located here:
> http://projects.theforeman.org/issues/17879
>
> It looks like we can create
Hey,
so you want to create dynamic lease reservations for them, so they are
then managable by Foreman? You can either manually edit dhcp.leases
file and put them there (see other dhcpd.leases under foremans control
for examples), or you can use DHCP API of the DHCP smart proxy to put
the records
Will fix this thanks.
On Mon, Jun 5, 2017 at 7:35 AM, Ido Kaplan wrote:
> Thank you - it's working!
> I suggest to edit the examples (4.3.2 Hostname patterns) in
> https://theforeman.org/plugins/foreman_discovery/8.0/index.html
>
>
> On Sunday, June 4, 2017 at 8:45:17 PM
an_discovery/host_converter.rb appears to have fixed it!
> Thank you
>
> On Wednesday, May 17, 2017 at 2:52:08 AM UTC-6, Lukas Zapletal wrote:
>>
>> Hello, might be also http://projects.theforeman.org/issues/19313
>>
>> Try to comment out this line:
>>
>>
&g
It works here, here is my command:
SATNET=122
--foreman-proxy-dhcp true \
--foreman-proxy-dhcp-interface virbr1 \
--foreman-proxy-dhcp-gateway=192.168.${SATNET}.1 \
--foreman-proxy-dhcp-range="192.168.${SATNET}.10 192.168.${SATNET}.109" \
The DNS server on Foreman does not have foreman A record, add it manually
if this is what you want.
I'd love to have this in our installer, but we don't have it. With katello
plugin installed, you cannot workaround this with unattended_url anymore.
LZ
On Wed, May 31, 2017 at 8:57 PM, bijith
Hello,
although I released Discovery 9.0 plugin for Foreman 1.15
compatibility, we are suffering from several blocker bugs around
Provision Host (Edit Host) form, auto-provisionig, DHCP orchestration
in Foreman and DHCP smart-proxy module. We are planning 9.1 release in
the upcoming week or two.
the best place to start learning how to do this?
>
> On Tue, 2017-05-23 at 09:05 +0200, Lukas Zapletal wrote:
>> Hello,
>>
>> in this case you want to leave default kickstart template "network"
>> configuration as is and only change post configuration for
Hello,
in this case you want to leave default kickstart template "network"
configuration as is and only change post configuration for network:
https://github.com/theforeman/community-templates/blob/develop/provisioning_templates/snippet/kickstart_networking_setup.erb
This is a snippet that is
You forgot the question mark, did you? Or maybe I did in the previous
mail, anyway its really this:
respond_to?(:reports)
https://ruby-doc.org/core-2.4.1/Object.html#method-i-respond_to-3F
LZ
On Fri, May 19, 2017 at 8:47 PM, Konstantin Orekhov wrote:
>
>> unless new_host
On Fri, May 19, 2017 at 10:54 AM, Lukas Zapletal <l...@redhat.com> wrote:
> unless new_host && hostgroup.nil? && reports.nil? && reports.empty?
Sorry I mean:
unless new_host && hostgroup.nil? && respond_to?(:reports) && reports.emp
1 - 100 of 234 matches
Mail list logo