I was seeing this on 1.15.4 and upgraded to 1.15.6 with the same results. For some reason image based deployments that have userdata enabled also require a finish template associated.
This leads to 1 of 2 outcomes: 1. as Ivan stated, the host creation UI throws this error and a cannot proceed 2. as a workaround, a finish template is associated, but if VM is being deployed with a non-root user (ie 'centos' for Centos instances) the provisioning cannot be completed via SSH as the wrong user is trying to login to run the finish script. This happens even if the image is configured with user 'centos': logs: 2017-10-25 15:31:45 1c049de5 [sql] [I] About to start post launch script on test28.ipadomain.com 2017-10-25 15:31:45 1c049de5 [sql] [I] generating template to upload to test28.ipadomain.com 2017-10-25 15:32:25 1c049de5 [sql] [I] Remove puppet certificate for test28.ipadomain.com 2017-10-25 15:32:27 1c049de5 [sql] [I] Adding autosign entry for test28.ipadomain.com 2017-10-25 15:32:37 1c049de5 [app] [W] Failed to launch script on test28.ipadomain.com: Please login as the user "centos" rather than the user " root". 2017-10-25 15:32:37 1c049de5 [sql] [W] Rolling back due to a problem: [#<Orchestration::Task:0x00000006e35e30 @name="Configure instance test 28.ipadomain.com via SSH", @status="failed", @priority=2003, @action=[#<Host::Managed id: 104, name: "test28.ipadomain.com", last_compile: nil, last _report: nil, updated_at: "2017-10-25 22:31:45", created_at: "2017-10-25 22:31:45", root_pass: "<snip>", architecture_id: 1, operatingsystem_id: 3, environment_id: 4, ptable_id: nil, medium_id: nil, build: true, comment: "", disk: "" , installed_at: nil, model_id: nil, hostgroup_id: 4, owner_id: 5, owner_type: "User", enabled: true, puppet_ca_proxy_id: 1, managed: true, u se_image: nil, image_file: nil, uuid: "i-06d131076cfee4de4", compute_resource_id: 2, puppet_proxy_id: 1, certname: nil, image_id: 2, organiz ation_id: 1, location_id: 3, type: "Host::Managed", otp: "0Jk(/vE83}OY%cib>,+a.k", realm_id: 1, compute_profile_id: 6, provision_method: "im age", grub_pass: "<snip>", content_view_id: nil, lifecycle_environment_id: nil, global_status : 0, lookup_value_matcher: "fqdn=test28.ipadomain.com", pxe_loader: "", discovery_rule_id: nil>, :setSSHProvision], @timestamp=2017-10-25 22:32: 37 UTC>] 2017-10-25 15:32:37 1c049de5 [sql] [I] Remove puppet certificate for test28.ipadomain.com 2017-10-25 15:32:39 1c049de5 [sql] [I] Delete the autosign entry for test28.ipadomain.com 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Prepare post installation script for test28.ipadomain.com *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Wait for test28.ipadomain.com to come online *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Enable certificate generation for test28.ipadomain.com *rollbacked* 2017-10-25 15:32:39 1c049de5 [sql] [E] Task Configure instance test28.ipadomain.com via SSH *failed* On Saturday, 7 October 2017 07:38:52 UTC-7, Ivan Adji-Krstev wrote: > > Hi Greg, > > I'm using Version 1.15.4. The newest one. > > On Thursday, October 5, 2017 at 12:24:46 PM UTC+2, Greg Sutcliffe wrote: >> >> On Thu, 2017-09-28 at 07:08 -0700, Ivan Adji-Krstev wrote: >> > Hi Greg, >> > and when i press resolve i got this message >> > Also when i try to press submit i get the same error. >> > >> > There is no finish template anywhere as options on the way. I have >> > try to lock the template but again same results. >> >> What version of Foreman are you on? There was a bug with the Resolve >> Templates button in recent Foreman versions (1.14 & 1.15, I think), but >> that was fixed in 1.15.4. >> >> Greg >> > -- 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, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, 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.
