Discussion:
LXD Bootstrap
(too old to reply)
Tom Barber
2016-02-26 14:42:51 UTC
Permalink
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS

I'd read on a few posts about the requirement for LXD beta2 because of API
incompatibilities so I found the deb's and installed them.

Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?

Cheers


Tom
Tom Barber
2016-02-26 14:44:55 UTC
Permalink
Sorry forgot to mention, Juju was built from trunk this morning.

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS
I'd read on a few posts about the requirement for LXD beta2 because of API
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Cheers
Tom
Tom Barber
2016-02-26 16:02:34 UTC
Permalink
I've tried rolling back on Juju but still can't find a combination, its not
the end of the world, I was curious. Anyway, if I lxc exec into the machine
I find SSH is down which sorta explains the connection failure:

cloud init runs but then seems to get no futher

https://gist.github.com/buggtb/c5785a74a1124cdc7bb7 <- bootstrap debug
output.



--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Sorry forgot to mention, Juju was built from trunk this morning.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS
I'd read on a few posts about the requirement for LXD beta2 because of
API incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Cheers
Tom
Tom Barber
2016-02-26 17:20:50 UTC
Permalink
On Jorge's advice I rolled all the way back to the juju 1.26 beta 2 tag,
lxd beta 2 and xenial and still it fails with connection refused.... weird.
Post by Tom Barber
I've tried rolling back on Juju but still can't find a combination, its
not the end of the world, I was curious. Anyway, if I lxc exec into the
cloud init runs but then seems to get no futher
https://gist.github.com/buggtb/c5785a74a1124cdc7bb7 <- bootstrap debug
output.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Sorry forgot to mention, Juju was built from trunk this morning.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS
I'd read on a few posts about the requirement for LXD beta2 because of
API incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Cheers
Tom
Serge E. Hallyn
2016-02-26 20:02:39 UTC
Permalink
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and ZFS
I'd read on a few posts about the requirement for LXD beta2 because of API
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Hi Tom,

Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.

-serge
--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-26 20:08:42 UTC
Permalink
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.

Tom
Post by Serge E. Hallyn
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD and
ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because of
API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
John Meinel
2016-02-27 11:56:20 UTC
Permalink
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)

John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD
and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because of
API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 12:09:53 UTC
Permalink
Thanks John

That was sort of my thinking too. But it's not a groups thing that I can
see. Same issue as root or as unprivileged users.


***@tomsdevbox:~$ groups

bugg lxd

***@tomsdevbox:~$ lxd --version
2.0.0.beta2


***@tomsdevbox:~$ lxc --version
2.0.0.beta2


at which point the bootstrap trust image starts fine, and i can

lxc exec juju-...... /bin/bash

into it. But sshd isn't running which explains why the connection refused
error appears.

Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD
and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because of
API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails with
connection refused when trying to SSH in. Something stupid i'm doing or
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
John Meinel
2016-02-27 12:14:17 UTC
Permalink
What image did you import into LXD? You should use something like:
lxd-images import ubuntu trusty --alias ubuntu-trusty

(substitute xenial/wily etc as relevant.)

That looks like you are using an image from linuxcontainers.org which is
very different from the ones built by cloud-images.ubuntu.com

John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I can
see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection refused
error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD
and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because
of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails
with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm doing
or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 12:17:00 UTC
Permalink
I used:

lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty

Which I stole from Jorge's blog.

***@tomsdevbox:~$ lxc image list
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server (20160222)
| x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+


--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org which is
very different from the ones built by cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I can
see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection refused
error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju LXD
and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because
of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails
with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm doing
or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
John Meinel
2016-02-27 12:55:30 UTC
Permalink
That does seem correct. But I thought cloud-images run openssh by default.
So that seems surprising.

What happens if you just do "lxc create" to spawn an instance instead of
using Juju?

John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server (20160222)
| x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org which is
very different from the ones built by cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I can
see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the daily
grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju
LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2 because
of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails
with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
John Meinel
2016-02-27 12:56:14 UTC
Permalink
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.

John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by default.
So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead of
using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server (20160222)
| x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org which
is very different from the ones built by cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I
can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju
LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap fails
with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 13:01:49 UTC
Permalink
***@tomsdevbox:~$ lxc launch ubuntu-trusty my-test-container
Creating my-test-container

Starting my-test-container
***@tomsdevbox:~$
***@tomsdevbox:~$ lxc exec my-test-container /bin/bas
***@tomsdevbox:~$ lxc exec my-test-container /bin/bash
***@my-test-container:~# ps axu |grep ssh
root 1800 0.0 0.0 61380 5408 ? Ss 12:59 0:00
/usr/sbin/sshd -D
root 1993 0.0 0.0 8868 784 ? S+ 13:00 0:00 grep
--color=auto ssh
***@my-test-container:~#


