It seems that hosting_queue_runner is unhappy about something I did here. :)

err: /Stage[main]/Aegir::Queue_runner/Drush::Dl[hosting_queue_runner]/Exec[drush-dl-hosting_queue_runner]/returns: change from notrun to 0 failed: Working directory '/var/aegir/hostmaster-6.x-1.6/sites/aegir.anarcat.ath.cx' does not exist

The strange thing is that drush @hostmaster uli gives me a link in http://aegir.local/... i suspect this is the root of the problem.

Here's the complete log.

anarcat@marcos:aegir-up$ vagrant up
[hm] Box aegir-1.6 was not found. Fetching box from specified URL...
[vagrant] Downloading with Vagrant::Downloaders::HTTP...
[vagrant] Downloading box: http://ergonlogic.com/files/boxes/aegir-current.box
[vagrant] Extracting box...
[vagrant] Verifying box...
[vagrant] Cleaning up downloaded box...
[hm] Importing base box 'aegir-1.6'...
[hm] Matching MAC address for NAT networking...
[hm] Clearing any previously set forwarded ports...
[hm] Forwarding ports...
[hm] -- 22 => 2222 (adapter 1)
[hm] Creating shared folders metadata...
[hm] Clearing any previously set network interfaces...
[hm] Preparing network interfaces based on configuration...
[hm] Running any VM customizations...
[hm] Booting VM...
[hm] Waiting for VM to boot. This can take a few minutes.
[hm] VM booted and ready for use!
[hm] Configuring and enabling network interfaces...
[hm] Setting host name...
[hm] Mounting shared folders...
[hm] -- v-root: /vagrant
[hm] -- manifests: /tmp/vagrant-puppet/manifests
[hm] -- v-pp-m0: /tmp/vagrant-puppet/modules-0
[hm] Running provisioner: Vagrant::Provisioners::Puppet...
[hm] Running Puppet with /tmp/vagrant-puppet/manifests/hm.pp...
stdin: is not a tty
notice: Scope(Class[main]):

        Running Puppet manifests to install and/or update Aegir.

        This may take awhile, so please be patient.
        For more detail on the operations being run, edit settings.rb,
        and set 'verbose = 1'.

err: /Stage[main]/Aegir::Queue_runner/Drush::Dl[hosting_queue_runner]/Exec[drush-dl-hosting_queue_runner]/returns: change from notrun to 0 failed: Working directory '/var/aegir/hostmaster-6.x-1.6/sites/aegir.anarcat.ath.cx' does not exist

notice: /Stage[main]/Aegir::Queue_runner/File[hosting-queue-runner init script]: Dependency Exec[drush-dl-hosting_queue_runner] has failures: true

warning: /Stage[main]/Aegir::Queue_runner/File[hosting-queue-runner init script]: Skipping because of failed dependencies
notice: /Stage[main]/Aegir::Queue_runner/Drush::En[hosting_queue_runner]/Exec[drush-en-hosting_queue_runner]: Dependency Exec[drush-dl-hosting_queue_runner] has failures: true
warning: /Stage[main]/Aegir::Queue_runner/Drush::En[hosting_queue_runner]/Exec[drush-en-hosting_queue_runner]: Skipping because of failed dependencies
notice: /Stage[main]/Aegir::Queue_runner/Service[hosting-queue-runner]: Dependency Exec[drush-dl-hosting_queue_runner] has failures: true
warning: /Stage[main]/Aegir::Queue_runner/Service[hosting-queue-runner]: Skipping because of failed dependencies
notice: Finished catalog run in 9.51 seconds

Comments

ergonlogic’s picture

Hmm, interesting. Have you tried setting the hostname in settings.rb, and/or $aegir_hostmaster_url in manifests/hm.pp?

anarcat’s picture

No. I assumed things were magic. :P

ergonlogic’s picture

I believe this stems from how Facter determines FQDN in Debian. Apparently it tries to guess, rather than looking at 'hostname -f'.

In the long-run, http://drupalcode.org/project/aegir-up.git/blob/HEAD:/Vagrantfile#l35 should fix it (i.e., magic). But it'll have to wait for the new feature (https://github.com/mitchellh/vagrant/pull/753) to land in a stable release of Vagrant. It looks like it'll make it into 1.0.

In the mean time, setting $aegir_hostmaster_url in manifests/hm.pp should work, assuming the Facter/FQDN issue is at the root of this. Please let me know if that works for you.

ergonlogic’s picture

Oh, BTW, running 'vagrant provision' once you've made any changes will run the Puppet manifests again, and should be sufficient to get the queue_runner running.

anarcat’s picture

Indeed, that fixes the problem.

ergonlogic’s picture

Status: Active » Fixed

OK, so I'll mark this as fixed, since we have a simple work-around, the solution is upstream, and we've already got the code necessary to take advantage of it once it lands.

ergonlogic’s picture

Version: » 6.x-1.6-beta1

Actually, really fixed now. The default hm.pp now set the front end URL by default, so user's should see this anymore.

Status: Fixed » Closed (fixed)

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