I read up on juju-local, and tried this in a clean wily amd64 cloud
image:
sudo apt install -y juju-local
juju init
juju switch local
juju bootstrap
I'm not entirely sure what I'm supposed to do now; there is a "juju
machine add" command, but this doesn't accept custom user data. But it
sounds like the above user data will already be created by juju itself?
So I ran
sudo juju machine add
and get
$ juju status
environment: local
available-version: 1.24.7
machines:
"0":
agent-state: started
agent-version: 1.24.6.1
dns-name: localhost
instance-id: localhost
series: wily
state-server-member-status: has-vote
"1":
instance-id: pending
series: trusty
services: {}
But there's no new machine anywhere, just the template from
bootstrapping:
$ sudo lxc-ls -f
NAME STATE IPV4 IPV6 GROUPS AUTOSTART
----------------------------------------------------------------
juju-trusty-lxc-template STOPPED - - - NO
... and now I just realize that this is trusty, not wily. So this should at
least work, no? In trusty we don't have systemd yet.
/var/log/juju-ubuntu-local/all-machines.log just spits out a series of
machine-0: 2015-10-28 08:27:55 ERROR juju.worker.diskmanager
lsblk.go:116 error checking if "fd0" is in use: open /dev/fd0: no such
device or address
but doesn't otherwise seem to do anything.
For completeness I retried the above steps with wily, and set "default-
series: wily" in ~/.juju/environments.yaml before bootstrap. But now
after bootstrap it doesn't even build a template container,
/var/lib/lxc/ stays empty and "sudo tail -f /var/log/juju-ubuntu-
local/*" again just shows a series of these /dev/fd0 checks. I gave up
after 10 minutes.
While these look like bugs, they look unrelated to this issue. Can you
please tell me how this bug can be reproduced starting from a fresh wily
install?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509747
Title:
Intermittent lxc failures on wily, juju-template-restart.service race
condition
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1509747/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
