LXD Bootstrap

[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

Quoting Casey Marshall (casey.marshall at canonical.com):
> On Mon, Feb 29, 2016 at 4:57 PM, Tom Barber <tom at analytical-labs.com> wrote:
> 
> > 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
> 
> 
> > --------------
> >
> > 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>)
> >
> > On 29 February 2016 at 22:43, Tom Barber <tom at analytical-labs.com> wrote:
> >
> >> 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
> >>
> >> bugg at 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>)
> >>
> >> On 29 February 2016 at 21:45, Serge E. Hallyn <serge at hallyn.com> wrote:
> >>
> >>> On Mon, Feb 29, 2016 at 09:45:14AM +0000, Tom Barber wrote:
> >>> > 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.
> >>> >
> >>> > bugg at tomsdevbox:~$ lxc launch ubuntu-trusty fix-server2
> >>> > Creating fix-server2
> >>> > Starting fix-server2
> >>> >
> >>> > bugg at tomsdevbox:~$ lxc exec fix-server2 /bin/bash
> >>> > root at 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....
> >>> >
> >>> > bugg at tomsdevbox:~$ lxc launch ubuntu-trusty fix-server3
> >>> > Creating fix-server3
> >>> > Starting fix-server3
> >>> > bugg at tomsdevbox:~$ lxc exec fix-server3 /bin/bash
> >>> > root at 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
> >>>
> >>> 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
> > Juju at lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju
> >
> >