Bug #1830

Puppet run triggers "no puppet proxy defined - cant continue" after 1.0 upgrade

Added by Keiran Sweet over 10 years ago. Updated over 4 years ago.

Puppet integration
Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


I've just upgraded from 0.4.2 -> 1.0.1 without any major issues, however i do use the run Puppet functionality of foreman as a stop gap until I get mcollective sorted out.

After upgrade, testing the puppet run functionality on existing nodes was triggering the no "puppet proxy defined - cant continue" error message in the top right hand corner of the node information screen.

Digging a little deeper seems to show that the puppet_proxy_id value in the database inst being updated with the new Puppet proxy value, the workaround for this at the moment is either:

Manual approach:
For each host click the edit button, ensure your Puppetmaster value is set as required and click submit, the puppet_proxy_id value will be updated in the database. In my case, the puppetmaster value was already correct, but the process of jumping in and out of the edit host screen was enough to trigger a database update for the node.

Automatic approach:
Write some MySQL to update the values of each hosts puppet_proxy_id values to reference the required proxy, this should be simple enough if you have one puppet proxy, however it could get a little complex if you have many hosts and multiple proxies.

Not a huge issue, but something that needs to be looked into when upgrading.



no_proxy_defined_-_cleaned.jpg View no_proxy_defined_-_cleaned.jpg 171 KB Keiran Sweet, 08/20/2012 08:34 AM
No proxy defined   cleaned

Related issues

Related to Foreman - Bug #3214: No location / Organization if host added by default from puppet runClosed2013-10-08

Associated revisions

Revision 5ab79857 (diff)
Added by Ohad Levy about 9 years ago

fixes #1830 - auto assign puppet proxy if its not defined upon facts/reports event


#1 Updated by Ohad Levy about 10 years ago

yep, this makes a lot of sense, we actually wrote a code to do that migration, but needs to assume you had a proxy configured before that.

we should see if we can come up with a better way. (or simply add mass assign of puppet masters to hosts).

#2 Updated by Keiran Sweet about 10 years ago

Just to make things a little more interesting, I noticed that puppet kick functionality is gone as of Puppet 3.x:

Obviously it will take a while for Foreman to support this version, however it does add a couple of other things to think about.


#3 Updated by Greg Sutcliffe about 10 years ago

  • Target version set to Bug scrub

#4 Updated by Crag Wolfe over 9 years ago

I also ran into this issue with a fresh foreman 1.1 install using rhel6.4 and sqlite. I "registered" my guest system to foreman manually rather than have foreman provision it (that is, I just ran "puppet agent -t" from the command line and then started the puppet service). Both foreman and the guest systems have puppet 3.1.1. The foreman versions are: foreman-1.1stable-3.el6.noarch, foreman-proxy-1.1stable-1.el6.noarch, foreman-sqlite-1.1stable-3.el6.noarch.

As is described in this issue, after I go into "Edit" host but leave the Puppet Master unchanged with my only smart proxy, the "Run puppet" button works after that.

#5 Updated by Sam Kottler over 9 years ago

  • Assignee changed from Ohad Levy to Sam Kottler
  • Target version changed from Bug scrub to 1.2.0

#6 Updated by Ohad Levy over 9 years ago

now that we have a puppet proxy validation, can we auto update the host from where the enc/report came from?

#7 Updated by Dominic Cleal over 9 years ago

  • Target version changed from 1.2.0 to 1.3.0

#8 Updated by Lukas Zapletal about 9 years ago

  • Description updated (diff)
  • Target version deleted (1.3.0)

#9 Updated by Dominic Cleal about 9 years ago

  • Related to Bug #3214: No location / Organization if host added by default from puppet run added

#10 Updated by Anonymous about 9 years ago

  • Status changed from New to Assigned

#11 Updated by Anonymous about 9 years ago

  • Status changed from Assigned to Ready For Testing

#12 Updated by Anonymous about 9 years ago

  • Assignee changed from Sam Kottler to Anonymous

#13 Updated by Dominic Cleal about 9 years ago

  • Target version set to 1.15.0

#15 Updated by Dominic Cleal about 9 years ago

  • Legacy Backlogs Release (now unused) set to 2

#16 Updated by Ohad Levy about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF