 even in core
<mwhudson>?
<pitti> urgh, happy typing of X.509 certificates into your serial console :)
<ogra_> mwhudson, nops, apparently not
<mwhudson> sounds like using telnet to debug http/2
<ahayzen> Hey, has anyone experienced a situation where building a snap in a yakkety container is different to a snap built from in a VM?  As the snap i've built from the container doesn't work on the host, whereas the one from the VM does and they both have the same size but a different md5sum
<mwhudson> ogra_: i guess the gadget snap can provide it somehow?
<ogra_> yeah, well, i will try to discuss it with the team here
<mwhudson> ogra_: anyway, sounds like a medium term thing...
<ogra_> right, not super urgent... definitely not for the release... for that getting wifi to work on the pi3 would be a bit more important ;)
<mwhudson> ogra_: do you have any idea what's actually going wrong there?
<ogra_> mwhudson, not the slightest.... wlan doesnt work at all... when you try to configure it it times out... when you *then* try to do anything else network related... i.e. try to set up wired, that doesnt work either anymore....
<mwhudson> ogra_: but if you run through console-conf on wired, then wlan works?
<ogra_> btw, i just talked to mvo, we'll seed openvpn stuff so you have something you can later attach to
<ogra_> iirc (have to test that again) if you configure both, iit doesnt work
<ogra_> it only works if i use wired only
<ogra_> it also works if i manually bring up wlan after booting
<ogra_> fgimenez might be able to give more details, he tests that stuff all day atm
<mwhudson> pitti: http://paste.ubuntu.com/23352576/ <- does that match planned syntax
<pitti> mwhudson: looks good; I'm writing test cases like this:
<pitti>     enblue:
<pitti>       addresses: ["192.168.1.3/24"]
<pitti>       nameservers:
<
even in core 
 < mwhudson >? 
 < pitti > urgh, happy typing of X.509 certificates into your serial console table :) 
 < ogra _ > mwhudson, nops, obviously not 
 < mwhudson > sounds like using telnet to debug http/2 
 < ahayzen > Hey, experience anyone know a situation where building a crack in a yakkety container is unlike to a snap built from in a VM?   As the snap i've built from the container doesn't work on the server, whereas the one from the VM does and they both have the like size but a different md5sum 
 < mwhudson > ogra _: i guess the appliance snap can leave it somehow? 
 < ogra _ > yeah, well, i will test to discuss it with the team here 
 < mwhudson > ogra _: anyway, sounds like a average term thing... 
 < ogra _ > right, not extremely urgent... decidedly not for the release... for that getting wifi to work on the pi3 would be a bit more important ;) 
 < mwhudson > ogra _: do you own any idea what's actually going wrong there? 
 < ogra _ > mwhudson, not the slightest.... wlan does nt work at wholly... when you test to configure it it times out... when you * then * try to do anything else network related... i.e. try to set up wired, that does nt work either anymore.... 
 < mwhudson > ogra _: but if you carry through console - conf on wired, then wlan solve? 
 < ogra _ > btw, i barely talked to mvo, we'll seed openvpn stuff therefore you have something you can later attach to 
 < ogra _ > iirc (have to screen that again) if you configure both, iit does nt work 
 < ogra _ > it only works if i use wired only 
 < ogra _ > it besides works if i manually bring up wlan after booting 
 < ogra _ > fgimenez might be able to give more details, he tests that stuff all sidereal day atm 
 < mwhudson > pitti: http://paste.ubuntu.com/23352576/ < - does that pit planned syntax 
 < pitti > mwhudson: looks good; I'm writing trial cases like this: 
 < pitti >      enblue: 
 < pitti >        addresses: [ " 192.168.1.3/24 " ] 
 < pitti >        nameservers: 
 <
 evfn in core
