Project

General

Profile

Actions
Copy link

Bug #1549

closed

Triggering 'Run puppet' from GUI returns 500 error

Added by Povilas Daukintis over 12 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Low
Assignee:
Sam Kottler
Category:
Puppet integration
Target version:
Bug scrub
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Hello,

I am using following foreman and foreman-proxy versions:

foreman: pre-0.5 (last git commit: dda8e2b951d52a5bfff13317f0b34a9a3c479574)
foreman-proxy: last git commit (aa0a791aa817b0a6a911fa3abe3341a3967dd698)

When triggering 'Run puppet' from Foreman GUI, 'failed to execute puppetrun: 500 Internal Server Error' message is returned, but Puppet agent is triggered successfully on node.

Foreman-proxy configuration was done according this documentation:

http://theforeman.org/projects/smart-proxy/wiki/Settingsyml

Snippet from foreman-proxy.log after triggering 'Run puppet':

E, [2012-03-26T09:29:22.954497 #24332] ERROR -- : Failed puppet run: Check Log files

You can find foreman and foreman-proxy configuration files attached to this ticket.

This bug is low priority and not a show stopper, but it might confuse Foreman GUI users.

Files

foreman_proxy_settings.yaml foreman_proxy_settings.yaml 415 Bytes Foreman proxy settings file Povilas Daukintis, 03/26/2012 02:46 AM
foreman_settings.yaml foreman_settings.yaml 81 Bytes Foreman settings file Povilas Daukintis, 03/26/2012 02:46 AM
puppetrb.patch puppetrb.patch 665 Bytes Povilas Daukintis, 04/04/2012 09:37 AM
Actions
Copy link

Also available in: Atom PDF