[foreman-users] Re: Install loop after upgrade to 3.4

2017-06-01 Thread 'Denis Müller' via Foreman users
I have the same issue, no solutions yet... Am Mittwoch, 31. Mai 2017 11:09:56 UTC+2 schrieb Nuno Marques: > > Hi all, > > I've just upgraded katello 3.2 to 3.4. > Now when I create a new Host on VMWare using a bootdisk, it enters a > loop, when the host reboots the installation starts all over

[foreman-users] Import Puppet environments from command line

2017-06-01 Thread Peter Bittner
Hi there, I've successfully managed to set up a Foreman host, a Puppet control repository and r10k on the Foreman host to pull changes from the repo whenever they are made (and merged into the main branch). Hence, Puppet environments are deployed automatically to the host. This is done by r10k,

[foreman-users] Re: Install loop after upgrade to 3.4

2017-06-01 Thread Nuno Marques
What I'm doing right now is: a few minutes after the host starts installing I cancel the build. The host finishes the installation and doesn't start another. On 01-06-2017 09:47, Denis Müller wrote: > I have the same issue, no solutions yet... > > Am Mittwoch, 31. Mai 2017 11:09:56 UTC+2 schrieb N

[foreman-users] Re: Install loop after upgrade to 3.4

2017-06-01 Thread 'Denis Müller' via Foreman users
as a stupid workaround, after host was built, i'm shutting it down, set first boot device to hdd and cancel build in foreman. Am Donnerstag, 1. Juni 2017 12:04:39 UTC+2 schrieb Nuno Marques: > > What I'm doing right now is: a few minutes after the host starts > installing I cancel the build. The

Re: [foreman-users] VM provisioning fails with errors

2017-06-01 Thread Lukas Zapletal
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 nair

Re: [foreman-users] Fresh Foreman 1.15.0 install dhcp subnet issue...

2017-06-01 Thread Lukas Zapletal
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" \ --foreman-proxy-dhcp-nameservers="192.168.${SATNE

[foreman-users] Foreman 1.12 and AWS

2017-06-01 Thread Isidor
Hello all, I trying to test deploy instances in AWS from my foreman, i was following the next guide: https://theforeman.org/2016/02/ec2-provisioning-using-foreman-update.html But when i launched the creation of the new host i had the error: " Failed to create a compute EC2 [...] The key pair 'f

[foreman-users] Re: Howto provision vm on hyper-v

2017-06-01 Thread Andreas Pieniak
Hi lovi, i think libvirt is not the best choice to provisioning vm's on hyper-v architecture. In fact iam not sure if it really works at all - nobody seems to use it for provisioning. A while ago i talked with @dlobatog to creating a new plugin for computing resources on hyper-v on mail, but m

Re: [foreman-users] Fresh Foreman 1.15.0 install dhcp subnet issue...

2017-06-01 Thread Sean A
Thanks for the reply, Lukas. It's possible I ran the command above using the --foreman-proxy-dhcp-subnet='192.168.2.0/24', and it seems using the CIDR notation doesn't work. I started fresh again, with the same installer args and reproduced it, then tried the installer again with --foreman-pr

[foreman-users] Re: foreman_hooks: different json output on create and destroy

2017-06-01 Thread 'Konstantin Orekhov' via Foreman users
> But in 1.15.0 and even 1.14.3 it is like this: > > { > "host": { > "host": { > "ip": "10.109.236.95", > "ip6": "", > "environment_id": 2, > "environment_name": "common", > "last_report": "2017-05-31 12:23:46 -0700", > "mac": "52:54:00:c7:da:da", >