Project

General

Custom queries

Profile

Actions
Copy link

Bug #33320

closed

Refer to FQDN instead of "Foreman server" in SmartProxy registration error messages

Added by William Clark over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
William Clark
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1994669
Pull request:
https://github.com/theforeman/puppet-foreman/pull/988
Fixed in Releases:
Foreman - 3.1.0
Found in Releases:
Red Hat JIRA:

Description

Foreman server is somewhat ambiguous as it can be branded differently in downstream builds or the user could have multiple Foreman servers. Using the FQDN always will improve clarity

#1

Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman/pull/988 added
#2

Updated by The Foreman Bot over 3 years ago

  • Fixed in Releases 3.1.0 added
#3

Updated by William Clark over 3 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF