On Wed, 2017-10-25 at 15:39 -0700, steved0ca wrote: > 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.
That's a bug if it's reproducible, as Foreman cannot use both for a VM creation anyway - they're mutually exclusive. If the user-data flag is set on the Image then it can only use that template. > 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': There's two things here. That it is attempting to use the finish template suggests the user-data flag is not set on the Image, or not working. The choice of user & password for an SSH-based image, though, is configurable in the Image (in the edit page). Note when I say Image, I'm talking about the object in the Foreman UI that is linked to the AMI, not the AMI itself. 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
