Facter 1.6.9 complains about "No LSB modules are available."

[Andreas Ntaflos]

Hi,

it seems that Facter 1.6.9 complains that "No LSB modules are
available." on every run. This is on Ubuntu 10.04 and 12.04, probably
others as well. This message (on stderr) usually comes from calling
"lsb_release -v" when no additional LSB modules are installed. Facter
apparently calls "lsb_release -v -s" in facter/lsbrelease.rb.

This is neither fatal nor problematic, but very annoying because a
typical puppet run used to be silent. Now my Cron mails are full of "No
LSB modules are available."

I also don't quite understand the purpose of this lsbrelease fact. At
least on a typical Ubuntu system "lsb_release -v -s" doesn't output
anything other than this useless message. What information is supposed
to be encoded in the lsbrelease fact? Is that fact even needed?

Thanks,

Andreas

[Andreas N]

On Friday, May 18, 2012 1:28:43 PM UTC+2, Andreas N wrote:

it seems that Facter 1.6.9 complains that "No LSB modules are
available." on every run. This is on Ubuntu 10.04 and 12.04, probably
others as well. This message (on stderr) usually comes from calling
"lsb_release -v" when no additional LSB modules are installed. Facter
apparently calls "lsb_release -v -s" in facter/lsbrelease.rb.

 

If anyone's interested, I've opened a bug report about this here: http://projects.puppetlabs.com/issues/14582

Andreas

[Stig Sandbeck Mathisen]

Andreas Ntaflos <da...@pseudoterminal.org> writes:

> it seems that Facter 1.6.9 complains that "No LSB modules are
> available." on every run. This is on Ubuntu 10.04 and 12.04, probably
> others as well. This message (on stderr) usually comes from calling
> "lsb_release -v" when no additional LSB modules are installed. Facter
> apparently calls "lsb_release -v -s" in facter/lsbrelease.rb.

> I also don't quite understand the purpose of this lsbrelease fact. At
> least on a typical Ubuntu system "lsb_release -v -s" doesn't output
> anything other than this useless message. What information is supposed
> to be encoded in the lsbrelease fact? Is that fact even needed?

It describes which of the Linux Standards Base specifications the system
conforms to.

The format is a colon separated list of strings. With "lsb-core" (and
"lsb-security") installed, the value looks like this:

core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch: \
core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch: \
core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch: \
security-4.0-amd64:security-4.0-noarch:security-4.1-amd64: \
security-4.1-noarch

--
Stig Sandbeck Mathisen