Seems alright if I just launch an instance. Also inside the juju
bootstrapped containers you can see some ssh related stuff where it sets
keys etc in the logs so its logging in and doing something.

I've compiled everything from 1.26 alpha2 to master so I'll happily wipe it
clean and try the branch! ;)

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by
default. So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead of
using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server
(20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org which
is very different from the ones built by cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I
can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was the
current incompatibilities. What you're seeing looks more like you aren't in
the "LXD" group, or you didn't refresh your groups after installing LXD.
(newgrp lxd)
John
=:->
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju
LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap
fails with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 13:14:29 UTC
Permalink
Okay checked out and tested but no dice currently:

***@tomsdevbox:~$ juju --version
2.0-beta2-xenial-amd64



***@tomsdevbox:~/work/src/github.com/juju/juju$ lxc --version
2.0.0.beta4


***@tomsdevbox:~/work/src/github.com/juju/juju$ lxd --version
2.0.0.beta4


***@tomsdevbox:~/work/src/github.com/juju/juju$ juju bootstrap
mycontroller lxd --debug --upload-tools
2016-02-27 13:09:10 INFO juju.cmd supercommand.go:59 running juju
[2.0-beta2 gc go1.6]
2016-02-27 13:09:10 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
provider name
2016-02-27 13:09:10 INFO cmd cmd.go:141 no credentials found, checking
environment
2016-02-27 13:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:340 preparing
controller with config: map[type:lxd name:mycontroller]
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:57 loading
LXD client config from "/home/bugg/.config/lxc/juju-mycontroller"
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:64 using
LXD remote "local"
2016-02-27 13:09:14 ERROR cmd supercommand.go:448 invalid config: json:
cannot unmarshal string into Go value of type int
***@tomsdevbox:~/work/src/github.com/juju/juju$



--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Creating my-test-container
Starting my-test-container
root 1800 0.0 0.0 61380 5408 ? Ss 12:59 0:00
/usr/sbin/sshd -D
root 1993 0.0 0.0 8868 784 ? S+ 13:00 0:00 grep
--color=auto ssh
Seems alright if I just launch an instance. Also inside the juju
bootstrapped containers you can see some ssh related stuff where it sets
keys etc in the logs so its logging in and doing something.
I've compiled everything from 1.26 alpha2 to master so I'll happily wipe
it clean and try the branch! ;)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by
default. So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead of
using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server
(20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org which
is very different from the ones built by cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I
can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was
the current incompatibilities. What you're seeing looks more like you
aren't in the "LXD" group, or you didn't refresh your groups after
installing LXD. (newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber <
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about Juju
LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap
fails with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 13:20:22 UTC
Permalink
The only thing I can tell you about this box that might different from the
test beds you guys use was it was a dist upgrade from wily because that was
the latest image the hosts had.

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
2.0-beta2-xenial-amd64
2.0.0.beta4
2.0.0.beta4
mycontroller lxd --debug --upload-tools
2016-02-27 13:09:10 INFO juju.cmd supercommand.go:59 running juju
[2.0-beta2 gc go1.6]
2016-02-27 13:09:10 INFO cmd cmd.go:141 cloud "lxd" not found, trying as a
provider name
2016-02-27 13:09:10 INFO cmd cmd.go:141 no credentials found, checking
environment
2016-02-27 13:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:340
preparing controller with config: map[type:lxd name:mycontroller]
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:57
loading LXD client config from "/home/bugg/.config/lxc/juju-mycontroller"
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:64 using
LXD remote "local"
cannot unmarshal string into Go value of type int
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Creating my-test-container
Starting my-test-container
root 1800 0.0 0.0 61380 5408 ? Ss 12:59 0:00
/usr/sbin/sshd -D
root 1993 0.0 0.0 8868 784 ? S+ 13:00 0:00 grep
--color=auto ssh
Seems alright if I just launch an instance. Also inside the juju
bootstrapped containers you can see some ssh related stuff where it sets
keys etc in the logs so its logging in and doing something.
I've compiled everything from 1.26 alpha2 to master so I'll happily wipe
it clean and try the branch! ;)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by
default. So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead
of using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server
(20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org
which is very different from the ones built by
cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that I
can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was
the current incompatibilities. What you're seeing looks more like you
aren't in the "LXD" group, or you didn't refresh your groups after
installing LXD. (newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber <
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about
Juju LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap
fails with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new
feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
John Meinel
2016-02-27 13:25:53 UTC
Permalink
You're running on Xenial but you don't have a Xenial image listed. Maybe
its launching a Trusty image for bootstrap? I thought it always tried to
match the host version.
I assume you did:
cd $GOPATH/src/github.com/juju/juju
git checkout lxd-container-type
godeps -u dependencies.tsv
go install ./...
$GOPATH/bin/juju --version
etc.

That particular "cannot unmarshal string into Go value" is exactly what I
would expect to see if you are using the wrong version of Juju with the
wrong version of LXD. LXD changed a few fields from ints to strings.
(2.0.0beta3 had an Architecture int, which they changed to Architecture
string.)
The unmarshall failure sounds like you're using 2.0.0beta4 for LXD, but a
version of juju that was compiled against 2.0.0beta3 bindings.

John
=:->
Post by Tom Barber
The only thing I can tell you about this box that might different from the
test beds you guys use was it was a dist upgrade from wily because that was
the latest image the hosts had.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
2.0-beta2-xenial-amd64
2.0.0.beta4
2.0.0.beta4
mycontroller lxd --debug --upload-tools
2016-02-27 13:09:10 INFO juju.cmd supercommand.go:59 running juju
[2.0-beta2 gc go1.6]
2016-02-27 13:09:10 INFO cmd cmd.go:141 cloud "lxd" not found, trying as
a provider name
2016-02-27 13:09:10 INFO cmd cmd.go:141 no credentials found, checking
environment
2016-02-27 13:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:340
preparing controller with config: map[type:lxd name:mycontroller]
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:57
loading LXD client config from "/home/bugg/.config/lxc/juju-mycontroller"
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:64 using
LXD remote "local"
cannot unmarshal string into Go value of type int
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Creating my-test-container
Starting my-test-container
root 1800 0.0 0.0 61380 5408 ? Ss 12:59 0:00
/usr/sbin/sshd -D
root 1993 0.0 0.0 8868 784 ? S+ 13:00 0:00 grep
--color=auto ssh
Seems alright if I just launch an instance. Also inside the juju
bootstrapped containers you can see some ssh related stuff where it sets
keys etc in the logs so its logging in and doing something.
I've compiled everything from 1.26 alpha2 to master so I'll happily wipe
it clean and try the branch! ;)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
BTW, if you are comfortable running Juju from master, there is a branch
"lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by
default. So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead
of using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server
(20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org
which is very different from the ones built by
cloud-images.ubuntu.com
John
=:->
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that
I can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was
the current incompatibilities. What you're seeing looks more like you
aren't in the "LXD" group, or you didn't refresh your groups after
installing LXD. (newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber <
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about
Juju LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap
fails with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid i'm
doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new
feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 13:33:21 UTC
Permalink
Yeah I did run the build like that, so not sure whats going on there. lxc
launch still works fine.

The box is empty except this hacking so I might flatten it and reinstall
wily and upgrade through it again, see if a clean slate does the trick. LXD
looks fine though, so I'm not sure what I'm doing wrong.

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
You're running on Xenial but you don't have a Xenial image listed. Maybe
its launching a Trusty image for bootstrap? I thought it always tried to
match the host version.
cd $GOPATH/src/github.com/juju/juju
git checkout lxd-container-type
godeps -u dependencies.tsv
go install ./...
$GOPATH/bin/juju --version
etc.
That particular "cannot unmarshal string into Go value" is exactly what I
would expect to see if you are using the wrong version of Juju with the
wrong version of LXD. LXD changed a few fields from ints to strings.
(2.0.0beta3 had an Architecture int, which they changed to Architecture
string.)
The unmarshall failure sounds like you're using 2.0.0beta4 for LXD, but a
version of juju that was compiled against 2.0.0beta3 bindings.
John
=:->
Post by Tom Barber
The only thing I can tell you about this box that might different from
the test beds you guys use was it was a dist upgrade from wily because that
was the latest image the hosts had.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
2.0-beta2-xenial-amd64
2.0.0.beta4
2.0.0.beta4
mycontroller lxd --debug --upload-tools
2016-02-27 13:09:10 INFO juju.cmd supercommand.go:59 running juju
[2.0-beta2 gc go1.6]
2016-02-27 13:09:10 INFO cmd cmd.go:141 cloud "lxd" not found, trying as
a provider name
2016-02-27 13:09:10 INFO cmd cmd.go:141 no credentials found, checking
environment
2016-02-27 13:09:10 DEBUG juju.cmd.juju.commands bootstrap.go:340
preparing controller with config: map[type:lxd name:mycontroller]
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:57
loading LXD client config from "/home/bugg/.config/lxc/juju-mycontroller"
2016-02-27 13:09:14 DEBUG juju.container.lxd.lxdclient client.go:64
using LXD remote "local"
cannot unmarshal string into Go value of type int
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Creating my-test-container
Starting my-test-container
root 1800 0.0 0.0 61380 5408 ? Ss 12:59 0:00
/usr/sbin/sshd -D
root 1993 0.0 0.0 8868 784 ? S+ 13:00 0:00 grep
--color=auto ssh
Seems alright if I just launch an instance. Also inside the juju
bootstrapped containers you can see some ssh related stuff where it sets
keys etc in the logs so its logging in and doing something.
I've compiled everything from 1.26 alpha2 to master so I'll happily
wipe it clean and try the branch! ;)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
BTW, if you are comfortable running Juju from master, there is a
branch "lxd-container-type" which should support LXD 2.0.0~beta4 (I have it
running here), and I'd be happy to get feedback on it.
John
=:->
Post by John Meinel
That does seem correct. But I thought cloud-images run openssh by
default. So that seems surprising.
What happens if you just do "lxc create" to spawn an instance instead
of using Juju?
John
=:->
Post by Tom Barber
lxd-images import ubuntu trusty amd64 --sync --alias ubuntu-trusty
Which I stole from Jorge's blog.
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION
| ARCH | SIZE | UPLOAD DATE |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
| ubuntu-precise | 4029ee764a39 | no | Ubuntu 12.04 LTS server
(20160222) | x86_64 | 155.25MB | Feb 26, 2016 at 5:12pm (CET) |
| ubuntu-trusty | 510c27eb5e30 | no | Ubuntu 14.04 LTS server
(20160222) | x86_64 | 118.51MB | Feb 26, 2016 at 5:13pm (CET) |
| ubuntu-wily | fb2cf6ab4af1 | no | Ubuntu 15.10 server
(20160222) | x86_64 | 154.27MB | Feb 26, 2016 at 5:12pm (CET) |
+----------------+--------------+--------+------------------------------------+--------+----------+------------------------------+
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by John Meinel
lxd-images import ubuntu trusty --alias ubuntu-trusty
(substitute xenial/wily etc as relevant.)
That looks like you are using an image from linuxcontainers.org
which is very different from the ones built by
cloud-images.ubuntu.com
John
=:->
On Sat, Feb 27, 2016 at 4:09 PM, Tom Barber <
Post by Tom Barber
Thanks John
That was sort of my thinking too. But it's not a groups thing that
I can see. Same issue as root or as unprivileged users.
bugg lxd
2.0.0.beta2
2.0.0.beta2
at which point the bootstrap trust image starts fine, and i can
lxc exec juju-...... /bin/bash
into it. But sshd isn't running which explains why the connection
refused error appears.
Tom
Post by John Meinel
Connection refused isn't the error you would be getting if it was
the current incompatibilities. What you're seeing looks more like you
aren't in the "LXD" group, or you didn't refresh your groups after
installing LXD. (newgrp lxd)
John
=:->
On Sat, Feb 27, 2016 at 12:08 AM, Tom Barber <
Post by Tom Barber
No worries Serge I was just some Friday fun to get me out of the
daily grind. Thanks for the update.
Tom
Post by Tom Barber
Post by Tom Barber
Afternoon, got bored decided to try Jorge's blog post about
Juju LXD and ZFS
Post by Tom Barber
I'd read on a few posts about the requirement for LXD beta2
because of API
Post by Tom Barber
incompatibilities so I found the deb's and installed them.
Its up and running and images start fine, but juju bootstrap
fails with
Post by Tom Barber
connection refused when trying to SSH in. Something stupid
i'm doing or
Post by Tom Barber
just broke for now?
Hi Tom,
Yeah it's just broken for now. It will be fixed when a new
feature branch
is merged, which I think is supposed to happen on or before Monday.
-serge
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-27 14:43:08 UTC
Permalink
Okay, evolution on a theme, clean install, compiled the new version and
added lxd and checked my user now I get:

016-02-27 14:40:51 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 10.0.3.94 failed: ssh: connect to host 10.0.3.94 port 22:
Connection refused
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 127.0.0.1 failed: Permission denied (publickey,password).
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for fe80::216:3eff:fe6e:86b5 failed: ssh: connect to host
fe80::216:3eff:fe6e:86b5 port 22: Invalid argument
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 10.0.3.94 failed: ssh: connect to host 10.0.3.94 port 22:
Connection refused
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 127.0.0.1 failed: Permission denied (publickey,password).


So similar, but different, still no sshd. So same problem on a clean OS
where only the lxd branch has ever run.

WTF? :)

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
John Meinel
2016-02-27 14:50:41 UTC
Permalink
Is 10.0.3.94 the correct IP for the LXD container? Did you let it sit a
while so it had a chance to keep trying until maybe SSH came up on its own?
And yet again, if you just do "lxc create" a container from exactly the
same image, is SSH running on it?

I'm recompiling my own work here making sure I'm tracking exactly the
lxd-container-type branch (though I merged it into the proposed branch I
had been working on.)

I'm running on Trusty, having installed LXD from the
ppa:ubuntu-lxc/lxd-stable ppa. I don't know if that has anything to do with
it. Would it be easier to chat about this on IRC? Are you available on
irc.freenode.net #juju-dev ?

John
=:->
Post by Tom Barber
Okay, evolution on a theme, clean install, compiled the new version and
016-02-27 14:40:51 DEBUG juju.provider.common bootstrap.go:318 connection
Connection refused
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 127.0.0.1 failed: Permission denied (publickey,password).
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for fe80::216:3eff:fe6e:86b5 failed: ssh: connect to host
fe80::216:3eff:fe6e:86b5 port 22: Invalid argument
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318 connection
Connection refused
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318 connection
attempt for 127.0.0.1 failed: Permission denied (publickey,password).
So similar, but different, still no sshd. So same problem on a clean OS
where only the lxd branch has ever run.
WTF? :)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
John Meinel
2016-02-27 14:53:30 UTC
Permalink
One thing you could try, "juju bootstrap test-lxd lxd --debug
--upload-tools --bootstrap-series trusty". It may be a difference based on
what the target series is.

John
=:->
Post by John Meinel
Is 10.0.3.94 the correct IP for the LXD container? Did you let it sit a
while so it had a chance to keep trying until maybe SSH came up on its own?
And yet again, if you just do "lxc create" a container from exactly the
same image, is SSH running on it?
I'm recompiling my own work here making sure I'm tracking exactly the
lxd-container-type branch (though I merged it into the proposed branch I
had been working on.)
I'm running on Trusty, having installed LXD from the
ppa:ubuntu-lxc/lxd-stable ppa. I don't know if that has anything to do with
it. Would it be easier to chat about this on IRC? Are you available on
irc.freenode.net #juju-dev ?
John
=:->
Post by Tom Barber
Okay, evolution on a theme, clean install, compiled the new version and
016-02-27 14:40:51 DEBUG juju.provider.common bootstrap.go:318 connection
Connection refused
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318
connection attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:52 DEBUG juju.provider.common bootstrap.go:318
connection attempt for 127.0.0.1 failed: Permission denied
(publickey,password).
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318
connection attempt for fe80::216:3eff:fe6e:86b5 failed: ssh: connect to
host fe80::216:3eff:fe6e:86b5 port 22: Invalid argument
2016-02-27 14:40:56 DEBUG juju.provider.common bootstrap.go:318
connection attempt for 10.0.3.94 failed: ssh: connect to host 10.0.3.94
port 22: Connection refused
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318
connection attempt for ::1 failed: Permission denied (publickey,password).
2016-02-27 14:40:58 DEBUG juju.provider.common bootstrap.go:318
connection attempt for 127.0.0.1 failed: Permission denied
(publickey,password).
So similar, but different, still no sshd. So same problem on a clean OS
where only the lxd branch has ever run.
WTF? :)
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 15:00:10 UTC
Permalink
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 15:17:10 UTC
Permalink
Also:

