Re: [foreman-users] Excessive looping while loading host edit page

ced that. If that's the case, this should be a > non-issue for us in the long term... once we upgrade :) > > On Thursday, February 2, 2017 at 6:29:37 PM UTC-5, Stefan Lasiewski wrote: >> >> How funny. I was just looking this up also. Also running Puppet 3.8 & >> F

Re: [foreman-users] Excessive looping while loading host edit page

How funny. I was just looking this up also. Also running Puppet 3.8 & Foreman 1.12.x, and a dozen Docker hosts. Turns out that Foreman doesn't like 12 hosts with dozens of interfaces on each! Looks like this has also been fixed in Foreman 1.14. See http://projects.theforeman.org/issues/16834 ,

Re: [foreman-users] Excessive looping while loading host edit page

Can we remove the interfaces from the WebUI besides deleting the host and re-run puppet? Won't we lose configuration data when we delete the host from Foreman? -= Stefan On Thursday, February 2, 2017 at 3:29:37 PM UTC-8, Stefan Lasiewski wrote: > > How funny. I was just looking this u

[foreman-users] VMware: Can't remove NIC on VMs provisioned by Foreman

Foreman: 1.11.4 VMware vSphere 6.x I hooked up vCenter to Foreman as a compute resource, and provisioned a dozen CentOS 7 VMs using Foreman and Network Boot. Now, when I try to remove some Network interfaces on some of the hosts, vCenter complains with: A specified parameter was not

[foreman-users] Re: VMware: Can't remove NIC on VMs provisioned by Foreman

ut i think the best option is to remove the > network card as a bootdevice once the guest build status is complete and > enable it once you decide to rebuild it. > > > > > On Tuesday, February 7, 2017 at 4:06:47 AM UTC+2, Stefan Lasiewski wrote: >> >> >> For

[foreman-users] Adding a new Libvirt compute resource, but how can I add a password?

I'm hooking Foreman into two servers which run KVM & Libvirt. I'm following 5.2.5 Libvirt Notes , and I created a SSH Key for testing. I can successfully reach the remote hypervisors with a command like `virsh -c

[foreman-users] foreman-rake "Don't know how to build task 'templates:purge'"

I'm running CentOS 6 with SCL, and we're still on Foreman 1.11. I'm trying to work with foreman_templates to update my templates. I installed foreman_templates a few weeks ago using `foreman-installer` and I thought it was working then.

Re: [foreman-users] Using the <%= options %> or <%= pxe_kernel_options %> array in templates?

up, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- Stefan Lasiewski Email: stef...@nersc.gov Computer System Engineer IIIE

[foreman-users] How should I keep my templates up to date?

We recently discovered that some of our provisioning templates in Foreman are out of date compared to the -stable branches at https://github.com/theforeman/community-templates/branches . In some cases, we're concerned that the templates are way out of date, possibly since we started with

Re: [foreman-users] foreman-rake "Don't know how to build task 'templates:purge'"

On Wednesday, October 12, 2016 at 2:12:42 AM UTC-7, Greg Sutcliffe wrote: > > On 11 October 2016 at 19:25, Stefan Lasiewski <slasi...@lbl.gov > > wrote: > > I was able to get the correct version of my templates by specifying the >> correct foreman branch, li

Re: [foreman-users] How should I keep my templates up to date?

Okay, thanks for that information. Also, it looks like I can print out my current templates with the Hammer CLI, like this: ``` hammer template dump --name "Kickstart default PXELinux" |less <%# kind: PXELinux name: Kickstart default PXELinux (Locally Customized) oses: - CentOS 4 -

[foreman-users] Using the <%= options %> or <%= pxe_kernel_options %> array in templates?

Hi all, Currently, we have a couple templates with local customizations to do things like pass on Kernel parameters, like this example from the `Kickstart default PXELinux` template. <%-# NOTE: # If host is VMware (If it uses the VMware provider), than pass kernel params to avoid