Bug #9449
closed
foreman-installer fails if lsb-release is missing on the system
Added by Phillip Schichtel about 9 years ago.
Updated almost 6 years ago.
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.
- Project changed from Foreman to Installer
- Category set to Foreman modules
- Status changed from New to Assigned
- Priority changed from Normal to Low
- Assignee set to Anonymous
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.
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.
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/puppet-foreman/pull/296 added
- Pull request deleted (
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- translation missing: en.field_release set to 28
Also available in: Atom
PDF
Updated by Anonymous 
Updated by 
Updated by