The defacing of the subnet fields partial to remove the domain and proxy association fields affects the normal subnet editing and not just the wizard.

With foreman_discovery - uses deface 1.0.1
With fog - deface < 1 depends on nokogiri ~> 1.4.3, fog uses 1.6.3.1

Don't only use the provisioner host's domain.

The installer modules should be imported and then the host's definition updated instead of using a foreman-installer command.

from production.log :

Started POST "/foreman_setup/provisioners/3/step4" for xxx.xxx.xxx.xxx at 2014-02-10 22:30:25 +0100
Processing by ForemanSetup::ProvisionersController#step4 as HTML
Parameters: {"authenticity_token"=>"xxxxxxxxxxxxxxxxxx", "id"=>"3"}
Rendered vendor/ruby/1.9.1/gems/foreman_setup-1.0.4/app/views/foreman_setup/provisioners/_step4.html.erb (64.4ms)
Rendered vendor/ruby/1.9.1/gems/foreman_setup-1.0.4/app/views/foreman_setup/provisioners/step4.html.erb within layouts/application (64.8ms)
Operation FAILED: cannot load such file -- uglifier
Rendered common/500.html.erb within layouts/application (2.6ms)
Rendered layouts/base.html.erb (1.0ms)
Completed 500 Internal Server Error in 569.7ms (Views: 4.5ms | ActiveRecord: 0.0ms)

I got an issue when tring to install the plugin using the deb package (I'm running Debian Wheezy).
I eventually found out that the postinst script logged everything in /var/log/foreman-installer.log so I could identify the issue : the gem has a dependency on deface which needs nokigiri which itself requires libxslt-dev and libxml2-dev to build successfully.
I don't really know if something can be done on the packaging side, but maybe something about this issue could be added to the README ?

Non-admins should be able to set up provisioners.

The foreman-installer command requires various subnet options, but no extra validation is added to ensure they're entered.

Clicking next on this screen

leads into this error

We are running foreman 3.1 on Ubuntu 20.04.

The install media setup page is intended to allow selection between a normal install media URL or a Spacewalk/Sat5 server, then generate the install media URL just based on the Spacewalk hostname.

When I ran foreman-installer

Here is the result:

/usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- kafo (LoadError) from /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/site_ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:inrequire'
from /usr/sbin/foreman-installer:5:in `

When using foreman_setup and katello, it produces output for foreman-installer. Instead, the output should be katello-installer and options (--foreman-proxy) should be replaced by --capsule options.

Once you create a provisioning setup, it's impossible to go through the wizard again to setup new networks. In my case I'm setting up a home network and a libvirt network, yet I have to remove the 'setup' object in order to create a new provisioning setup.

In foreman where can I manually change my IP address? Thanks.

Wrong arguments:
--foreman-proxy-parent-fqdn=
--foreman-proxy-foreman-oauth-key
--foreman-proxy-foreman-oauth-secret

Correct Arguments:
--foreman-proxy-content-parent-fqdn
--foreman-proxy-oauth-consumer-key
--foreman-proxy-oauth-consumer-secret

RPM version: tfm-rubygem-foreman_setup-7.0.0-1.fm1_24.el7.noarch

Thanks

Hello
Are there any docs how to use this in hiera with foreman?
Actually, I couldn't find any docs whatsoever for this plugin :/
Thanks

The wizard should set up associations required for foreman_bootdisk.

It should allow setup or even provisioning of other provisioner hosts.

When trying to edit a previous provisioning setup the subnet is flagged as already being created. This should ideally look if the subnet is created and and move on to the next screen.

Created from: https://projects.theforeman.org/issues/25176

Installed this plugin under Katello-3.X and it generates the wrong commandline in foreman_setup/app/views/foreman_setup/provisioners/_step3.html.erb
It checks for Katello vs Foreman but Katello switched to foreman-installer instead of katello-installer since version 3.0 or higher (might even be since 2.4, I'm not sure)