You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With facter 2.1.0 on Ubuntu Lucid, I get an error that looks like
Error: Error from DataBinding 'hiera' while looking up 'nginx::client_body_buffer_size': Undefined variable "::operatingsystemmajrelease"; Undefined variable "operatingsystemmajrelease" on node redacted.example.com
Since 7a67a9d, data/hiera.yaml specifies looking in operatingsystem/%{::operatingsystem}/%{::operatingsystemmajrelease} for data, but fails in this scenario because operatingsystemmajrelease is undefined.
Facter >= 2.2.0 sets a value for operatingsystemmajrelease in Ubuntu and shouldn't have this problem, but I haven't personally tested this configuration yet.
The most recent version of Facter available from Canonical is 2.1.0 in Utopic, so anyone with a vanilla Ubuntu installation (e.g., not using a very current puppetlabs package or rolling their own) is going to have this problem.
The text was updated successfully, but these errors were encountered:
Remove operatingsystemmajrelease from hieradata's hierarchy as it doesn't have a value
set on Ubuntu on anything lower than Facter 2.2. This means Ubuntu installations that
aren't running the most up to date Facter version would have compilation failures.
Fixesvoxpupuli#497
With facter 2.1.0 on Ubuntu Lucid, I get an error that looks like
Since 7a67a9d, data/hiera.yaml specifies looking in operatingsystem/%{::operatingsystem}/%{::operatingsystemmajrelease} for data, but fails in this scenario because operatingsystemmajrelease is undefined.
Facter >= 2.2.0 sets a value for operatingsystemmajrelease in Ubuntu and shouldn't have this problem, but I haven't personally tested this configuration yet.
The most recent version of Facter available from Canonical is 2.1.0 in Utopic, so anyone with a vanilla Ubuntu installation (e.g., not using a very current puppetlabs package or rolling their own) is going to have this problem.
The text was updated successfully, but these errors were encountered: