Project

General

Profile

Bug #9449

foreman-installer fails if lsb-release is missing on the system

Added by Phillip Schichtel over 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
Foreman modules
Target version:
1.8.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman/pull/296
Fixed in Releases:
Found in Releases:
Foreman - 1.7.2

Description

I faced the problem on my minimal wheezy installation.
The lsb facts are missing on the system as the lsb-release package is not included in the debian base installation.

Associated revisions

Revision 61cab9cf (diff)
Added by Michael Moll over 7 years ago

fixes #9449 - drop usage of lsb facts

Revision e94db974 (diff)
Added by Michael Moll over 7 years ago

refs #9449 - drop usage of lsb fact

Closes GH-154

History

#1 Updated by Anonymous over 7 years ago

  • Assignee set to Anonymous
  • Project changed from Foreman to Installer
  • Category set to Foreman modules
  • Status changed from New to Assigned
  • Priority changed from Normal to Low

This is due some few usages of $::lsbdistcodename in theforeman-foreman (and theoretically $::lsbmajdistrelease in theforeman-foreman_proxy. However, at least one usage can't be deleted and it's questionable for some others, so maybe it's just better to include lsb packages in the installation docs.

#3 Updated by Anonymous over 7 years ago

That issue is about something else. I get that a dependency of foreman-installer on lsb-release would solve the problem from a users' point of view.

#4 Updated by Anonymous over 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman/pull/296 added
  • Pull request deleted ()

#5 Updated by Anonymous over 7 years ago

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

#6 Updated by Dominic Cleal over 7 years ago

  • Legacy Backlogs Release (now unused) set to 28

Also available in: Atom PDF