[foreman-users] Debian 8.5 installation Media changes during install to 8.7

Hi, I've configured an "Operation System" for Debian 8.5. After some month of installation I've also get automatically Debian 8.6 and 8.7

[foreman-users] Re: no new entries to /etc/salt/autosign.conf during provisioning

No one else runs into that problem? Or have a hint? :-/ Am Donnerstag, 9. Februar 2017 16:14:01 UTC+1 schrieb Tom K.: > > Hi, > > when I install new hosts via Foreman, everything works fine. Just the fact > that no salt autosign will work. I have to > do it manually with s

[foreman-users] no new entries to /etc/salt/autosign.conf during provisioning

Hi, when I install new hosts via Foreman, everything works fine. Just the fact that no salt autosign will work. I have to do it manually with salt-key -A After accepting manually the salt run from foreman works perfect. I find now helpful entry in the foreman logs to fix this. Does anyone have

[foreman-users] Re: Debian Installation -suddenly mount of sda failed

The initrd Images on the tftp are not compatible to the wished installing instance. I've deleted them manually from my tftp server and let them recreate from foreman. Now the installation is running fine. But find that out. *arg* Am Freitag, 27. Januar 2017 10:24:52 UTC+1 schrieb

[foreman-users] Debian Installation -suddenly mount of sda failed

Hi, I've a running foreman setup. I've already installed enough machines to our vsphere. My last VM instance installation was in dec 2016 but now, without any changes to my foreman I get

[foreman-users] wrong number of arguments 'set_hostgroup_defaults_with_salt_proxy' - v1.13.2

Sorry, I've more/better details but the same error. If I select any of my hostgroups during the "new host" process, following Exception is thrown. And I can't set/update further settings through ComputeProfile oder Envorinment or PuppetCA. Nothing inherit from my hostgroup will get set. Hope

[foreman-users] Re: massiv Problems during create new Host on 1.13.2

call' | /opt/rh/sclo-ror42/root/usr/share/gems/gems/rack-1.6.2/lib/rack/sendfile.rb:113:in `call' | /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:518:in `call' | /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:165

[foreman-users] Re: massiv Problems during create new Host on 1.13.2

Just I've I save a new, unfinished configured host, there comes the message that I have to check my Interfaces for it. Ok, thats clearly... I haven't set it since it keeps on "Baremetal" after I've switched to a hostgroup. After that mistaken save there are the settings, inherit from my hostgrou

[foreman-users] massiv Problems during create new Host on 1.13.2

Hi, I've installed a new and fresh Foreman 1.13.2 Have configured subnets, profile and resources. Also installation stuff and some HostGroups. And a working smartproxy for salt. Now, if I want to install a new host on our vsphere I run into problems. I select a defined hostgroup which reference

Re: [foreman-users] Foreman - 0 bytes file boot/CentOS-7.2-x86_64-vmlinuz

n the right direction. It's working now. Thanks a lot, Tom Am Donnerstag, 24. November 2016 18:15:57 UTC+1 schrieb Neil Hanlon: > > Anything in /var/log/foreman-proxy/proxy.log on your smart proxy w/ regard > to pulp or CentOS-7.2-x86_64-vmlinuz? > > On Thu, Nov 24, 2016 a

Re: [foreman-users] Foreman - 0 bytes file boot/CentOS-7.2-x86_64-vmlinuz

s-001 in.tftpd[16470]: RRQ from 10.1.92.157 filename boot/CentOS-7.2-x86_64-vmlinuz.c32 Am Donnerstag, 24. November 2016 17:51:46 UTC+1 schrieb Neil Hanlon: > > Try removing these files from the proxy and doing a "cancel build" -> > "build" on the host. > > T

[foreman-users] Foreman - 0 bytes file boot/CentOS-7.2-x86_64-vmlinuz

Hi! I've build a couple of debian hosts with my foreman setup. Now I want to setup some CentOS Machines. But during Build process the PXE Start via TFPT failed. It says Could not find boot/CentOS-7.2-x86_64-vmlinuz I checked this on my smartproxy. It's there, but just 0 bytes. -rw-r-

Re: [foreman-users] Re: Finished unattend installation callback failed, 409 possible Loop

such an IP. > > On Wed, Nov 23, 2016 at 1:32 PM, Tom K. > wrote: > >> Further more, if I run >> >> puppet agent --test >> >> on one of that doubled machines, it pushes the report to the IPAddress >> named ones. >> >> >> -- >

[foreman-users] Re: Finished unattend installation callback failed, 409 possible Loop

Further more, if I run puppet agent --test on one of that doubled machines, it pushes the report to the IPAddress named ones. -- 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,

[foreman-users] Finished unattend installation callback failed, 409 possible Loop

Hi, when I install a new machine, the whole procedure runs fine. Get its files from tftp, runs installation but during callback it failes. When I set in the f

[foreman-users] 2 Location, 2 SmartProxy, 1 Foreman - 409 Loop

Hi, I've the following setup showing in the attached Image. 2 Location, 2 SmartProxy, 1 Foreman. Provisioning in the same Location (Network) where the Foreman lives works fine. If I install a VM in Location B, the provisioning works fine. It takes IP settings from the SmartProxy in its lo

Re: [foreman-users] undefined method 'physical_device' in preseed_networking_setup

Perfect! But there are still some other errors. Will report @github Thanks. -- Tom Am Freitag, 14. Oktober 2016 11:29:31 UTC+2 schrieb Dominic Cleal: > > On 14/10/16 09:14, Tom K. wrote: > > Hi, > > > > I try to provision a vm machine with an alias/virtual Interface

[foreman-users] undefined method 'physical_device' in preseed_networking_setup

Hi, I try to provision a vm machine with an alias/virtual Interface like eth0:1. So far so good. After the first build and the final Callback to Foreman I get an Exception in the foreman log so that the "wget" command to finish build cancels. | ActionView::Template::Error: The snippet 'preseed

[foreman-users] Re: error listing VMs: No route matches, what does it mean?

Still no idea what this means. Did anyone have any idea what "missing required keys" mean? What kind of key? Or is it more the fact "no route matches" *desperate* -- Tom Am Mittwoch, 10. August 2016 11:41:23 UTC+2 schrieb Tom K.: > > Hi! > > I've a (seems s

[foreman-users] error listing VMs: No route matches, what does it mean?

Hi! I've a (seems so) proper working foreman. Deployment on VMWare vSphere works fine. Now I want to associate some existing VMs via "compute resource" but all I get is the following error. There was an error listing VMs: No route matches {:action=>"show", :compute_resource_id=>#1, :pubkey_ha

[foreman-users] undefined method `join' for #, receiving salt states from smartproxy

