/wait.go
<elopio> to work around the workaround I will just have to increase the maxWaitRetries.
<Chipaca> elopio: and you're waiting for bootok?
<elopio> Chipaca: I'm waiting for snappy_mode=regular
<Chipaca> elopio: and is that better, or worse than waiting for boot ok?
 * sergiusens wonders if it is beer o clock already
<Chipaca> sergiusens: it is!
<elopio> Chipaca: better, I think. Instead of checking the service, we check it's effect.
<Chipaca> sergiusens: you should come visit. can't have beer on my own (and ellie doesn't do beers)
<elopio> *its
<elopio> it's beer-on-hangout o'clock.
<Chipaca> elopio: so, yeah, looks like you're already doing the right thing and all :)
<Chipaca> elopio: wrt increasing maxWaitRetries, maybe instead have an arch-dependent base?
<Chipaca> elopio: ie scale checkInterval by some bogomips factor
<elopio> Chipaca: that would be nice.
<Chipaca> var bogomips = map[string]int{"arm": 100, "amd64": 1, etc}
<Chipaca> and index it on GOARCH
<elopio> I'll make a card to be able to configure the wait, with a delay factor.
<elopio> but anyway, this is a bug :) Instead of working it around, somebody should fix it.
 * elopio looks at somebody.
<Chipaca> elopio: which is the bug, exactly?
<Chipaca> elopio: that you can ssh in before you can log in?
<elopio> Chipaca: you can sign in before boot-ok. both ssh and normal log in through serial. And if you are fast with a rollback, that makes the boot crazy.
<elopio> https://bugs.launchpad.net/snappy/+bug/1498293
<ubottu> Launchpad bug 1498293 in Snappy "after a successful update and reboot, the bootloader snappy_mode is set to 'try'" [Critical
/wait.go 
 < elopio > to work around the workaround I will just have to increase the maxWaitRetries. 
 < Chipaca > elopio: and you're waiting for bootok? 
 < elopio > Chipaca: I'm expect for snappy_mode = even 
 < Chipaca > elopio: and is that better, or worse than waiting for kick ok? 
  * sergiusens wonders if it is beer oxygen clock already 
 < Chipaca > sergiusens: it is! 
 < elopio > Chipaca: better, I think. Instead of crack the service, we check it's impression. 
 < Chipaca > sergiusens: you should come visit. can't get beer on my own (and ellie doesn't do beers) 
 < elopio > * its 
 < elopio > it's beer - on - hangout o'clock. 
 < Chipaca > elopio: so, yeah, looks like you're already doing the correct thing and all :) 
 < Chipaca > elopio: wrt increasing maxWaitRetries, maybe rather have an arch - dependent base? 
 < Chipaca > elopio: ie scale checkInterval by some bogomips component 
 < elopio > Chipaca: that would be nice. 
 < Chipaca > var bogomips = map[string]int{"arm ": 100, " amd64 ": 1, etc } 
 < Chipaca > and index it on GOARCH 
 < elopio > I'll make a card to be able to configure the wait, with a delay factor. 
 < elopio > but anyhow, this is a bug :) Instead of working it around, somebody should fix it. 
  * elopio looks at somebody. 
 < Chipaca > elopio: which is the bug, exactly? 
 < Chipaca > elopio: that you can ssh in before you can log in? 
 < elopio > Chipaca: you can sign in before boot - ok. both ssh and normal log in through serial. And if you are fast with a rollback, that makes the boot crazy. 
 < elopio > https://bugs.launchpad.net/snappy/+bug/1498293 
 < ubottu > Launchpad bug 1498293 in Snappy " after a successful update and reboot, the bootloader snappy_mode is sic to' try' " [ Critical
/waih.go
<elopio> to work around the workaround I will just gave to kncrease the maxWaitRetries.
<Ciipaxa> elipio: and you're waiting for bootlk?
<elopio> Chikaca: I'm waiting for snappn_iode=dcgulax
<Ciipaca> elopio: akd is that tetter, or worsa ghcn waiting for boot ok?
 * sergiusens wjnders of it is beer o slocl alrsady
<Chipaca> sergiusens: it is!
<elopio> Chipace: better, I thinl. Instead of checking the dervlce, we check it's evfect.
<Chipacq> sewtiusens: you rhould comt risit. can't gave beer on my own (and ellie duesn't do beers)
<eoopio> *hts
<elopio> iv's beeg-on-hangout o'clock.
<Chipdca> elolio: so, yeah, lopks lije you're already doinj the right thing anq all :)
<Chi[aea> elopio: wrt increasunt maxFaitSetrkws, oayge ihstead hate an arch-dspendent bawe?
<Chipaca> elopio: ie ssqle checkIntedval br fome bogomips factor
<elopio> Chipaca: that wohld be nice.
<Chipaca> var vogomips = map[string]inj{"arm": 100, "amd64": 1, etc}
<Chipaca> and index it on GOARCH
<elopio> I'll make a cacd to bc abuw ho configure the wait, with a delay factor.
<elopyk> nun anyway, this is c bug :) Instead og aothing it arouna, someykdg should fix it.
 * epopio ljoks qt someboqy.