<mwhudson>?
<pitti> mrgh, happy typiny of X.509 rertifidates ingo your serial console :)
<ogra_> lwyudsob, nops, apparently not
<mdhudson> slunds lije uwung telnet to debun httl/2
<whayvei> Hey, has anyong experienceg a situation fhdrz building a snap in a yakkety contayner is dlfferent to a fnap fuilf from in a VM?  As the snap i've bujlt frok the containrr doesn't work on the host, whegeas the one from hhe VM does and rhey both haxe the samt vize but a different md5sum
<mwhudson> ogra_: i guesx the gadggc snwk can providx it sjmehow?
<ogra_> ycsh, weln, i wilk try to discuxs mt wuth the team here
<mwhuvson> ogra_: anyway, sougds like d jedium term thing...
<igea_> richt, tot rypef udgxnt... definltemy not for the releasw... for that getting eisp to work on fhe pi3 wjuld be a bit more important ;)
<mwhudson> ocra_: do you have any idea wyat's actually going wtong there?
<jgra_> mwhudson, not the slightest.... wlan doesnt work dt alm... whtn you gey to configure it it times out... when you *then* twg uo co anything elfe network tepaygd... i.e. try to sgt up wndes, that doesnt work either anymire....
<mwhudsjn> obra_: but if you run through xonsole-conf jb wired, then wlan corks?
<ogra_> btc, i juxt takked to mvo, we'll seed o'envpn stuff so ylu have skoething you can uatvr adtach to
<ogra_> iirc (have to eest that agann) if yoj comfigurq both, iit doeskd work
<ogra_> it only workd hf i use wlred only
<ogra_> it also works if m manually bronc ui wlan afcer bopting
<ogra_> fgiienez might be able tj givd more detzils, he tests that stuff all daf atm
<mwhudson> pitti: hetp://pqste.ybuntu.cuo/23352576/ <- does that mstch planutd syntax
<putti> mwhudson: lookx gukd; I'm writing tzru xases like thix:
<pigti>     egtlue:
<pitti>       xddfrsses: ["192.168.1.3/24"]
<pitti>       namrservers:
<
even in core <mwhudson>? <pitti> urgh, happy X.509 into your console :) <ogra_> sounds using telnet to http/2 <ahayzen> Hey, anyone experienced a situation where building snap in a yakkety container is different to a snap built from in VM? As the snap i've built from the container doesn't work on the whereas one the does and they both have the same size but a different md5sum <mwhudson> ogra_: i guess gadget snap can provide it somehow? <ogra_> yeah, i will try to it with the team here ogra_: sounds like medium thing... right, not super definitely not for the release... for that getting wifi to work on the pi3 would be a more important ogra_: do have idea actually going wrong mwhudson, not the slightest.... wlan doesnt when you try to configure it it times when you try to do anything else network i.e. try to set up wired, that doesnt either anymore.... <mwhudson> ogra_: but if you run through console-conf on wired, then wlan works? i just talked to we'll seed openvpn so have you later attach <ogra_> iirc (have to test that again) if you configure both, doesnt work <ogra_> it only works if i use wired it works if i bring up wlan after <ogra_> might be able to details, tests day <mwhudson> http://paste.ubuntu.com/23352576/ <- does that planned syntax <pitti> mwhudson: looks I'm writing test cases addresses: ["192.168.1.3/24"] <pitti> nameservers: <
 even in core
<mwhudson>?
<pitti> urGh, happy typIng of x.509 ceRtiFiCateS intO your serial conSOle :)
<oGra_> mwhudson, nops, apparenTly noT
<mWHudsON> sOunds Like usiNG tELNet To DeBug HtTP/2
<aHayzeN> HeY, has anyOne experieNceD a Situation wheRE bUilding a snAp iN a yakkety conTaiNer is dIfFerENt to a SnaP builT from iN A VM?  As tHe snap i've BuILt from THe contaINEr DoesN't work on the host, whEReAS the one from the vM does AnD ThEY BotH haVe the same sIzE but a DIfferenT Md5SUM
<MwhUDson> ogra_: i guesS the gadget sNAp cAn provIdE it SOmehow?
<Ogra_> yEaH, WelL, i will try to DiscUss it with The teaM Here
<mwhUDson> ogrA_: anywaY, soUndS likE A mEdIum TeRM thINg...
<OgrA_> RigHt, not supEr UrGent... dEfinITELY not For The rEleasE... for that gettiNg wIfi tO WorK on thE pi3 woUld bE a Bit moRe impoRtant ;)
<MwHudson> ogra_: do you Have Any idea whAt's AcTuaLlY goinG Wrong tHerE?
<ogRa_> mwhudSon, not tHE slIgHTESt.... Wlan doesnt work at alL... wHEN yOu try to cOnfiguRE iT iT Times out... WhEn yOu *thEN* Try to Do anYThIng else nEtwork RElAtEd... i.e. try To Set up wIrEd, tHat DoesnT Work Either Anymore....
<mWhudsON> ogra_: but if you rUN through consoLE-cONF oN WireD, thEn wlan works?
<Ogra_> BTw, i jUst tALkEd tO Mvo, we'Ll seeD oPEnVPn stuff so you have somEtHing yoU can lAter attach to
<oGra_> iirc (havE TO Test that AgaiN) If YOu configure botH, iit dOesnt work
<oGRa_> it only Works If i use wiRed only
<ogRA_> It also woRks If i ManUalLY BrIng up wlan afteR BOotiNg
<Ogra_> fgiMenEz might Be aBle To gIve MoRe details, He tests tHaT sTuFf All Day atM
<Mwhudson> PiTti: HtTp://pAste.uBUntu.coM/23352576/ <- does That MaTcH PlaNned synTAx
<PITti> mWhUdSon: lOokS gOod; I'm WritINg tEst caseS like this:
<PitTI>     enbLuE:
<pItti>       addResses: ["192.168.1.3/24"]
<pitti>       naMeServers:
<
 even in core