Hi, I've a running Foreman 1.11.3 and a Smartyproxy 1.11.3 on 2 different machines. The Smartproxy serves the salt-api/saltmaster. Now, if I query from Foreman the states of the Saltmaster SmartyProxy, nothing happens. Sometimes a popup appears with the message Error: ERF12-4701 [ProxyAPI::P

Re: [foreman-users] Plain installation CentOS / SSLCertificateChainFile: file '/var/lib/puppet/ssl/ca/ca_crt.pem' does

n 30/06/16 08:40, Tom K. wrote: > > While checking with "systemctl status httpd.service" > > > > Jun 30 03:28:23 foreman-host.internal.loc systemd[1]: Starting The > Apache HTTP Server... > > > > Jun 30 03:28:23 foreman-host.internal.loc httpd[14695]:

[foreman-users] Plain installation CentOS / SSLCertificateChainFile: file '/var/lib/puppet/ssl/ca/ca_crt.pem' does

Hi! I've installed a new Foreman. With : rpm -ivh http://yum.puppetlabs.com/puppetlabs-release-el-7.noarch.rpm yum -y install epel-release http://yum.theforeman.org/releases/1.11/el7/x86_64/foreman-release.rpm yum -y ins

Re: [foreman-users] passing array/list from foreman to smartproxy for saltmaster

Ok, thanks. I will have a look. Currently I've done it with jinja. As parameter value a simple csv List like vhost_configs=images,videos and in the salt sls {% for vhConf in pillar['vhost_configs'].splitt(',') %} it works for me. :-) -- Tom Am Montag, 13. Juni 2016 23:54:29 UTC+2 schrieb

[foreman-users] passing array/list from foreman to smartproxy for saltmaster

Is it (still) not possible to provide via (global) parameters a list of data to a smartproxy for a saltmaster? In Foreman defined : vhost_configs=['images','videos'] And on my SaltMaster in my init.sls {% if pillar['vhost_configs'] is defined %} {% for vhConf in pillar['vhost_configs'] %} c