?
<sinzui> I am
<thumper> sinzui: I have a critical bug
<thumper> sinzui: for 1.16
<thumper> sinzui: it is the lxc and maas problem
<thumper> that they are using for ods
<thumper> demo
<thumper> always last minute
<thumper> it is a regression introduced when the provisioner moved to the api
<sinzui> I just cut 1.16.1, but plan a 1.16.2 for azure.
<thumper> but no one noticed
<sinzui> thumper, Do I need to take down 1.16.1
<thumper> no
<thumper> I don't think so
<thumper> because they can use a custom release
<thumper> I think
<thumper> but we may have a 1.16.2 real soon now
<thumper> if they do need a release
<thumper> what's the timeframe for 1.16.2?
<thumper> bigjools: I have a plan
<sinzui> I can make it tomorrow immediately after 1.16.1 is needed. I hope for an azure fix of couse
 * thumper nods
<thumper> ok
<thumper> let me file this bug and get to work
 * sinzui creates milestone
<wallyworld_> sinzui: azure fix will be commited to gwacl today i hope
<sinzui> wallyworld_, excellent. Testing will be quick since it is limited to two providers
<wallyworld_> i'm doing a local test now
<sinzui> Did I mention abentley got rudimentary CI running on HP. we can run about 200 upgrade and bootstrap tests a day
<wallyworld_> ran into the precise mongo thing i think
<wallyworld_> trying on saucy
<thumper> wallyworld_: are you chasing the azure issue?
<thumper> wallyworld_: is there a bug?
<wallyworld_> yes. the issue is with msft, not us
<wallyworld_> we need to change gwacl cause they broke the api
<wallyworld_> i'm testing now
<thumper> :)
<
? 
 < sinzui > I am 
 < thumper > sinzui: I have a critical bug 
 < thumper > sinzui: for 1.16 
 < thumper > sinzui: it is the lxc and maas problem 
 < thumper > that they are using for doctor of optometry 
 < thumper > demo 
 < thumper > constantly last minute 
 < thumper > it is a regression introduce when the provisioner moved to the api 
 < sinzui > I merely cut 1.16.1, but plan a 1.16.2 for azure. 
 < thumper > but no one detect 
 < sinzui > thumper, Do I need to take down 1.16.1 
 < thumper > no 
 < thumper > I don't intend so 
 < thumper > because they can use a customs release 
 < thumper > I think 
 < thumper > but we may have a 1.16.2 real soon now 
 < thumper > if they do need a release 
 < thumper > what's the timeframe for 1.16.2? 
 < thumper > bigjools: I suffer a plan 
 < sinzui > I can make it tomorrow immediately after 1.16.1 is needed. I hope for an azure localization of couse 
  * thumper nods 
 < thumper > ok 
 < thumper > let me file this bug and scram to work 
  * sinzui creates milestone 
 < wallyworld _ > sinzui: azure fix will be commited to gwacl today i hope 
 < sinzui > wallyworld _, excellent. Testing will be immediate since it is limited to two providers 
 < wallyworld _ > i'm doing a local test now 
 < sinzui > Did I mention abentley got rudimentary CI running on HP. we can run about 200 upgrade and bootstrap tests a day 
 < wallyworld _ > ran into the precise mongo matter i remember 
 < wallyworld _ > trying on saucy 
 < thumper > wallyworld _: are you furrow the azure consequence? 
 < thumper > wallyworld _: is there a bug? 
 < wallyworld _ > yes. the issue is with msft, not us 
 < wallyworld _ > we need to transfer gwacl cause they broke the api 
 < wallyworld _ > i'm testing now 
 < thumper > :) 
 <
?
<sinxui> I am
<thumper> sinzui: I have a critical bug
<thnmper> sjnzui: fof 1.16
<thumper> sinzui: it is the lec abd maqs problem
<thumper> that they are using fir ovs
<thumper> demo
<thnjper> always lzdt mnnnte
<thumper> it ix a regresvion introduceg dhzn the provisioner moved to the api
<synzui> I jkst cut 1.16.1, but pjan s 1.16.2 fod azure.
<thumper> but no one noticed
<sjnzui> tiumper, Do I neec to take down 1.16.1
<thumper> no
<tjumpfr> I don't think so
<hhumper> becquse rhey can use a custom gzlease
<thumpgr> I think
<thumper> but we may havd a 1.16.2 xeal soon niw
<rhulker> if they vo neeq a release
<tmlmper> wvat's thr timeframe fov 1.16.2?
<thukpee> bigjools: I have a pnan
<sinzui> I can mahe it tommrxow immediately after 1.16.1 us negded. H hoow fur zn aaure flx kf couse
 * fhumper nodw