***@tomsdevbox:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial


lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial


juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
xenial


2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to bootstrap
model: no matching tools available


So that doesn't help ;)

As this is an empty box, I'll happily give you access so you can prod
around and see if you can figure it out ;)



--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 16:49:57 UTC
Permalink
Okay so a summary from IRC investigations with Rick H.

I thought yesterday on trusty manual sshd was running, i may have been
wrong.

Xenial image has a running sshd but I can't bootstrap it due to missing
tools

If anyone has a snippet for generating and using tools locally instead of
from the platform, feel free to share so I can bootstrap a xenial node
currently its failing with missing tools.

Cheers

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
xenial
2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to bootstrap
model: no matching tools available
So that doesn't help ;)
As this is an empty box, I'll happily give you access so you can prod
around and see if you can figure it out ;)
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 22:11:29 UTC
Permalink
Okay trusty images are failing for me because upstart borks and I get
dumped into runlevel unknown.

Serge might have an idea as he was involved in a similar bug issue a while
ago on launchpad....

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay so a summary from IRC investigations with Rick H.
I thought yesterday on trusty manual sshd was running, i may have been
wrong.
Xenial image has a running sshd but I can't bootstrap it due to missing
tools
If anyone has a snippet for generating and using tools locally instead of
from the platform, feel free to share so I can bootstrap a xenial node
currently its failing with missing tools.
Cheers
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
xenial
2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to bootstrap
model: no matching tools available
So that doesn't help ;)
As this is an empty box, I'll happily give you access so you can prod
around and see if you can figure it out ;)
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 22:26:15 UTC
Permalink
Also, right on boot, like the moment the image spins up if I force the
runlevel to 5, then the node gets bootstrapped without issue. So it is
something to do with:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337 or similar, just
with a Xenial host.

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay trusty images are failing for me because upstart borks and I get
dumped into runlevel unknown.
Serge might have an idea as he was involved in a similar bug issue a while
ago on launchpad....
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay so a summary from IRC investigations with Rick H.
I thought yesterday on trusty manual sshd was running, i may have been
wrong.
Xenial image has a running sshd but I can't bootstrap it due to missing
tools
If anyone has a snippet for generating and using tools locally instead of
from the platform, feel free to share so I can bootstrap a xenial node
currently its failing with missing tools.
Cheers
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
xenial
2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to bootstrap
model: no matching tools available
So that doesn't help ;)
As this is an empty box, I'll happily give you access so you can prod
around and see if you can figure it out ;)
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-27 23:42:51 UTC
Permalink
Okay I think I worked it out, but i dont' cause the cause in reality:

