Foreman really does this: ssh user@IP_OF_HOST "run script" So make sure the IP is correctly routed, I have no idea why it would connect to itself.
LZ On Tue, Mar 28, 2017 at 3:09 PM, Tyler Gregory <[email protected]> wrote: > That's definitely what I'm doing wrong, but isn't it odd that Foreman runs > the templates on itself in the absence of a provisioning IP address? > > On Tuesday, March 28, 2017 at 4:40:15 AM UTC-5, Lukas Zapletal wrote: >> >> Foreman connects to the IP address that is defined for your >> provisioning NIC, check the IP and routing from Foreman server. >> >> LZ >> >> On Mon, Mar 27, 2017 at 10:37 PM, Tyler Gregory <[email protected]> wrote: >> > Hello all, >> > >> > I am attempting to use Foreman to provision a Linux VM on VMware, and to >> > use >> > a finishing script over SSH. The VM deploys fine, but instead of being >> > run >> > on the VM, the finishing script is run on the Foreman box itself. >> > >> > Here's the template: >> > #!/bin/bash >> > >> > wall "Test" >> > >> > cat /etc/puppet/puppet.conf << EOF >> > >> > [main] >> > vardir = /var/lib/puppet >> > logdir = /var/log/puppet >> > rundir = /var/run/puppet >> > ssldir = \$vardir/ssl >> > >> > [agent] >> > pluginsync=true >> > report = true >> > ignoreschedules = true >> > ca_server = <My CA server> >> > certname = <%= @host.name %> >> > environment = production >> > server = <My puppet master> >> > >> > >> > EOF >> > >> > >> > puppet_unit=puppet >> > /usr/bin/systemctl list-unit-files | grep -q puppetagent && >> > puppet_unit=puppetagent >> > /usr/bin/systemctl enable ${puppet_unit} >> > /sbin/chkconfig --level 345 puppet on >> > >> > >> > export FACTER_is_installer=true >> > >> > >> > /usr/bin/puppet agent --config /etc/puppet/puppet.conf --onetime --tags >> > no_such_tag --server <My puppet master> --no-daemonize >> > >> > >> > if [ -f /usr.bin/dnf]; then >> > dnf -y update >> > else >> > yum -t -y update >> > fi >> > >> > >> > sync >> > >> > >> > exit 0 >> > >> > >> > I realize there are some errors with the template, and the wall was only >> > placed there as a troubleshooting measure, but I have no idea what could >> > be >> > causing Foreman to execute this template on itself instead of on the VM. >> > Any >> > help is appreciated. >> > >> > Thanks, >> > >> > Tyler >> > >> > -- >> > 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. >> >> >> >> -- >> Later, >> Lukas @lzap Zapletal > > -- > 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. -- Later, Lukas @lzap Zapletal -- 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.
