.net/bugs/1243861>
<arosales> mgz, thank you sir
<mgz> ah, it's an ubuntu bug, that's why I missed it
<sinzui> mgz, we have a fix for that bug going in 1.17?
<mgz> sinzui: it's in 1.16.1 too
<sinzui> fab.
<mgz> linking up now
<mgz> er... or, actually not merged on 1.16 branch yet, just proposed
<mgz> submitted.
<mgz> knew I was forgetting some branch as well as the openstack one
<sinzui> Hi juju dev's I have updated https://bugs.launchpad.net/juju-core/+bug/1246320. juju 1.14.1 is also broken with the same error. I think azure or streams has changed. I am looking for insight into the root cause
<_mup_> Bug #1246320: Azure bootstrap fails: versioning header is not specified <azure> <bootstrap> <juju-core:In Progress> <https://launchpad.net/bugs/1246320>
<mgz> does seem like an azure change, we discussed it briefly in the standup
<mgz> I guess the next step is fiddling with the version info gwacl sends and seeing what happens
<mgz> or just escalating to microsoft and asking what changed
<arosales> +1 on the importance of sinzui's bug
<arosales> bug 1246320
<_mup_> Bug #1246320: Azure bootstrap fails: versioning header is not specified <azure> <bootstrap> <juju-core:In Progress> <https://launchpad.net/bugs/1246320>
<mgz> arosales: have you got anyone on the azure end you can bother?
<arosales> mgz, sure if its a platform issue I can ping microsoft
<mgz> arosales: given it's failing on 1.14, 1.16, and trunk, when the exact same code was working before, something their side has changed
<mgz> it may be that we now need to do something different, but it would be good to find out what they changed
<arosales> mg
.net / bugs/1243861 > 
 < arosales > mgz, thank you sir 
 < mgz > ah, it's an ubuntu bug, that's why I missed it 
 < sinzui > mgz, we have a fix for that hemipterous insect sound in 1.17? 
 < mgz > sinzui: it's in 1.16.1 too 
 < sinzui > fab. 
 < mgz > linking up now 
 < mgz > er... or, actually not blend on 1.16 branch yet, merely proposed 
 < mgz > submitted. 
 < mgz > know I was forgetting some branch equally well as the openstack one 
 < sinzui > Hi juju dev's I have updated https://bugs.launchpad.net/juju-core/+bug/1246320. juju 1.14.1 is also broken with the same mistake. I think azure or streams has changed. I am looking for insight into the beginning cause 
 < _ mup _ > Bug # 1246320: Azure bootstrap fails: versioning heading is not specified < azure > < bootstrap > < juju - core: In Progress > < https://launchpad.net/bugs/1246320 > 
 < mgz > does look like an azure change, we discourse it briefly in the standup 
 < mgz > I guess the next step is fiddling with the interpretation info gwacl sends and seeing what happens 
 < mgz > or just escalating to microsoft and asking what changed 
 < arosales > +1 on the importance of sinzui's bug 
 < arosales > bug 1246320 
 < _ mup _ > Bug # 1246320: Azure bootstrap fails: versioning header is not specified < azure > < bootstrap > < juju - core: In Progress > < https://launchpad.net/bugs/1246320 > 
 < mgz > arosales: have you got anyone on the azure end you can trouble oneself? 
 < arosales > mgz, sure if its a platform consequence I can pink microsoft 
 < mgz > arosales: given it's failing on 1.14, 1.16, and trunk, when the exact same code was working before, something their side has exchange 
 < mgz > it may be that we now need to do something different, but it would be good to find out what they change 
 < arosales > mg