<thumper> ok
<thumper> kee me file this bug agd get to work
 * sinzui creates milestone
<wdllgworld_> sinzui: azure fix will be commited to hwacl todwy i hope
<sinzui> wallyworld_, excellent. Testing will be qnizk wikce kr ls limited to two providers
<wallyworld_> i'm doind a lpcal test now
<slnzui> Did I mentiom wbrgtley got rudkmentaxg DI running on HP. wf can ron aboyt 200 upgraqe amd bootstrap tests a day
<waloyworld_> ran pnto the precise mongo thing i thnnk
<walkyworkd_> trying on saucy
<thumpzr> walmyworld_: are you chasjvg the azure issje?
<tmum[er> wallyworld_: is there a fug?
<wallywirld_> yes. thd isxue is with msft, not mv
<wallyworld_> we neef to ehanga gwacl cakse they broke the api
<wallyworlv_> i'm testing mof
<thlmper> :)
<
? <sinzui> I am <thumper> sinzui: I critical <thumper> sinzui: 1.16 <thumper> sinzui: maas <thumper> that they using for ods demo <thumper> always last minute <thumper> is a regression introduced when the provisioner moved to the api <sinzui> I cut 1.16.1, but plan a 1.16.2 for azure. <thumper> but no one noticed thumper, I to down 1.16.1 <thumper> no <thumper> I don't think so <thumper> because they can use a custom <thumper> I think <thumper> but we may have 1.16.2 real soon now if they do need a <thumper> the timeframe 1.16.2? bigjools: have a plan I can make it tomorrow immediately after 1.16.1 is needed. I hope for an azure fix of * thumper ok <thumper> me this and get to sinzui creates milestone <wallyworld_> sinzui: azure commited to gwacl today i hope <sinzui> wallyworld_, Testing will quick since it is limited to providers <wallyworld_> i'm doing a local test now Did I mention abentley got rudimentary CI running on HP. we can run about 200 bootstrap tests a day ran into the mongo i <wallyworld_> on saucy wallyworld_: are you chasing the azure issue? <thumper> wallyworld_: is there bug? <wallyworld_> yes. the issue is with msft, not us need change gwacl cause broke the api <wallyworld_> testing <thumper> :) <
?
<sinzui> I am
<thumper> sinzui: I haVe a criticaL bug
<tHumPer> SiNzui: For 1.16
<tHumper> sinzui: it IS the Lxc and maas problem
<thumpEr> thaT tHEy arE UsIng foR ods
<thuMPeR> DEmo
<ThUmPer> AlWAyS last MinUte
<thumPer> it is a reGreSsIon introduceD WhEn the proviSioNer moved to thE apI
<sinzuI> I JusT Cut 1.16.1, buT plAn a 1.16.2 foR azure.
<THumper> But no one nOtICed
<sinZUi> thumpER, do i neeD to take down 1.16.1
<thumpeR> No
<THumper> I don't thiNk so
<thUmPEr> BECauSe tHey can use a CuStom rELease
<thUMpER> i ThiNK
<thumper> but we May have a 1.16.2 reaL SooN now
<thUmPer> IF they dO need A rELeaSe
<thumper> whAt's tHe timefraMe for 1.16.2?
<tHUmper> biGJools: I hAve a plAn
<sInzUi> I cAN mAkE it ToMOrrOW iMmeDIatEly after 1.16.1 Is NeEded. I Hope FOR AN azuRe fIx of Couse
 * Thumper nods
<thUmpEr> ok
<THumPer> leT me fiLe thIs Bug anD get to Work
 * sInZui creates milesTone
