Puppet package needs ruby-hiera (unmapped dep)

Correct. This packaging bug was fixed in the debian repository just before the 3.3.0-1 release, with commit id 11a376f8348dfa2c254b19f7b29aec13940aeb92.

The "ruby-hiera" dependency was moved from the "puppetmaster-common" package to the "puppet-common" package. Previously, this was only needed by the puppet master, and the dependency was not moved to the correct place until 3.3.0-1

See also http://anonscm.debian.org/gitweb/?p=pkg-puppet/puppet.git;a=commitdiff;h=11a376f8348dfa2c254b19f7b29aec13940aeb92

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I can run "puppet apply" with an empty manifest and also a trivial manifest with a single static file defined, using puppet-common 3.2.4-2ubuntu2 on Saucy and without ruby-hiera installed. What exactly is the failure case here, please? What do you have in /etc/puppet/manifests/abstracts.pp:10? If you have something that specifically needs hiera, but puppet doesn't need hiera in all cases, then shouldn't this be at best a recommendation rather than a hard dependency?

We should certainly pick up the ruby-hiera dependency in puppet-common on the next merge from Debian for Trusty, as I see no reason to diverge from Debian on this.

But do we need Saucy fixed? If so, what is the justification, please?

Triaged for Trusty, since we should merge Debian's ruby-hiera dependency.

Hi,

I'm not using nothing specific to Hiera, but I don't know if some 3rd party module is (stdlib?).

There are the first 15 lines of the abstracts.pp file:

node 'debian-like-linux' {
 class { 'apt':
  always_apt_update => false,
  disable_keys => undef,
  proxy_host => false,
  proxy_port => '8080',
  purge_preferences_d => false,
  purge_sources_list => false,
  purge_sources_list_d => false,
 }
 sysctl { 'fs.file-max': value => '9999999' }
 sysctl { 'fs.inotify.max_user_watches': value => '100000' }
 sysctl { 'fs.nr_open': value => '9999999' }
 sysctl { 'net.core.netdev_max_backlog': value => '4096' }
 sysctl { 'net.core.rmem_max': value => '16777216' }
        ...
}

Puppet will need hiera when you apply a manifest containing any parameterized class, like the one in your example.

(and this is new functionality in puppet 3.x, it does not apply to puppet 2.7)

I vote for this to be fixed on Saucy.

I could simply fix +180 manifests to avoid Puppet trigget the automatic usage of Hiera...

Or I could simply go back to Raring and use the official Puppet packages and wait for them to release the official packages to Saucy as well (at the price of holding back early-adopters of this new Ubuntu release).

> Puppet will need hiera when you apply a manifest containing any parameterized class, like the one in your example.

Thanks. I'll test this and see if I can produce a failure case. Given that parameterized classes are pretty core functionality in puppet and just about every sane puppet deployment would probably use one, I guess it makes sense to make ruby-hiera as a dependency, and think that this should also be fixed in Saucy. Thank you for clarifying.

Failure case:

--->8---
class foo($content="abc") {
    file { '/tmp/foo': content => $content; }
}

class {foo:}
--->8---

"puppet apply" on a file of these contents produces errors of the style:

Error: Puppet::Parser::AST::Resource failed with error RuntimeError: Hiera terminus not supported without hiera library at /home/ubuntu/test.pp:5 on node foo

Installing ruby-hiera fixes it.

This was fixed in Trusty in 3.3.1-1ubuntu1, which picked up the Debian fix. For Saucy, I've prepared an SRU. I've also written a dep8 test that I've added to my Saucy SRU that I will submit to Debian.

Hello Herbert, or anyone else affected,

Accepted puppet into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/puppet/3.2.4-2ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Thank you Brian, it worked!

I've used the version 3.2.4-2ubuntu2.1 of puppet-common and it installed ruby-hiera as a dependency.

The verification of the Stable Release Update for puppet has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package puppet - 3.2.4-2ubuntu2.1

---------------
puppet (3.2.4-2ubuntu2.1) saucy; urgency=low

  * Add required dependency ruby-hiera, without which puppet does not work
    correctly in common cases (LP: #1242363).
  * d/tests/parameterised-class: dep8 test for failure case.
 -- Robie Basak <email address hidden> Fri, 29 Nov 2013 10:03:09 +0000