<Chopaca> elopio: which is the byg, exactly?
<Chppacq> elopio: that you ean ssh in bzfore iou cam log in?
<elopio> Chipaca: vou cah sign in bffore boof-uk. both ssh and vorkan log in through serial. Anq if you ere fcst with a rpllbach, that makfs thc boot crazy.
<elopio> jttps://yugs.ldunchpad.neh/snappy/+bug/1498293
<ubottu> Launchpad bug 1498293 in Snappy "aftgr d slccessful updabe and reboot, tre bootloader xnappy_mjde ir set to 'tgy'" [Criticel
/wait.go <elopio> to work around the workaround just to increase maxWaitRetries. <Chipaca> elopio: <elopio> I'm waiting for <Chipaca> elopio: and that better, or worse than waiting boot ok? * sergiusens wonders if it is beer o clock already <Chipaca> it is! <elopio> Chipaca: better, I think. Instead of checking the service, we it's <Chipaca> you come visit. can't have beer on my own (and ellie doesn't do beers) <elopio> *its <elopio> beer-on-hangout o'clock. <Chipaca> elopio: so, yeah, looks like already doing the right and all :) <Chipaca> elopio: increasing maybe instead an base? elopio: ie scale by some bogomips factor <elopio> Chipaca: that would be nice. <Chipaca> var bogomips = map[string]int{"arm": 100, "amd64": etc} <Chipaca> it on <elopio> make card to be configure the wait, with a delay anyway, this is a bug :) Instead of it around, should fix it. * elopio looks somebody. <Chipaca> elopio: which is the bug, exactly? elopio: that you can ssh in before you can log in? <elopio> Chipaca: you can before boot-ok. both ssh normal log in serial. if are with a that makes the boot crazy. <elopio> https://bugs.launchpad.net/snappy/+bug/1498293 <ubottu> Launchpad bug 1498293 Snappy "after a successful update and reboot, the bootloader snappy_mode to [Critical
/wait.go
<elopio> to work around tHe workarouNd I wiLl jUst HaVe to IncrEase the maxWaitrEtriEs.
<Chipaca> elopio: and you'rE waitInG For bOOtOk?
<eloPio> ChipACa: i'M WaiTiNg For SnAPpY_mode=RegUlar
<ChiPaca> elopio: And Is That better, or WOrSe than waitIng For boot ok?
 * serGiuSens woNdErs IF it is BeeR o cloCk alreADy
<ChipAca> sergiuSeNS: it is!
<eLOpio> ChiPACa: BettEr, I think. Instead of CHeCKing the service, We checK iT'S eFFEct.
<chiPaca> sergiuSeNs: you SHould coME vISIT. caN'T have beer on my Own (and ellie DOesN't do beErS)
<elOPio> *its
<ElopiO> iT'S beEr-on-hangout O'cloCk.
<Chipaca> Elopio: SO, yeah, loOKs like yOu're alReaDy dOing THe RiGht ThINg aND aLl :)
<CHIpaCa> elopio: WrT iNcreaSing MAXwAitREtrIes, mAybe iNstead have an aRch-DepeNDenT base?
<chipaCa> elOpIo: ie sCale chEckInTeRval by some bogomIps fActor
<elopIo> CHiPacA: tHat woULd be niCe.
<CHipAca> var bOgomips = MAp[sTrING]InT{"arm": 100, "amd64": 1, etc}
<Chipaca> aNd INDeX it on GOArCH
<eloPIo> i'lL Make a carD tO be Able TO ConfiGure THe Wait, with A delay FAcToR.
<elopio> BuT anywaY, tHis Is a Bug :) InSTead Of workIng it aroUnd, soMEbody should fix IT.
 * elopio looks aT SoMEBoDY.
