-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
When starting the controller for the first time, I get the 2 errors below.
The first error seems to be fixed here: https://bugzilla.mozilla.org/show_bug.cgi?id=1024938
I am not sure if the second error is related, but when the controller and compute nodes are up, the page at 192.168.42.11 is unreachable.
NB: I am on a windows host, I'll try the install procedure on MacOS and Linux hosts asap but I have the feeling those are not OS-related errors.
$ vagrant up controller --provision(...)
==> controller: notice: /Stage[main]/Ip_masq/Exec[ip_forward]/returns: executed
successfully
==> controller: err: /Stage[main]/Base_packages/Exec[apt_get_update]/returns: ch
ange from notrun to 0 failed: /usr/bin/apt-get -y update returned 100 instead of
one of [0] at /tmp/vagrant-puppet-2/manifests/nodes.pp:27
==> controller: notice: /Stage[main]/Ovs_2/Package[build-essential]: Dependency
Exec[apt_get_update] has failures: true
==> controller: warning: /Stage[main]/Ovs_2/Package[build-essential]: Skipping b
ecause of failed dependencies
(...)
==> controller: warning: /Stage[main]/Firewall::Linux::Debian/Service[iptables-p
ersistent]: Skipping because of failed dependencies
==> controller: err: /Stage[main]//Node[controller]/File[/home/stack/devstack/lo
cal.sh]/ensure: change from absent to file failed: Could not set 'file on ensure
: No such file or directory - /home/stack/devstack/local.sh.puppettmp_3827 at /t
mp/vagrant-puppet-2/manifests/nodes/controller.pp:34
==> controller: notice: /Stage[main]//Node[controller]/Notify[running_devstack]:
Dependency Exec[apt_get_update] has failures: true
Full stack trace: https://gist.github.com/banzo/7f9ec25543cbbbf35859
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels