Augeas support on my Vagrant machine?

Question

I'm trying to getting support for augeas on my Vagrant machine.

I tried to install some package with these directives:

package { "augeas-tools":   ensure => installed }
package { "libaugeas-dev":  ensure => installed }
package { "libaugeas-ruby": ensure => installed }

When i try to use augeas on my manifests, after the vm boot i receive this error:

err: Could not find a suitable provider for augeas

I'm using the precise32 official box with Vagrant 1.0.3.

Vagrant 1.0.3 has ruby 1.8.7 and puppet 2.7.14

$ ruby -v
$ ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
$ puppet help
$ Puppet v2.7.14

This is my little manifest with php class, included after apache class, mysql and other classes tested separately. All things works correctly excepting for the augeas command.

class php {

    exec { "apt-update":
        command     => "/usr/bin/apt-get update",
        refreshonly => true;
    }

    package { "augeas-tools":   ensure => installed }
    package { "libaugeas-dev":  ensure => installed }
    package { "libaugeas-ruby": ensure => installed }

    package { "php5":               ensure => installed }
    package { "php5-cli":           ensure => installed }
    package { "php5-xdebug":        ensure => installed }
    package { "php5-curl":          ensure => installed }
    package { "php5-intl":          ensure => installed }
    package { "php5-imap":          ensure => installed }
    package { "php5-mcrypt":        ensure => installed }
    package { "php5-imagick":       ensure => installed }
    package { "php5-sqlite":        ensure => installed }
    package { "php5-gd":            ensure => installed }
    package { "php-apc":            ensure => installed }

    package { 
        "libapache2-mod-php5" : 
            ensure => installed,
            require => Package["php5"]
    }

    augeas { "php-cli":
        require =>  [
                        Package["php5"],
                        Package["augeas-tools"],
                        Package["libaugeas-dev"],
                        Package["libaugeas-ruby"],
                    ],
        context => "/etc/php5/cli/php.ini",
        changes => [
            "set date.timezone Europe/Rome",
            "set short_open_tag Off",
        ];
    }

    augeas { "php-apache":
        require =>  [
                        Package["php5"],
                        Package["augeas-tools"],
                        Package["libaugeas-dev"],
                        Package["libaugeas-ruby"],
                    ],
        context => "/etc/php5/apache2/php.ini",
        changes => [
            "set date.timezone Europe/Rome",
            "set short_open_tag Off",
        ];
    }

}

After installation of packages, logging in the vagrant machine with "vagrant ssh", i launch:

vagrant@precise32:~$ ruby -raugeas -e "puts Augeas.open"
#<Augeas:0xb77a3598>

Thanks in advance!

Which version of puppet are you using, and what does your puppet code look like? — raphink, Jun 05 '12 at 11:15
I added the information you've requested. I hope this helps... — Francesco Casula, Jun 05 '12 at 12:10

score 8 · Answer 1 · edited Dec 27 '12 at 07:50

8

I added the following to my Vagrantfile and it augeas started working.

Before declaring puppet provisioner add the following line, if on ubuntu:

config.vm.provision :shell, :inline => "sudo apt-get update && sudo apt-get install puppet -y"

This will update your apt packages and then update puppet client whose latest version already has a fix.

edited Dec 27 '12 at 07:50

Berkay Turancı

3,373
4
32
45

answered Dec 27 '12 at 07:18

user1931475

81
1
1

score 7 · Answer 2 · answered Jun 05 '12 at 18:38

It turns out that this wasn't fixed in bug #6907 that I referenced in my other answer. That fix only worked for Puppet providers that depended on commands that were then supplied during the run.

For the Augeas provider, it uses an internal Puppet called "features" to check if the ruby-augeas library is available or not. Features are only being checked once and the results cached, so even after installing the library, this meant the feature still evaluated to false.

I filed this upstream as bug #14822 and have sent a pull request with a fix. Testing with the patch, I now get this successful run:

notice: /Stage[main]//Package[ruby-augeas]/ensure: created
notice: /Stage[main]//Augeas[test]/returns: executed successfully

I'm not familiar with Vagrant, but I think you'll need to find a workaround to install the libaugeas-ruby package before the Puppet run in the meantime.

I'm sure this is the way to find the solution, but not the solution itself. Vote Up! :) — Francesco Casula, Jun 06 '12 at 07:45

score 1 · Answer 3 · answered Jun 05 '12 at 12:37

1

On Puppet 2.7.14, this should work as the dependencies for providers will only be evaluated when they're needed - i.e. when Puppet needs to run those Augeas resources.

Without the full Puppet log file to confirm, I suspect that it's because you're missing explicit dependencies between the Augeas package(s) and the Augeas resources that need them. Remember, listing the resources in the manifest in that order doesn't mean Puppet executes it that way.

You could either add requires parameters to every Augeas resource:

augeas { "php-cli":
    require => [ Package["php5"], Package["libaugeas-ruby"] ],
    # ...
}

Or use the chaining syntax to automatically make every Augeas resource depend on a package. Add this on a line inside the class, but not inside any resource:

Package["libaugeas-ruby"] -> Augeas <| |>

answered Jun 05 '12 at 12:37

Dominic Cleal

3,205
19
22

I've added all the requires to the augeas directive but the problem still persist. Note: i've edited the main question with the new code including new requires. Thanks for you reply... – Francesco Casula Jun 05 '12 at 13:54
Ok, could you try running this command after libaugeas-ruby is installed? `ruby -raugeas -e "puts Augeas.open"` – Dominic Cleal Jun 05 '12 at 14:03
added to the main question: # – Francesco Casula Jun 05 '12 at 14:45
The stuff mentioned in my other answer's been merged, so as of 2.7.20 or 3.0.2 you'll be able to do this. – Dominic Cleal Dec 04 '12 at 22:33

Slava Semushin · Answer 4 · 2013-07-19T15:07:42.467

After reading answer from @m0dlx I inspect /home/vagrant/postinstall.sh file and found that Vagrant uses own copy of Ruby:

# The base path to the Ruby used for the Chef and Puppet gems ruby_home="/opt/vagrant_ruby"

After that I find file augeas.rb at /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/puppet-2.7.19/lib/puppet/provider/augeas/augeas.rb and edit it, by changing line

confine :true => Puppet.features.augeas?

to

confine :true => :augeas

(Shortly speaking I partially apply patch from @m0dlx.)

After that this error is gone.

Augeas support on my Vagrant machine?

4 Answers4