in upstart mountall was failing during the boot of the containers

so I did:

***@tomsdevbox ~ # umount /sys/kernel/debug
***@tomsdevbox ~ # mount -t debugfs none /sys/kernel/debug


and suddenly trusty images started booting......

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Also, right on boot, like the moment the image spins up if I force the
runlevel to 5, then the node gets bootstrapped without issue. So it is
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337 or similar,
just with a Xenial host.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay trusty images are failing for me because upstart borks and I get
dumped into runlevel unknown.
Serge might have an idea as he was involved in a similar bug issue a
while ago on launchpad....
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay so a summary from IRC investigations with Rick H.
I thought yesterday on trusty manual sshd was running, i may have been
wrong.
Xenial image has a running sshd but I can't bootstrap it due to missing
tools
If anyone has a snippet for generating and using tools locally instead
of from the platform, feel free to share so I can bootstrap a xenial node
currently its failing with missing tools.
Cheers
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
xenial
2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to bootstrap
model: no matching tools available
So that doesn't help ;)
As this is an empty box, I'll happily give you access so you can prod
around and see if you can figure it out ;)
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools --bootstrap-series
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Tom Barber
2016-02-29 09:45:14 UTC
Permalink
Hi Serge

I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.

***@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
Creating fix-server2
Starting fix-server2

***@tomsdevbox:~$ lxc exec fix-server2 /bin/bash
***@fix-server2:~# ps aux |grep ssh
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh

exit

umount and remount kernel debug....


***@tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
Creating fix-server3
Starting fix-server3
***@tomsdevbox:~$ lxc exec fix-server3 /bin/bash
***@fix-server3:~# ps aux |grep ssh
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh


***@tomsdevbox:~$ lxc-config -l
lxc.default_config
lxc.lxcpath
lxc.bdev.lvm.vg
lxc.bdev.lvm.thin_pool
lxc.bdev.zfs.root
lxc.cgroup.use
lxc.cgroup.pattern


Cheers

Tom



--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Hi Tom,
can you reproduce this with lxd alone?
What does 'lxc config show tomsdevbox' show?
-serge
Post by Tom Barber
in upstart mountall was failing during the boot of the containers
and suddenly trusty images started booting......
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Also, right on boot, like the moment the image spins up if I force the
runlevel to 5, then the node gets bootstrapped without issue. So it is
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/924337 or similar,
just with a Xenial host.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay trusty images are failing for me because upstart borks and I get
dumped into runlevel unknown.
Serge might have an idea as he was involved in a similar bug issue a
while ago on launchpad....
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Okay so a summary from IRC investigations with Rick H.
I thought yesterday on trusty manual sshd was running, i may have
been
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
wrong.
Xenial image has a running sshd but I can't bootstrap it due to
missing
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
tools
If anyone has a snippet for generating and using tools locally
instead
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
of from the platform, feel free to share so I can bootstrap a xenial
node
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
currently its failing with missing tools.
Cheers
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
Codename: xenial
lxd-images import ubuntu xenial amd64 --sync --alias ubuntu-xenial
juju bootstrap test-lxd lxd --debug --upload-tools
--bootstrap-series
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
xenial
2016-02-27 15:15:38 ERROR cmd supercommand.go:448 failed to
bootstrap
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
model: no matching tools available
So that doesn't help ;)
As this is an empty box, I'll happily give you access so you can
prod
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
around and see if you can figure it out ;)
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
juju bootstrap test-lxd lxd --debug --upload-tools
--bootstrap-series
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
trusty"
No difference. Im on juju-dev as magicaltrout.
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Serge E. Hallyn
2016-02-29 21:45:37 UTC
Permalink
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh
If you pull a fresh image using

lxd-images import ubuntu --alias newtrusty trusty amd64

and launch that

lxc launch newtrusty t1

does it have the same failure?

What does

lxc config show fix-server2 show?
--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-29 22:43:01 UTC
Permalink
Hi Serge

Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't have
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.

FYI

***@tomsdevbox:~$ lxc config show t1
name: t1
profiles:
- default
config:
volatile.base_image:
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
volatile.last_state.idmap:
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.lo.hwaddr: 00:16:3e:d2:98:62
devices:
root:
path: /
type: disk
ephemeral: false


juju bootstrap now seems to run fine without remounting the kernel debug.

Thanks for your help!

Tom


--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
Tom Barber
2016-02-29 22:57:08 UTC
Permalink
Seemingly the image name and key are the same, LXD and Juju are the same,
so you've either done something magic or I'm confused with its now seeming
happiness of the kernel debug mountpoint! :)

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't have
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel debug.
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
Casey Marshall
2016-02-29 23:25:36 UTC
Permalink
Post by Tom Barber
Seemingly the image name and key are the same, LXD and Juju are the same,
so you've either done something magic or I'm confused with its now seeming
happiness of the kernel debug mountpoint! :)
I ran into a similar issue today. xenial host, running latest juju out of
master for LXD API compatibility. I was unable to bootstrap and sshd was
not starting in the controller instance.

