Bug #1733: Environment issue if the env is not specifically defined - Smart Proxy - Foreman

Actions

Copy link

Bug #1733

closed

Environment issue if the env is not specifically defined

Added by Jeff Palmer over 12 years ago. Updated over 12 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Greg Sutcliffe

Category:

API

Target version:

1.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

When using puppet in a "default" single environment scenario (as in, no [production] stanzas in the puppet.conf) the smart proxy returns an empty array of environments when you query the http://foreman.example.com:8443/puppet/environments URL

Actions

Copy link

Updated by Greg Sutcliffe over 12 years ago

Status changed from New to Ready For Testing
Assignee set to Greg Sutcliffe
% Done changed from 0 to 80

We're testing for conf[:main][:modulepath] || conf[:master][:modulepath] but a 'basic' puppet.conf (like http://pastebin.com/1w40gqWc) has neither. We can fix this by adding the global Puppet default modulepath.

Pull request with proposed fix at: https://github.com/theforeman/smart-proxy/pull/23

Actions

Copy link

Updated by Jeff Palmer over 12 years ago

I have applied this patch.

Afterwards, the smart-proxy shows the environment, it also returns a proper json list of the classes for the environment.
Additionally, the foreman UI now allows importing the puppet classes as expected.

Actions

Copy link