[03:12] <Rlyeh> Yesterday, I Downloaded Snappy from "http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-armhf-bbb.img.xz"for BBB
[03:12] <Rlyeh> But the system didn't boot
[03:12] <Rlyeh> I checked the "system-boot partition, the "uenv.txt" was empty
[03:13] <Rlyeh> "system-boot" partition
[03:14] <Rlyeh> And there was a install.yaml! It was not available in the version 1!
[03:14] <Rlyeh> Well, do you know how can I boot the new snappy on my BBB?
[03:16] <Rlyeh> Should I have to copy the uenv.txt content from version 1 to this new version? or the boot mechanism is totally changed in new version?
[03:18] <Rlyeh> Here is the uenv.txt in version 1, 2 and 3 -> "http://paste.ubuntu.com/12720512/"
[03:18] <Rlyeh> It's same
[05:49] <Rlyeh> No solution for boot problem?!!!
[06:11] <biezpal> Rlyeh, afaik, uEnv.txt should be empty. There is snappy-system.txt with all required variables
[06:17] <Rlyeh> It's not booting :(
[06:23] <Rlyeh> BBB jumps to debian on emmc
[06:33] <tbr> Rlyeh: did you hold down S2 before connecting power to the BBB?
[06:48] <clobrano> Buongiorno :)
[07:12] <fgimenez> good morning
[07:24] <davidcalle> Good morning
[07:28] <dholbach> good morning
[08:08] <longsleep> good morning snappy
[08:09] <longsleep> biezpal: it is normal that uEnv.txt is empty. Snappy uses uboot.env for booting
[08:10] <longsleep> biezpal: Do you have a serial console, to check what u-boot is doing?
[08:11] <longsleep> biezpal: ah sorry, it was Rlyeh who asked that question
[08:14] <biezpal> longsleep, np :)
[08:22] <ogra_> well, Ryleh most likely didnt press S2
[08:43] <longsleep> ogra_: i should probably get a BBB for testing - S2 is a button?
[08:44] <ogra_> yeah ... also called "user button"
[08:44] <longsleep> ok - and that controls what to boot or why does one have to press it?
[08:44] <ogra_> you have to hold it down for the first time you want to boot from external media (subsequent boots from SD dont need it)
[08:45] <longsleep> ahh - the bbb only boots from nand by default - i get it thanks
[08:45] <ogra_> well, eMMC
[08:45] <longsleep> is the eMMC removable ?
[08:45] <ogra_> nope
[08:46] <longsleep> i see - can snappy also boot when put on the eMMC then?
[08:46] <ogra_> never tried :)
[08:46] <tbr> longsleep: you can nuke the MLO on eMMC, then it will default to SD
[08:46] <longsleep> tbr: right, but would be nice to avoid using an external media or have the sd available for storage
[08:46] <ogra_> buut given we boot based on labels i wouldnt see why not
[08:47] <ogra_> as long as you can name the partitions correctly on the MMC
[08:47] <longsleep> it works fine for the odroid, though the eMCC is removable there and we do not use it because of the cost
[08:47] <tbr> ogra_: I offered a while ago to look into the install script that debian uses and how that could be adapted, but then some handwaving ensued
[08:48] <longsleep> how do you flash the eMMC - is there some boot loader / fastboot thing?
[08:48] <longsleep> i mean if you cannot put it into your pc
[08:48] <tbr> longsleep: you could flash it over USB or UART, but usually you just boot from an SD and write from the booted system to the eMMC
[08:49] <ogra_> there is work going on to create a recovery img we ship in all installs ...
[08:49] <ogra_> that would have a dd like installer i guess
[08:49] <ogra_> and factory reset etc
[08:50] <longsleep> yeah that would be nice
[08:53] <longsleep> tbr: i just read the docs about it, thanks
[08:54] <longsleep> ogra_: do you have an idea what happens if you have partitions with the same label on eMMC and SD ?
[08:54]  * longsleep wonders which one is used
[08:54] <ogra_> nope
[08:54] <ogra_> havent tried
[08:54] <JamesTait> Good morning all; happy Friday, and happy Curious Events Day! 😃
[08:56] <tbr> https://github.com/RobertCNelson/tools/tree/master/scripts - if someone wants to take a look how to adapt
[09:57] <Chipaca> elopio: fgimenez: you around?
[10:18] <fgimenez> Chipaca, yep
[10:18] <Chipaca> fgimenez: i have a branch up for review that probably breaks stuff
[10:19] <Chipaca> fgimenez: could you / would you take a look?
[10:19] <Chipaca> fgimenez: https://code.launchpad.net/~chipaca/snappy/auth/+merge/273684
[10:19] <fgimenez> Chipaca, sure, which one?
[10:19] <fgimenez> Chipaca, ok thanks :)
[10:19] <Chipaca> fgimenez: basically all non-GET rest api tests will fail
[10:20] <Chipaca> fgimenez: or should :D
[10:20] <Chipaca> need to add something to first boot to set a default password
[10:20] <fgimenez> Chipaca, ok, thx i'll check :) we are currently testing post to packages
[10:20] <Chipaca> neat
[11:19] <fgimenez> Chipaca, it fails \o/
[11:19] <Chipaca> heh
[11:20] <Chipaca> fgimenez: thanks
[11:20] <Chipaca> now we need to decide how to un-fail it :)
[11:20] <fgimenez> Chipaca, ok, the tests need some adjustments though, it was passing at first :)
[11:20] <Chipaca> fgimenez: oh? how?
[11:21] <fgimenez> Chipaca, they was using /usr/bin/snapd instead of the compiled one
[11:21] <Chipaca> lel
[11:23] <fgimenez> Chipaca, also, we were checking for a 405 method not allowed response in unhandled verbs
[11:23] <Chipaca> that is correct
[11:23] <Chipaca> but now you'd get a 401 before that
[11:23] <fgimenez> Chipaca, yes, we need to change that in the test
[11:23] <Chipaca> you'd still want to check for the 405 once you're sending in credentials
[11:23] <fgimenez> Chipaca, ah, ok, then that's ok
[12:17] <Chipaca> ogra_: you around perchance?
[12:17] <ogra_> no, not perchance ...
[12:17] <ogra_> ... just regular
[12:18] <Chipaca> :)
[12:18] <ogra_> :)
[12:18] <Chipaca> ogra_: so, REST API now needs creds to do stuff
[12:18] <ogra_> whee
[12:18] <Chipaca> ogra_: including things like, um, setting up creds
[12:18] <ogra_> lol
[12:18] <Chipaca> (nothing of this is landed yet ;)
[12:19] <ogra_> so i guess we should have some snappy config way to set this to a sane default (i.e. if --developer-mode enable ubuntu/ubuntu)
[12:19] <Chipaca> that, and/or "snappy passwd"
[12:20] <ogra_> ah, thats new ?
[12:20] <Chipaca> that's non-existent
[12:20] <Chipaca> that's what i'm asking :)
[12:20] <ogra_> can we also enforce updating of the  pw ?
[12:20] <Chipaca> ogra_: you mean, pw age policy?
[12:21] <ogra_> so that we could ship with a default on the images but enforce the update on first login via the REST api ?
[12:21] <ogra_> yeah, something like the pw age policy
[12:21] <ogra_> but if i dont have ssh enabled i need to be able to get in once to set a new one
[12:22] <Chipaca> that's a good point, we probably want that
[12:22] <Chipaca> but it's a chunk of work :)
[12:22] <ogra_> yeah, i guess
[12:23] <Chipaca> and not sure of the details of it
[12:24] <Chipaca> ogra_: snappy config such that the oem can set default pw was what i was thinking, with it defaulting to ubuntu/ubuntu if in dev mode
[12:24] <Chipaca> ogra_: and i didn't know if we'd also need a snapp passwd thing
[12:24] <Chipaca> ogra_: password aging, and password policy in general, wasn't in what i'd been thinking of doing
[12:24] <ogra_> well, we dont use --developer-mode on the official images we offer
[12:24] <ogra_> only --enable-ssh
[12:25] <Chipaca> so the cmd is a must
[12:26] <Chipaca> with a nice-to-have of accepting config (just to set passwd in core) if no passwd set
[12:26] <ogra_> also do we have a way to have passwords hidden in the snappy config output yet ?
[12:27] <ogra_> so only *** is shown
[12:27] <Chipaca> ogra_: i was thinking of doing it for coreconfig
[12:27] <ogra_> yeah
[12:28] <ogra_> though with a fixed lenght string so the actual PW lenght isnt guessable
[12:28] <Chipaca> ogra_: was thinking of just replacing the value in the yaml with "***pasword***" or some such placeholder text, on the way out
[12:28] <ogra_> yeah
[12:28] <Chipaca> ogra_: which is something you could do with bip too :)
[12:28] <ogra_> just to indicate there is one set
[12:28] <Chipaca> (was it bip?)
[12:29] <ogra_> yeah
[12:29] <ogra_> the package is called ircproxy :)
[12:29] <ogra_> but it uses bip
[12:30] <Chipaca> ogra_: another way would be to use a special yaml thing for passwords
[12:30] <Chipaca> i could dig into that if it'd be useful
[12:31] <ogra_> we should ask jdstrand for input here
[12:31] <ogra_> after all thats a security thing :)
[13:28] <Chipaca> ogra_: echo "config: {ubuntu-core: {password: password}}" | snappy config ubuntu-core -- -
[13:28] <Chipaca> \o/
[13:29] <ogra_> :)
[13:30] <clobrano> Hi Chipaca, any news from security guys for Bug #1496319? :)
[13:30] <Chipaca> clobrano: no
[13:30] <Chipaca> clobrano: but i hear they're backlogged atm
[13:31] <ogra_> and most of them are in the US....
[13:31] <ogra_> where nobody works today... celebrating that guy who got lost
[13:33] <clobrano> :D
[14:03] <jdstrand> Chipaca: we are we needed for 1496319?
[14:11] <tbr> did anyone look into snappy images for scaleway yet?
[14:17] <jdstrand> beuno: fyi, I tried to accept docker in the review: OOPS ID: OOPS-3587e98ff8044c0db2885414f81ffd46
[14:17] <jdstrand> kickinz1: ^
[14:18] <jdstrand> beuno: I don't know how to proceed and am afraid to try to approve again
[14:18] <jdstrand> beuno: it is ok to accept (kickinz1 will fix 'architectures' for next time and the security policy changes are ok)
[14:19] <jdstrand> it appears to have been accepted
[14:20] <jdstrand> (based on the website)
[14:31] <beuno> jdstrand, I accepted it as well
[14:31] <beuno> maybe we fought over accepting it
[14:31] <beuno> jdstrand, I'll look into it, thanks
[14:43] <jdstrand> maybe
[14:51] <tedg> ogra_: That's Monday actually, US is in today :-)
[14:51] <tedg> (well I imagine some people took vacation)
[14:57] <ogra_> tedg, oh, not today ?
[14:57] <ogra_> damn, mixed that up
[14:58] <ogra_> tbr, i dont think anyone has started on that
[14:58] <tbr> k
[14:58] <tbr> it's interesting because it's cloud, but it's ARMv7
[14:58] <ogra_> yeah
[15:22] <Chipaca> fgimenez: any idea why umount would pin a cpu at 100% at the start of adt-run?
[15:23] <Chipaca> 32223 root       20   0 25392  1688  1512 R   1 100.  0.0  8:52.81 umount /tmp/diskimage185973715/system
[15:23] <Chipaca> like so ^
[15:24] <fgimenez> Chipaca, nope atm, how do you run it?
[15:24] <Chipaca> fgimenez: GOPATH=~/canonical/snappy ./run-checks
[15:26] <fgimenez> Chipaca, never saw that before, from which branch are you running it?
[15:27] <Chipaca> fgimenez: my auth thing
[15:28] <fgimenez> Chipaca, didn't try run-checks, go run _integration-tests/main.go goes fine here, i'll check run-checks
[15:28] <Chipaca> it's u-d-f hanging somehow
[15:28] <Chipaca> sergiusens: you seen that?
[15:29] <sergiusens> Chipaca, fgimenez if u-d-f was rebuilt, maybe check all the FDs are closed
[15:29] <sergiusens> lsof
[15:29] <sergiusens> it shouldn't cause a spin of the cpu
[15:31] <Chipaca> oh
[15:31] <Chipaca> no space left on device
[15:31] <Chipaca> that might cause it
[15:31] <elopio> fgimenez: could we use a link to the icon, instead of copying it into every snap?
[15:31] <elopio> does that work? I'll give it a try.
[15:33] <fgimenez> elopio, it would be very useful, let me know how it goes
[15:41] <elopio> fgimenez: I did this service test before I realized I wanted to copy your local snaps style.
[15:41] <elopio> I regret that because now every other branch depends on it.
[15:41] <elopio> are you ok if I land it, and then make another branch to move the helloDBus tests to examples, and add a local snap instead?
[15:43] <fgimenez> elopio, sure, np
[15:44] <Chipaca> fgimenez: rebooted because my /tmp got into a mess, and now i get past the unmounting, but am still at the "ssh connection failed" bit
[15:44] <Chipaca> i've never gotten past this stage
[15:44] <Chipaca> how do i get it past this stage?
[15:46] <fgimenez> Chipaca, which version of autopkgtest are you using?
[15:46] <Chipaca> fgimenez: 3.17.3
[15:47] <fgimenez> Chipaca, same here, what if you execute go run _integration-tests/main.go -release 15.04 ?
[15:47] <elopio> Chipaca: did your udf fail? I get this every other time: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1496484
[15:48] <Chipaca> elopio: when it failed, i aborted, cleared loop0p5, and redid
[15:49] <Chipaca> fgimenez: doing that now
[15:49] <elopio> tedg: how do I make a snappy lxc?
[15:53] <Chipaca> fgimenez: getting the same “adt-virt-ssh: WARNING: ssh connection failed. Retrying in 3 seconds...”
[15:53] <Chipaca> fgimenez: except more than 3 seconds pass between each one
[15:53] <Chipaca> and the qemu is doing *something*
[15:57] <fgimenez> Chipaca, you should be able to access the image with kvm -m 512 -redir :8022::22 /tmp/snappy-test/image/snappy-rolling-edge-latest.img
[15:57] <fgimenez> Chipaca, does it boot ok?
[15:58] <Chipaca> well, 15.04 not rolling because you just told me to -release 15.04 :)
[15:58]  * Chipaca tries it
[15:58] <fgimenez> Chipaca, yes, sorry :)
[15:59] <Chipaca> it's not booting
[16:00] <fgimenez> Chipaca, maybe udf doesn't create it properly
[16:01] <ogra_> is that 204 ?
[16:01] <ogra_> (that is exactly what i wanted to have tested)
[16:01] <ogra_> could be the grub changes, but these only landed in 204
[16:03] <Chipaca> this is 15.04
[16:03] <Chipaca> not sure the revno
[16:03] <Chipaca> redoing from the start
[16:03] <ogra_> u-d-f should have printed it
[16:04] <fgimenez> ogra_, 15.04 204 is working fine here
[16:04] <ogra_> phew !
[16:04]  * ogra_ hugs fgimenez 
[16:04] <ogra_> thanks !
[16:05] <ogra_> that saves my weekend :)
[16:05] <fgimenez> ogra_, yw :)
[16:06]  * Chipaca continues to work to ruin ogra_'s weekend
[16:06] <ogra_> haha
[16:06]  * Chipaca likes the feeling of power
[16:06] <ogra_> my heating breaking down already is ahead of you
[16:06]  * ogra_ hopes it is only the oil filter being dirty and not the pump 
[16:07] <Chipaca> oil filter? do you use a diesel engine to power the pump?
[16:07] <ogra_> yeah, but its a clean VW one
[16:07] <ogra_> :P
[16:08] <davmor2> ogra_: damn you beat me to it :)
[16:08] <ogra_> (i think 60-70% of german heatings still burn oil)
[16:08] <Chipaca> fgimenez: retried with rolling, still no luck with the tests, but the image boots
[16:08] <ogra_> its a central heating but a oli furnace
[16:08] <ogra_> ... that powers it
[16:09] <Chipaca> fgimenez: and i can ssh in and all
[16:09] <davmor2> ogra_: yes you and america are the reason the cost of diesel rockets in the winter
[16:09] <ogra_> i dont really need the heating, it is warm enough still, but it also does warm water
[16:09] <Chipaca> ogra_: leaves more russian gas for the uk \o/
[16:09] <ogra_> lol
[16:09] <ogra_> i wish we had gas in my street ...
[16:10] <ogra_> but like cable the neighborhood wasnt willing to pay for it
[16:11] <ogra_> (tow streets down they have gas and 200MBit cable)
[16:11] <fgimenez> Chipaca, what if, with the image booted with kvm, you run go run _integration-tests/main.go -ip 127.0.0.1 -port 8022 ?
[16:12] <Chipaca> STUFF IS HAPPENING!!!!1!!!one!
[16:12] <ogra_> yay
[16:12] <fgimenez> Chipaca, \o/
[16:14] <fgimenez> this bypass the image creation and booting part, anyway something is wrong, that should be done by the runner
[16:22] <tedg> stgraber: I thought there was a snappy image for LXD, but I can't seem to find it. Am I remembering wrong or just suck at Google? :-)
[16:23] <ogra_> tedg, there is an lxd snap in the store
[16:24] <tedg> ogra_: Yeah, looking the other way around
[16:26] <Chipaca> fgimenez: ohhh...
[16:26] <Chipaca> fgimenez: after a number of reboots and stuff, this:
[16:26] <Chipaca> Rebooting...
[16:26] <Chipaca> bash: line 1:  1087 Killed                  bash -ec './_integration-tests/reboot-wrapper integration.test' 2> >(tee -a /tmp/adt-run.rEvouJ/command1-stderr >&2) > >(tee -a /tmp/adt-run.rEvouJ/command1-stdout)
[16:26] <Chipaca> fgimenez: and now it's stuck waiting for ssh again
[16:26] <Chipaca> (i can log into the system just fine)
[16:26] <Chipaca> ah! but no ipv4 address!
[16:28]  * Chipaca runs dhclient by hand
[16:28] <fgimenez> Chipaca, you found it after all! i thought i was mistaken :) it must be the same think that elopio reported for bbb
[16:35] <fgimenez> leaving, nice weekend everyone o/
[16:54] <Chipaca> ogra_: elopio: have either of you ever seen a package decide it's sideloaded on update?
[17:19] <elopio> Chipaca: nop.
[17:20] <elopio> Chipaca: oh, I forgot. I did this because it was hard to find the test that was failing for you a couple of weeks ago
[17:20] <elopio> https://code.launchpad.net/~elopio/snappy/results_on_error/+merge/273013
[17:21] <longsleep> What is the best approach to add snapcraft plugins, adding an example how to use it?
[17:21] <elopio> not sure if there's a better way to do it. Can you review please?
[17:21] <sergiusens> tedg, until recently there was no snappy image for lxd due to all the security architecture around it
[17:22] <sergiusens> recently though, apparamor gained the possibility of profiles within profiles which was one of the blockers
[17:22]  * sergiusens knows he is using the terminology all wrong
[17:26] <jdstrand> wait, what?
[17:26] <jdstrand> I'm confused by the 'all wrong terminology'
[17:27] <jdstrand> oh, snappy in lxd?
[17:27] <jdstrand> right, so, apparmor doesn't yet have namespace stacking support
[17:28] <jdstrand> which means that the host and the guest can't have unmodified profiles
[17:29] <jdstrand> so it makes running snappy in a container harder than you'd want (should be able to if you disable apparmor for lxd on the host)
[17:29] <jdstrand> the namespace stacking work has not landed yet, but it is coming. we are targeting 16.04
[17:37] <tedg> Ah, okay, so elopio I was wrong about that ^
[17:38] <tedg> Apparently we can't do the tests in LXD yet.
[18:17] <ogra_> Chipaca, never
[18:31] <sergiusens> longsleep, I don't follow, or if I do, just add a small project in the examples directory; to make sure it doesn't break even add a smaller project in integration_tests
[18:55] <ogra_> beuno, you are being missed in a certain "-external" channel
[19:45] <jdstrand> ogra_: fyi, I filed those three snappy bugs we talked about (nameservers, ntp and rsyslog)
[21:25] <sergiusens> jdstrand, I think a little bird told me you were going to get the reviewer tools updated in ppa:snappy-dev/tools for vivid and trusty, is that correct?
[21:25] <jdstrand> yes
[21:26] <jdstrand> but I need to first update them for the things we agreed to :)
[21:26] <jdstrand> I've started that
[22:16] <jdstrand> sergiusens: ok, fix committed to trunk. the store will pick it up next week
[22:16] <jdstrand> sergiusens: I have one other thing to add then I'll push to the ppa
[22:16] <jdstrand> that will happen next week
[22:17] <jdstrand> sergiusens: unless it is critical that you have it in the ppa sooner. let me know and I'll push what I have
[22:20] <sergiusens> jdstrand, it's fine; just noticed an MP where snappy build re enabled the review tools so didn't want have havoc when the tools ppa got updated
[22:24] <jdstrand> sergiusens: right, don't push that yet. feel free to add me as a reviewer
[22:25] <jdstrand> sergiusens: the one thing that is left is actually so that can be turned on
[22:28] <sergiusens> jdstrand, I noticed it landed while I was out; but it hasn't made it to the general population yet ;)
[23:08] <jdstrand> sergiusens: ok, I uploaded review tools 0.34 to the tools-proposed ppa
[23:09]  * jdstrand -> weekend