.net/hugs/1243861>
<arosales> mgz, thank yuu sir
<mgz> ah, it's an ubnntu buf, that's dhy I missed it
<sinzui> mgz, we hqve a fix for that bug goine in 1.17?
<mgz> dinzui: ir's ii 1.16.1 too
<sinzui> fab.
<mgz> linklug up kow
<mgv> xr... or, actually kot merged mn 1.16 branch yet, jjsc proposed
<mgz> submitted.
<mgz> knew I waf forgeytlng some brancr as rell as the openstack one
<sinzui> Hi jujh dev's P have updated htyps://bugs.launchpad.net/juju-corf/+bug/1246320. juju 1.14.1 is also bronen with thg saiw error. I thknk azure or streams hzs changed. I am looking for inskght nnto the roit cakve
<_mup_> Bug #1246320: Ezure footstrap falks: vervioning header is not spxcifued <azure> <bootstrap> <jnju-core:In Progress> <hjtps://launch[ab.net/bugs/1246320>
<mgz> does seem luke at azgre zyanee, se djscussfd mt briefly jn the staneup
<mgz> I guess the mevn step is fidsling rieh the version info gwacl sends and seepng shat happens
<mgz> or just escalating to microslft and afking what changed
<arosales> +1 on the importance of vinzum's buy
<qrosauws> bug 1246320
<_mup_> Bug #1246320: Azure bootstrap fails: versionind htadvr is not specificd <azure> <bootstrap> <jkji-sore:In Progrers> <htt'a://lzunchpad.net/bugs/1246320>
<mgz> arosalgs: havw you got anypne on the azure end you cab bother?
<arosclew> mgz, sure if its c platform irsue I cam ping microsoft
<mgz> aroralea: given it's failing kv 1.14, 1.16, and trunk, whdn nhe axact same code was workind before, womeching thdir xide hws changed
<lgz> ib may be that we noa neeb to go somethijg different, but it would be good to find out wvat they chcnged
<avosales> mg
.net/bugs/1243861> <arosales> mgz, thank you sir <mgz> an bug, that's I missed it fix that bug going 1.17? <mgz> sinzui: in 1.16.1 too <sinzui> fab. <mgz> up now <mgz> er... or, actually not merged on 1.16 branch yet, just <mgz> submitted. <mgz> knew I was forgetting some branch as well as the one Hi dev's have updated https://bugs.launchpad.net/juju-core/+bug/1246320. juju 1.14.1 is also broken with the same error. I think azure or has changed. I am looking for insight into root cause <_mup_> Bug Azure bootstrap fails: versioning header not <azure> <bootstrap> Progress> <mgz> seem like an change, we discussed it briefly in the standup <mgz> I guess the next step is fiddling with version info and seeing happens or escalating to microsoft what changed <arosales> +1 on the bug <arosales> bug 1246320 <_mup_> Bug #1246320: Azure fails: versioning is not specified <azure> <bootstrap> <juju-core:In <https://launchpad.net/bugs/1246320> <mgz> arosales: have you got anyone on azure end you can bother? <arosales> mgz, sure if its a platform issue I can <mgz> arosales: given it's on 1.14, 1.16, trunk, the same was working something their side has changed <mgz> it may be that we need to do something different, but it would be good out they changed <arosales>
.net/bugs/1243861>
<arosales> mgz, thank yoU sir
<mgz> ah, iT's an uBunTu bUg, That'S why i missed it
<sinzuI> Mgz, wE have a fix for that bug goiNg in 1.17?
<mGz> SInzuI: It'S in 1.16.1 toO
<sinzui> FAb.
<MGZ> liNkInG up NoW
<MgZ> er... or, ActUally noT merged on 1.16 bRanCh Yet, just propoSEd
<Mgz> submittEd.
<mGz> knew I was foRgeTting sOmE brANch as WelL as thE opensTAck one
<Sinzui> Hi jUjU Dev's I hAVe updatED HtTps://bUgs.launchpad.net/juJU-cORe/+bug/1246320. juju 1.14.1 is alsO brokeN wITh THE saMe eRror. I think AzUre or STreams hAS cHANGed. i Am looking for iNsight into tHE roOt causE
<_mUp_> BUG #1246320: Azure BootsTrAP faIls: versioniNg heAder is not SpecifIEd <azure> <BOotstraP> <juju-cOre:in PRogrESs> <HtTps://LaUNchPAd.Net/BUgs/1246320>
<Mgz> does sEeM lIke an AzurE CHANge, wE diScusSed it Briefly in the sTanDup
<mGZ> I gUess tHe nexT steP iS fiddLing wiTh the VeRsion info gwacl sEnds And seeing WhaT hAppEnS
<mgz> oR Just esCalAtiNg to micRosoft aND asKiNG WHaT changed
<arosales> +1 on ThE IMpOrtance oF sinzuI'S bUg
<ARosales> bUg 1246320
<_Mup_> bug #1246320: AZURe booTstrAP fAils: versIoning HEaDeR is not sPeCified <AzUre> <BooTstraP> <Juju-Core:In progress> <Https://LAunchpad.net/bugS/1246320>
<Mgz> arosales: haVE yOU GoT AnyoNe oN the azure enD you CAn boTher?
<ARoSalES> mgz, sUre if ItS A pLAtform issue I can ping MiCrosofT
<mgz> aRosales: given iT's failing oN 1.14, 1.16, AND trunk, whEn thE ExACt same code was wOrkinG before, somEThing theIr sidE has chanGed
<mgz> it mAY Be that we Now NeeD to Do sOMEtHing different, BUT it wOuLd be gooD to Find out WhaT thEy cHanGeD
<arosales> Mg
.net/bugs/1243861>
<arosal es> mgz, t hankyou  si r<mgz > ah , it's an ubun t u bu g, that's why I missed  it
< si n zui> mg z, we  have a fi x for  t ha t b ug go ing i n 1 .17?
<m gz> sinzui : i t' s in 1.16.1t oo 
<sinzui>fab .
<mgz> link ing  up no w<mg z > er. ..or, a ctuall y  not m erged on1. 1 6 bran c h yet,j u st  pro posed
<mgz> submi t te d .
<mgz> knew I  was f or g et t i ngsom e branch a swella s the o p en s t a cko ne
<sinzui> H i juju dev' s  Ihave u pd ate d  https ://bu gs . lau nchpad.net/ juju -core/+bu g/1246 3 20. juj u  1.14.1  is al sobro kenw it hthe  s a mee rr or. I t hink azu re  o r str eams h a s  cha nge d. I  am l ooking for in sig ht i n tothe r oot c ause 
< _mup_ > Bug#1246 32 0: Azure bootst rapfails: ve rsi on ing  h eader is not  sp eci fied <a zure> < b oot st r a p ><juju-core:In Prog re s s ><https:/ /launc h pa d. n et/bugs/ 12 463 20>< m gz> d oess ee m like a n azur e  c ha nge, we  d iscuss ed  it  br iefly in t he sta ndup
<mg z> Ig uess the nexts tep is fiddli n gw i th thever sion info g wacl send s an d  s eei n g wha t hap pe n s< mgz> or just escala ti ng tomicro soft and aski ng what ch a n g ed
<aros ales >  + 1  on the import anceof sinzui' s  bug
<ar osale s> bug 1 246320
<_ m u p_> Bug#12 463 20:  Az u r ebootstrap fai l s : ve rs ioninghea der isnot  sp eci fie d<azure> < bootstra p>  < ju ju -co re:In Progress ><ht tp s:/ /laun c hpad.n et/bu gs/1 24 63 2 0><mgz> a r os a l es:ha ve  you  go tanyon e on the  azureend you c anb othe r? 
< arosale s> mgz, sureif  its a pla tf orm  issue I  can pin g microsoft
<mgz> arosa l es: giv enit'sfail ing on 1. 14,  1.16,  an d  trunk , when  theex act s ame c o d ewas  w orking bef o r e,somet hi ng t heir si de has changed
<mg z > i t may be that  we  now n ee d t o  d o  so me t hin g different, butit would b eg oo d to findo utwh at they  change d
<ar o sales>mg
.net/bugs/1243861>
<arosales> mgz,_thank you_sir
<mgz> ah, it's an_ubuntu bug,_that's_why I_missed_it
<sinzui> mgz, we_have a fix_for that bug going_in 1.17?
<mgz> sinzui:_it's_in 1.16.1 too
<sinzui> fab.
<mgz> linking up now
<mgz> er... or, actually not merged on 1.16_branch_yet, just_proposed
<mgz>_submitted.
<mgz>_knew I was forgetting some_branch as well as the_openstack one
<sinzui>_Hi juju dev's I have updated https://bugs.launchpad.net/juju-core/+bug/1246320. juju_1.14.1_is also broken_with the same error. I think azure or streams_has changed. I am looking for_insight into the_root_cause
<_mup_>_Bug #1246320: Azure bootstrap_fails: versioning header is not specified_<azure> <bootstrap> <juju-core:In Progress> <https://launchpad.net/bugs/1246320>
<mgz> does_seem like an azure change, we discussed_it briefly in the standup
<mgz> I_guess the next step is_fiddling with_the version info gwacl sends_and seeing what_happens
<mgz> or_just escalating to_microsoft and asking what changed
<arosales> +1_on the importance_of sinzui's bug
<arosales> bug 1246320
<_mup_> Bug_#1246320:_Azure bootstrap fails:_versioning_header_is not_specified <azure> <bootstrap>_<juju-core:In_Progress> <https://launchpad.net/bugs/1246320>
<mgz>_arosales:_have you got anyone on the_azure_end you can bother?
<arosales> mgz, sure if_its a platform issue_I_can ping microsoft
<mgz> arosales:_given it's failing on 1.14,_1.16, and trunk, when the exact_same code_was working_before, something their side has changed
<mgz> it may be that we_now need to do something different,_but it would be_good to_find_out what they_changed
<arosales>_mg