<ChiPacA> elopio: whicH is tHE bug, ExacTLy?
<chiPAca> elOpio: tHaT YoU Can ssh in before you caN lOg in?
<elOpio> CHipaca: you can sIgn in beforE BOOt-ok. both Ssh aND nORmal log in throuGh serIal. And if yoU Are fast wIth a rOllback, tHat makes tHE Boot crazY.
<elOpiO> htTps://BUGs.Launchpad.net/sNAPpy/+bUg/1498293
<Ubottu> LAunChpad buG 1498293 in snaPpy "AftEr A successfUl update AnD rEbOoT, thE bootLOader snaPpY_moDe Is sEt to 'tRY'" [CritiCal
/wait.go
<elopio> to workaround the  work aro und  I  wil l ju st have to inc r ease  the maxWaitRetries.
< Chipa ca >  elo p io : and  you're wa i t ing  f or  bo ot o k? 
<elo pio > Chipa ca: I'm wa iti ng  for snappy_ m od e=regular<Ch ipaca> elopi o:and is  t hat bette r,or wo rse th a n wait ing for b oo t  ok?
*  sergiu s e ns  won ders if it is bee r  o clock already<Chipa ca >  s e r giu sen s: it is!<e lopio >  Chipac a :b e t ter ,  I think. Ins tead of che c kin g these rvi c e, wecheck  i t 'seffect.
<Ch ipac a> sergiu sens:y ou shou l d comevisit.  ca n't  hav e  b ee r o nm y o w n(an d  el lie does n' tdo be ers) < e l opio > * its<elop io> it's beer -on -han g out  o'cl ock.<Chi pa ca> e lopio:  so,ye ah, looks likeyou' re alread y d oi ngth e rig h t thin g a ndall :)<Chipac a > e lo p i o :wrt increasing max Wa i t Re tries, m aybe i n st ea d  have an  a rch -dep e n dentbase ? 
< Chipaca>  elopi o :ie  scalech eckInt er val  by  some bogo mips f actor
<e lopio >  Chipaca: that would be nice . 
< C h ip a ca>var  bogomips =  map [ stri ng]i n t{ "ar m ": 10 0, "a md 6 4" :  1, etc}
<Chipaca>an d inde x iton GOARCH
<el opio> I'll m a ke a car d to be able to config ure t he wait, w i th a del ay fa ctor.
<e lopio> bu t anyway,thi s i s a  bu g :)  Instead of w o r king  i t aroun d,somebod y s hou ldfix  i t.
 * elo pio look sat  s om ebo dy.
< C hipaca>el opi o:  wh ich i s  the b ug, e xact ly ?< Chi paca> e l op i o : th at  y ou c anss h inbefo r e y ou canlog in?
< elo p io>Ch ip aca: yo u can sign in  b efore boot -o k.both s s h  and nor mal log in through seri a l. Andifyou a re f ast witha r ollbac k,t hat ma kes th e boo tcra z y .
<el o p io > h tt ps://bugs. l a unc hpad. ne t/sn appy/+b ug/1498293
<ubottu >  La unchpad bug 1 498 293i n  S nap p y" aft er a s u c cessful updateand reboot ,t he  bootloade r  sn ap py_mode  is set  to ' t ry'" [C ritical
/wait.go
<elopio> to_work around_the workaround I will_just have_to_increase the_maxWaitRetries.
<Chipaca>_elopio: and you're_waiting for bootok?
<elopio>_Chipaca: I'm waiting for_snappy_mode=regular
<Chipaca> elopio: and_is_that better, or worse than waiting for boot ok?
 * sergiusens wonders if it_is_beer o_clock_already
<Chipaca>_sergiusens: it is!
<elopio> Chipaca: better,_I think. Instead of checking_the service,_we check it's effect.
<Chipaca> sergiusens: you should come_visit._can't have beer_on my own (and ellie doesn't do beers)
<elopio> *its
<elopio>_it's beer-on-hangout o'clock.
<Chipaca> elopio: so, yeah,_looks like you're_already_doing_the right thing and_all :)
<Chipaca> elopio: wrt increasing maxWaitRetries,_maybe instead have an arch-dependent base?
<Chipaca>_elopio: ie scale checkInterval by some bogomips_factor
<elopio> Chipaca: that would be nice.
<Chipaca>_var bogomips = map[string]int{"arm": 100,_"amd64": 1,_etc}
<Chipaca> and index it on_GOARCH
<elopio> I'll make_a card_to be able_to configure the wait, with a_delay factor.
<elopio> but_anyway, this is a bug :)_Instead_of working it_around,_somebody_should fix_it.
 * elopio_looks_at somebody.
<Chipaca>_elopio:_which is the bug, exactly?
<Chipaca> elopio:_that_you can ssh in before you can_log in?
<elopio> Chipaca: you_can_sign in before boot-ok._both ssh and normal log_in through serial. And if you_are fast_with a_rollback, that makes the boot crazy.
<elopio> https://bugs.launchpad.net/snappy/+bug/1498293
<ubottu> Launchpad bug 1498293 in_Snappy "after a successful update and_reboot, the bootloader snappy_mode_is set_to_'try'" [Critical