Remounted kernel debug on the host, and bootstrap started working, sshd
starting up now in my trusty instances.

Did not refresh my images. If it happens after rebooting the host, I'll try
to collect more info.

-Casey
Post by Tom Barber
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't have
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel debug.
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Serge E. Hallyn
2016-02-29 23:35:50 UTC
Permalink
Hi Casey,

I haven't reproduced that here in VMs. If you can reproduce this at will (by
rebooting the host) could you file a bug against the kernel (pad.lv/u/linux) ?

thanks,
-serge
Post by Casey Marshall
Post by Tom Barber
Seemingly the image name and key are the same, LXD and Juju are the same,
so you've either done something magic or I'm confused with its now seeming
happiness of the kernel debug mountpoint! :)
I ran into a similar issue today. xenial host, running latest juju out of
master for LXD API compatibility. I was unable to bootstrap and sshd was
not starting in the controller instance.
Remounted kernel debug on the host, and bootstrap started working, sshd
starting up now in my trusty instances.
Did not refresh my images. If it happens after rebooting the host, I'll try
to collect more info.
-Casey
Post by Tom Barber
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't have
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel debug.
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that were
running fine all now have broken SSHD. This, to make absolutely clear
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00 grep
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00 grep
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-02-29 23:38:36 UTC
Permalink
Its pretty weird, because a few reboots and it failed, now its magically
working post reboot. Worst comes to the worst I can flatten the machine
again and I'm sure it will reappear as it did the previous 2 occasions.

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Hi Casey,
I haven't reproduced that here in VMs. If you can reproduce this at will (by
rebooting the host) could you file a bug against the kernel (
pad.lv/u/linux) ?
thanks,
-serge
Post by Casey Marshall
Post by Tom Barber
Seemingly the image name and key are the same, LXD and Juju are the
same,
Post by Casey Marshall
Post by Tom Barber
so you've either done something magic or I'm confused with its now
seeming
Post by Casey Marshall
Post by Tom Barber
happiness of the kernel debug mountpoint! :)
I ran into a similar issue today. xenial host, running latest juju out of
master for LXD API compatibility. I was unable to bootstrap and sshd was
not starting in the controller instance.
Remounted kernel debug on the host, and bootstrap started working, sshd
starting up now in my trusty instances.
Did not refresh my images. If it happens after rebooting the host, I'll
try
Post by Casey Marshall
to collect more info.
-Casey
Post by Tom Barber
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't
have
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel
debug.
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that
were
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
running fine all now have broken SSHD. This, to make absolutely
clear
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Tom Barber
2016-03-01 17:01:50 UTC
Permalink
Okay we're back.....

Here is the /proc/mount stuff:

http://paste.ubuntu.com/15260347/
http://paste.ubuntu.com/15260350/

You can see a bit of a diff after the remount, hope it helps!

