Project

General

Profile

Actions

Bug #1855

closed

Include foreman's default port in foreman_url

Added by Andy Edmonds about 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Foreman version: 1.0.1
Puppet version: 2.7.19

By default the foreman-installer runs foreman on port 3000 however the foreman module's params.pp sets foremanurl to _only the FQDN of the host and not the port… this then has a knock on effect to any of the file templates, including /etc/puppet/node.rb

Actions #1

Updated by Sam Kottler about 12 years ago

  • Status changed from New to Pending

There is a related discussion in the pull request, but basically we make some assumptions when you use the installer right now. One of them is that Foreman runs on port 80 since that's the port that the vhost created by the installer listens on. There are plans to improve the installer and this is definitely on the list of things that should be parameterized.

I'm marking this issue pending because it relies on some other issues getting resolved, but I want to circle back to ensure this is taken care of in the next major release of the installer.

Actions #2

Updated by Ewoud Kohl van Wijngaarden about 11 years ago

  • Status changed from Pending to Resolved
  • % Done changed from 0 to 100

I think all instances of url not really being an URL are fixed. I know node.rb is fixed so please re-open if there are still any instances left.

Actions

Also available in: Atom PDF