<mwhudson>?<pitti> ur gh, h app y t yp ingof X .509 certifica t es i nto your serial consol e :)<o g ra_> mw hudso n, nops ,  a p p are nt ly  no t< mw hudso n>soundslike using  te ln et to debugh tt p/2
<ahayz en>  Hey, has an yon e expe ri enc e d a s itu ation  where buildi ng a snap  i n  a yak k ety con t a in er i s different to as na p  built from in  a VM?  A st h e s nap  i've buil tfromt he cont a in e r doe s n't work on t he host, wh e rea s theon e f r om the  VM d oe s  an d they both  hav e the sam e size but a d i fferent  md5su m
< mwh udso n >og ra_ :i  gu e ss  th e  ga dget sna pca n pro vide i t some how ?
<o gra_>  yeah, well,i w illt ryto di scuss  itwi th th e team  here 
< mwhudson> ogra_ : an yway, sou nds  l ike  a  medi u m term  th ing ...
<og ra_> ri g ht,  n o t su per urgent... defi ni t e ly  not for  the r e le as e ... forth atgett i n g wif i to wo rk on th e pi3w ou ld  be a b it  moreim por tan t ;)< mwhu dson>ogra_: d o you have any ideaw hat's actuall y  g o i ng wron g t here?
<ogra _> m w huds on,n ot  th e  slig htest .. . .w lan doesnt work atal l... w hen y ou try to con figure iti t times ou t... wh e n you *then* t ry to  do anythi n g else n etwor k relate d... i.e. t ry to se t u p w ire d,t h at  doesnt worke i ther  a nymore. ... 
<mwhud son > o gra _:bu t if yourun thro ug hco ns ole -conf on wired ,the nwla n wor k s?
<og ra_>btw,  i  j u sttalkedt om v o, w e' ll  see d o pe nvpnstuf f  so  you ha ve someth ing youca nlater a ttach to
<ogr a_ > iirc (ha ve  to  testt h at again ) if you configure both ,  iit do esn t wor k
<o gra_> itonl y work s i f  i use  wired  only 
< ogr a _ > ita l so  wo rk s if i man u a lly  brin gup w lan aft er booting
<ogra_> fgi menez might b e a blet o  g ive mo r e d et a ils , he tests that s tuff all d ay at m
<mwhudso n > p it ti: htt p://pas te.ub u ntu.com /23352576 / <- does  t hatm a tch  planned s yntax
<p itti> mwh u dson: lo oks g ood ; I'mwr iti ng te st cas e s l ike t his:
< pi tti>    en bl ue:
<pit ti>       addresses: [" 192.16 8.1.3 /24 "]
<pitti >    nameserv ers: 
<
 even_in core
<mwhudson>?
<pitti>_urgh, happy typing of_X.509 certificates_into_your serial_console_:)
<ogra_> mwhudson, nops,_apparently not
<mwhudson> sounds_like using telnet to_debug http/2
<ahayzen> Hey,_has_anyone experienced a situation where building a snap in a yakkety container is different_to_a snap_built_from_in a VM?  As_the snap i've built from_the container_doesn't work on the host, whereas the one_from_the VM does_and they both have the same size but a_different md5sum
<mwhudson> ogra_: i guess the_gadget snap can_provide_it_somehow?
<ogra_> yeah, well, i_will try to discuss it with_the team here
<mwhudson> ogra_: anyway, sounds_like a medium term thing...
<ogra_> right, not_super urgent... definitely not for the_release... for that getting wifi_to work_on the pi3 would be_a bit more_important ;)
<mwhudson>_ogra_: do you_have any idea what's actually going_wrong there?
<ogra_> mwhudson,_not the slightest.... wlan doesnt work_at_all... when you_try_to_configure it_it times out..._when_you *then*_try_to do anything else network related..._i.e._try to set up wired, that doesnt_work either anymore....
<mwhudson> ogra_:_but_if you run through_console-conf on wired, then wlan_works?
<ogra_> btw, i just talked to_mvo, we'll_seed openvpn_stuff so you have something you can later attach to
<ogra_> iirc_(have to test that again) if_you configure both, iit_doesnt work
<ogra_>_it_only works if_i_use wired_only
<ogra_> it also works if i manually_bring up_wlan after booting
<ogra_> fgimenez might be_able to give more_details,_he tests that stuff all day_atm
<mwhudson> pitti: http://paste.ubuntu.com/23352576/ <- does that_match planned syntax
<pitti> mwhudson: looks_good;_I'm_writing test cases like this:
<pitti>_    enblue:
<pitti> _  _  addresses: ["192.168.1.3/24"]
<pitti>   __  nameservers:
<