I'm attempting to provision a lucid32 box using drush-vagrant. I also have drupal-up installed with their basic Debian blueprints, so I'm not sure whether this issue is best suited to it or drush-vagrant as a whole.

Anyway, I can't seem to provision my box at all. Puppet provisioning fails with the following error:
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type config_file at /tmp/vagrant-puppet/modules-0/apt/manifests/init.pp:36 on node default.cc2.local

Upon tracking down config_file, I discover it's part of the common module. I follow the instructions and adding common to the import list, and am then able to provision the box. However, when the provisioner attempts to install drush, it hits the following issue:

err: /Stage[main]/Drush/Package[drush]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install drush' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Couldn't find package drush

After querying which repositories apt is pulling from, I discover that it's pulling from the *Debian* repositories as hard-coded in drush-vagrant's common module, and not leaving the Lucid box's apt settings in place.

I'm really not sure what to do about this. Would I be better off forking common without apt's custom repository settings, or is this a bug that you might be able to look into? Let me know if you need any more information.

Comments

helmo’s picture

helmo commented

Most work has been on drupal-up and aegir-up, which both use the debian base box.

The puppet code has probably just evolved towards usage on Debian.

Maybe we should consider using the same box for the default blueprint, otherwise it should probably be upgraded to the precise64 box.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Which blueprint are you using? The 'default' one that ships with drush-vagrant is the only one that uses lucid32, to my knowledge. But it doesn't attempt to install Drush via Puppet.

geoffreyr’s picture

geoffreyr commented

I was attempting to use the lucid32 box. I'll try using the Debian boxes that come with drupal-up again.

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented

Maybe we should consider using the same box for the default blueprint, otherwise it should probably be upgraded to the precise64 box.

Right... The initial reason for going with lucid32 is that it was the box most likely already downloaded, since it's the one listed in the Vagrant docs: http://vagrantup.com/v1/docs/boxes.html. I'm open to changing this though. Perhaps since we use the Debian one elsewhere, we should use it here too.

franskuipers’s picture

franskuipers commented

It seems that the puppet manifests in drupal-up & aegir-up are tailored on the Debian-box?

If that is true, I think it would be best to change out blueprint to the same box. Then people can inter-mix our default blueprint with the puppet manifests from these the drupal-up & aegir-up projects

ergonlogic’s picture

ergonlogic
he/him
Primary language English
Location Montréal, Québec 🇨🇦
commented
Status: Active » Fixed

Okay, switched defaults to use our custom Debian basebox, though I used the i386 box, since it's extremely difficult to debug problems running 64-bit boxes on CPUs that don't support 64-bit virtualization.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.