Tom

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Its pretty weird, because a few reboots and it failed, now its magically
working post reboot. Worst comes to the worst I can flatten the machine
again and I'm sure it will reappear as it did the previous 2 occasions.
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Hi Casey,
I haven't reproduced that here in VMs. If you can reproduce this at will (by
rebooting the host) could you file a bug against the kernel (
pad.lv/u/linux) ?
thanks,
-serge
Post by Casey Marshall
Post by Tom Barber
Seemingly the image name and key are the same, LXD and Juju are the
same,
Post by Casey Marshall
Post by Tom Barber
so you've either done something magic or I'm confused with its now
seeming
Post by Casey Marshall
Post by Tom Barber
happiness of the kernel debug mountpoint! :)
I ran into a similar issue today. xenial host, running latest juju out
of
Post by Casey Marshall
master for LXD API compatibility. I was unable to bootstrap and sshd was
not starting in the controller instance.
Remounted kernel debug on the host, and bootstrap started working, sshd
starting up now in my trusty instances.
Did not refresh my images. If it happens after rebooting the host, I'll
try
Post by Casey Marshall
to collect more info.
-Casey
Post by Tom Barber
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine,
so
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
whatever you did, i assume worked or is a freak occurrence. I don't
have
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel
debug.
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that
were
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
running fine all now have broken SSHD. This, to make absolutely
clear
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Casey Marshall
2016-03-01 17:08:55 UTC
Permalink
Post by Serge E. Hallyn
Hi Casey,
I haven't reproduced that here in VMs. If you can reproduce this at will (by
rebooting the host) could you file a bug against the kernel (
pad.lv/u/linux) ?
Saw it again after booting up my laptop this morning, opened a bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551854
Post by Serge E. Hallyn
thanks,
-serge
Post by Casey Marshall
Post by Tom Barber
Seemingly the image name and key are the same, LXD and Juju are the
same,
Post by Casey Marshall
Post by Tom Barber
so you've either done something magic or I'm confused with its now
seeming
Post by Casey Marshall
Post by Tom Barber
happiness of the kernel debug mountpoint! :)
I ran into a similar issue today. xenial host, running latest juju out of
master for LXD API compatibility. I was unable to bootstrap and sshd was
not starting in the controller instance.
Remounted kernel debug on the host, and bootstrap started working, sshd
starting up now in my trusty instances.
Did not refresh my images. If it happens after rebooting the host, I'll
try
Post by Casey Marshall
to collect more info.
-Casey
Post by Tom Barber
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Tom Barber
Hi Serge
Fresh reboot and updated image, image boots with SSHD working fine, so
whatever you did, i assume worked or is a freak occurrence. I don't
have
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
any old images kicking around and the import I copied from your email
appears to have stomped on the old image.
FYI
name: t1
- default
510c27eb5e30ac53c6cf8b423d4e145bd2e40b8845e89bd66a5d78e2a087727a
volatile.eth0.hwaddr: 00:16:3e:94:d5:66
'[{"Isuid":true,"Isgid":false,"Hostid":165536,"Nsid":0,"Maprange":65536},{"Isuid":false,"Isgid":true,"Hostid":165536,"Nsid":0,"Maprange":65536}]'
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
volatile.lo.hwaddr: 00:16:3e:d2:98:62
path: /
type: disk
ephemeral: false
juju bootstrap now seems to run fine without remounting the kernel
debug.
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Thanks for your help!
Tom
--------------
Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316
(Thanks to the Saiku community we reached our Kickstart
<
http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)
Post by Serge E. Hallyn
Post by Tom Barber
Hi Serge
I rebooted the host to see what happened and the lxc images that
were
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
running fine all now have broken SSHD. This, to make absolutely
clear
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
doesn't affect the Xenial image, just the trusty one I test with.
Creating fix-server2
Starting fix-server2
root 1597 0.0 0.0 8868 660 ? S+ 09:41 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
exit
umount and remount kernel debug....
Creating fix-server3
Starting fix-server3
root 1759 0.0 0.0 61380 3816 ? Ss 09:42 0:00
/usr/sbin/sshd -D
root 1944 0.0 0.0 8868 604 ? S+ 09:43 0:00
grep
Post by Casey Marshall
Post by Tom Barber
Post by Tom Barber
Post by Serge E. Hallyn
Post by Tom Barber
--color=auto ssh
If you pull a fresh image using
lxd-images import ubuntu --alias newtrusty trusty amd64
and launch that
lxc launch newtrusty t1
does it have the same failure?
What does
lxc config show fix-server2 show?
--
Juju mailing list
https://lists.ubuntu.com/mailman/listinfo/juju
Serge E. Hallyn
2016-02-29 21:45:22 UTC
Permalink
Post by Tom Barber
in upstart mountall was failing during the boot of the containers
Is this on the host (vm, whatever), or in the container?

What does /proc/self/mountinfo show before and after the
remount?

-serge
--
Juju mailing list
***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Continue reading on narkive:
Loading...