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
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.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Branch linked: lp:ubuntu/saucy-proposed/puppet
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs ruby-hiera (unmapped dep)
To manage notification
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://wi
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.
** Description changed:
+ [Impact]
+
+ puppet does not work correctly in a very common use case
** Changed in: puppet (Ubuntu Saucy)
Assignee: (unassigned) => Robie Basak (racb)
** Changed in: puppet (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
h
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 wit
> 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
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 bac
Puppet will need hiera when you apply a manifest containing any
parameterized class, like the one in your example.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppe
(and this is new functionality in puppet 3.x, it does not apply to
puppet 2.7)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs ruby-hiera (unmapped
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 => und
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 failu
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 b
14 matches
Mail list logo