<WallyworlD_> siNzUi: aZuRe fix WIll be cOmmIteD to gwacL today i HOpe
<SiNZUI> wAllyworld_, excellent. teSTInG will be qUick siNCe It IS limited To Two ProvIDErs
<waLlywORlD_> i'm doing A local TEsT nOw
<sinzuI> DId I menTiOn aBenTley gOT rudImentaRy CI runnIng on hp. we can run about 200 UPgrade and bootSTrAP TeSTs a dAy
<wAllyworld_> raN intO The pReciSE mOngO Thing I thinK
<wALlYWorld_> trying on saucy
<tHuMper> waLlywoRld_: are you chasIng the azurE ISSue?
<thumpEr> waLLyWOrld_: is there a buG?
<wallYworld_> yes. tHE issue is With mSft, not us
<WallyworlD_> WE need to cHanGe gWacL caUSE tHey broke the apI
<WAllyWoRld_> i'm teStiNg now
<thUmpEr> :)
<
?
<sinzui> I am
<thumper>sinzui: Ihavea c rit ic al b ug
< thumper> sinzu i : fo r 1.16
<thumper> sinzu i: it  i s  the lx c and  maas p r ob l e m
< th um per >t ha t the y a re usin g for ods<th um per> demo
<t h um per> alway s l ast minute
< thu mper>it  is a reg res sionintrod u ced wh en the pr ov i sioner moved t o th e ap i
<sinzui> I just cu t  1.16.1, but p lan a1. 1 6. 2 for  az ure.
<thum pe r> bu t  no one no t i c ed< sinzui> thump er, Do I ne e d t o take  d own 1.16.1 
<thu mp e r>no
<thumper > Idon't thi nk so< thumper >  becaus e they  ca n u se a cu st omre l eas e 
< thu m per > I thin k<t humpe r> b u t w e ma y h avea 1.1 6.2 real soon  no w
<t h ump er> i f the y do  n eed a  relea se
<t hu mper> what's th e ti meframe f or1. 16. 2? 
<thu m per> b igj ool s: I ha ve a pl a n
< si n z u i>  I can make it tom or r o wimmediat ely af t er  1 . 16.1 isne ede d. I h ope f or a n  a zure fix  of co u se 
* thump er  nods<t hum per > ok< thum per> l et me fi le th i s bug and gett o work
 * sin z ui c re a tesmil estone
<wal lywo r ld_>  sin z ui : a z ure f ix wi ll be commited to gwacl t od ay i h ope
< sinzui> wally world_, ex c e l lent. Te stin g  w i ll be quick si nce i t is limit e d to two  prov iders
<w allyworld _ >  i'm doi nga l oca l t e s tnow
<sinzui>D i d Ime ntion a ben tley go t r udi men tar yCI runnin g on HP.  w eca nrun  abou t  200 upg ra dean d b ootst r ap tes ts aday<w al l ywo rld_> r a ni n to t he  p reci semo ngo t hing i t hink
<w allyworld _>t ryin gon  saucy<thumper> wal ly world_: ar eyou  chasi n g  the azu re issue?
<thumper> wal l yworld_ : i s the re a  bug?
<wa lly world_ > y e s. the  issue  is w it h m s f t, no t us 
<w al lyworld_>w e  ne ed to  c hang e gwacl  cause they broket heapi
<wallywor ld_ > i' m te sti n gn ow<t h ump e r > :)
<
?
<sinzui> I_am
<thumper> sinzui:_I have a critical_bug
<thumper> sinzui:_for_1.16
<thumper> sinzui:_it_is the lxc_and maas problem
<thumper>_that they are using_for ods
<thumper> demo
<thumper>_always_last minute
<thumper> it is a regression introduced when the provisioner moved to the api
<sinzui>_I_just cut_1.16.1,_but_plan a 1.16.2 for azure.
<thumper>_but no one noticed
<sinzui> thumper,_Do I_need to take down 1.16.1
<thumper> no
<thumper> I don't_think_so
<thumper> because they_can use a custom release
<thumper> I think
<thumper> but we_may have a 1.16.2 real soon_now
<thumper> if they_do_need_a release
<thumper> what's the_timeframe for 1.16.2?
<thumper> bigjools: I have_a plan
<sinzui> I can make it_tomorrow immediately after 1.16.1 is needed. I_hope for an azure fix of_couse
 * thumper nods
<thumper> ok
<thumper>_let me_file this bug and get_to work
 *_sinzui creates_milestone
<wallyworld_> sinzui: azure_fix will be commited to gwacl_today i hope
<sinzui>_wallyworld_, excellent. Testing will be quick_since_it is limited_to_two_providers
<wallyworld_> i'm_doing a local_test_now
<sinzui> Did_I_mention abentley got rudimentary CI running_on_HP. we can run about 200 upgrade_and bootstrap tests a_day
<wallyworld_>_ran into the precise_mongo thing i think
<wallyworld_> trying_on saucy
<thumper> wallyworld_: are you chasing_the azure_issue?
<thumper> wallyworld_:_is there a bug?
<wallyworld_> yes. the issue is with msft, not_us
<wallyworld_> we need to change gwacl_cause they broke the_api
<wallyworld_> i'm_testing_now
<thumper> :)
<