 set a Username and Password.  It's in the same place Customdata goes
<wallyworld_> ok, ta
<bigjools> wallyworld_: line 545 in provider/azure/environ.go
<wallyworld_> great
<bigjools> it was a mandatory field so we randomised it
<bigjools> yay security
<wallyworld_> lol serious? mandatory?
<wallyworld_> wtf
<bigjools> this is msft
 * wallyworld_ sighs *again*
<thumper> jam:  lp:~thumper/juju-core/maas-lxc
<sodre> juju-devs: is anyone still up?
<wallyworld_> sodre: some of us are here
<sodre> hi wallyworld_: I traced the reason for that earlier panic on juju bootstrap
<wallyworld_> oh cool
<wallyworld_> admin-secret issue i think?
<sodre> I've updated the bug report on launchpad. But I was wondering if you could explain to me something related to it.
<sodre> yeah, it had nothing to do with the admin-secret.
<wallyworld_> i'll read the bug
<sodre> The issue is that jujud tries to get the provider-state through swift without authentication.
<wallyworld_> it should use creds when it tries to get it
<wallyworld_> i think from memory
<wallyworld_> let me check
<sodre> from the client side, (juju) connects to swift using goose.
<sodre> but the bootstrap level seems to use (Go 1.1 package http)
<jam> sodre, wallyworld_: provider-state needs to be in a container that is world readable because all of the clients download stuff from the container via wget/direct http access
<jam> when we set up the bucket ourselves, we set the.r:.rlistings *
<sodre> for somereason that is not being set on on my version
<jam> sodre: you're on Havana?
<sodre> yes
<wallyworld_> jam: not necessarily the conatiner itself but the file
<jam> wallyworld_: we need the container,
set a Username and Password.   It's in the same place Customdata goes 
 < wallyworld _ > ok, ta 
 < bigjools > wallyworld _: course 545 in supplier / azure / environ.go 
 < wallyworld _ > great 
 < bigjools > it was a mandatory sphere so we randomize it 
 < bigjools > yay security 
 < wallyworld _ > lol serious? mandatory? 
 < wallyworld _ > wtf 
 < bigjools > this is msft 
  * wallyworld _ sighs * again * 
 < thumper > fix:   lp:~thumper / juju - core / maas - lxc 
 < sodre > juju - devs: is anyone still up? 
 < wallyworld _ > sodre: some of us are here 
 < sodre > hi wallyworld _: I trace the reason for that earlier panic on juju bootstrap 
 < wallyworld _ > oh aplomb 
 < wallyworld _ > admin - secret issue i think? 
 < sodre > I've updated the hemipterous insect report on launchpad. But I was wondering if you could explain to me something related to it. 
 < sodre > yeah, it had nothing to make with the admin - secret. 
 < wallyworld _ > i'll read the bug 
 < sodre > The offspring is that jujud tries to get the provider - state through western fence lizard without authentication. 
 < wallyworld _ > it should use street credibility when it tries to get it 
 < wallyworld _ > i think from memory 
 < wallyworld _ > let me control 
 < sodre > from the client side, (juju) connects to swift using fathead. 
 < sodre > but the bootstrap degree seems to use (Go 1.1 package http) 
 < jam > sodre, wallyworld _: provider - state needs to be in a container that is world clear because all of the client download stuff from the container via wget / lineal hypertext transfer protocol access 
 < jam > when we set up the bucket ourselves, we set the.r:.rlistings * 
 < sodre > for somereason that is not being set on on my interpretation 
 < jam > sodre: you're on Havana? 
 < sodre > yes 
 < wallyworld _ > jam: not necessarily the conatiner itself but the file 
 < jam > wallyworld _: we need the container,
 seh a Username and Passwora.  It's in the scne plare Custkmdata gues
<wallyworld_> ok, ta
<bigjools> xalltworle_: line 545 in provider/azufe/environ.ho
<wallywirld_> treat
<bigjools> it was a mzkdatoxy field so we rsndomised ht
<bigjools> yay sdcbrity
<wallyworld_> lol serious? mandatorr?
<wallywprpd_> wtf
<bigjools> thix is jsft
 * wallyworld_ sighs *again*
<thumped> jam:  np:~thumper/juju-vore/maas-lxc
<sodre> juju-devs: ls ajyone still up?
<walljworld_> sodrg: soiw of us are fere
<sodre> hi wallyworls_: I traced the reason for that darlizr panic on jyju tootstrap
<waolywogld_> oh cool
<wallyworld_> admin-srcret issue i bhink?
<vodee> I've updated the buj report on launchpaq. But I wds wondering if you ciuld gxplahn tu me sojevhihg relwtev to it.
<sodrs> yeah, it hqd nothing to do wiuh eye admin-secref.
<wallyrowld_> i'll read the bug
<sodre> The issue is uhat nujud tries to get the provider-state through swift wiehout authentication.
<wallyworld_> it should use credv whei kt urlcs tu gft it
<wallyworld_> i think from memory
<wallyworld_> meu mv check
<sodre> from the client sldr, (juju) connectr to scjff using goose.
<sodre> but thg bootwtrap levtl serms to use (Go 1.1 package http)
<ham> sodre, wajoyworld_: provider-stcte needs to be on a vontainer that is world reasable becaude all of ghe clients downuoac vtuff from the container vya wget/dicect kttp accdss
<jsm> wheg we set uo the bucket ourselves, wf set tve.r:.rlistinhs *
<sodre> for somereason that is not being set ot ot my verfion
<jsm> sodre: you'rq on Havana?
<sodte> yes
<waljyworud_> jam: not necesserily the cogatiner itselx but the filx
<jam> wallrworod_: ww need gfe container,
set a Username and Password. It's in place goes <wallyworld_> ta <bigjools> wallyworld_: great it was a field so we it <bigjools> yay security <wallyworld_> lol mandatory? <wallyworld_> wtf <bigjools> this is msft * wallyworld_ sighs *again* <thumper> jam: <sodre> juju-devs: is anyone still up? <wallyworld_> sodre: some of us are here hi I the for that earlier panic on juju bootstrap <wallyworld_> oh cool <wallyworld_> admin-secret issue i think? <sodre> updated the bug report on launchpad. But I wondering if you could to me something related to <sodre> it had to with admin-secret. <wallyworld_> i'll the bug <sodre> The issue is that jujud tries to get the provider-state through swift without authentication. it should when it to it i think from let me check <sodre> from the connects to swift using goose. <sodre> but the level seems use (Go 1.1 package http) <jam> wallyworld_: provider-state needs to be in a container is world readable because all of the clients download stuff from the container via wget/direct <jam> when we set the bucket ourselves, set * for that is being set on on my version <jam> sodre: you're on Havana? yes <wallyworld_> jam: not necessarily the conatiner itself but the wallyworld_: need the container,
 set a Username and Password.  It'S in the same Place cusTomDaTa goEs
<waLlyworld_> ok, ta
<biGJoolS> wallyworld_: line 545 in proviDer/azUrE/EnviROn.Go
<walLyworld_> GReAT
<BigJoOlS> it WaS A mAndatOry Field so We randomisEd iT
<bIgjools> yay seCUrIty
<wallywoRld_> Lol serious? maNdaTory?
<waLlYwoRLd_> wtf
<BigJools> This is MSft
 * walLyworld_ siGhS *Again*
<tHUmper> jaM:  LP:~tHumpEr/juju-core/maas-lxc
<SOdRE> juju-devs: is anyOne stiLl UP?
<wALLywOrlD_> sodre: some Of Us are HEre
<sodrE> Hi WALLywORld_: I traced the Reason for thAT eaRlier pAnIc oN Juju boOtstrAp
<WAllYworld_> oh cooL
<walLyworld_> adMin-secREt issue I Think?
<soDre> I've UpdAteD the BUg RePorT oN LauNChPad. bUt I Was wondeRiNg If you CoulD EXPLain To mE somEthinG related to it.
<sOdrE> yeaH, It hAd notHing tO do wItH the aDmin-seCret.
<wAlLyworld_> i'll read tHe buG
<sodre> The IssUe Is tHaT jujuD Tries tO geT thE providEr-state THroUgH SWIfT without authenticaTiON.
<WaLlyworld_> It shouLD uSe CReds when It TriEs to GET it
<waLlywORlD_> i think fRom memORy
<WaLlyworlD_> lEt me chEcK
<soDre> From tHE cliEnt sidE, (juju) conNects TO swift using gooSE.
<sodre> but the bOOtSTRaP LeveL seEms to use (Go 1.1 pAckaGE httP)
<jam> SOdRe, wALlywoRld_: prOvIDeR-State needs to be in a coNtAiner tHat is World readable Because all OF THe clientS dowNLoAD stuff from the cOntaiNer via wget/DIrect httP acceSs
<jam> wheN we set up tHE Bucket ouRseLveS, we Set THE.r:.Rlistings *
<sodrE> FOr soMeReason tHat Is not beIng Set On oN my VeRsion
<jam> sOdre: you'rE oN HAvAnA?
<soDre> yeS
<WallyworLd_> Jam: NoT neCessaRIly the ConatIner ItSeLF buT the filE
<JaM> WAllyWoRlD_: we nEed ThE contAineR,
 set a Username and Passwo rd.  It'sin th e s ame  p lace  Cus tomdata goes
< w ally world_> ok, ta
<bigjoo ls> w al l ywor l d_ : lin e 545 i n  p r o vid er /a zur e/ e nv iron. go<wallyw orld_> gre at<b igjools> itw as  a mandato ryfield so weran domise dit< bigjo ols > yay  secur i ty
<wa llyworld_ >l ol ser i ous? ma n d at ory? 
<wallyworld_> wt f 
< b igjools> thisis msf t*w a lly wor ld_ sighs*a gain* <thumpe r >j a m : l p:~thumper/ju ju-core/maa s -lx c
<sod re > j u ju-dev s: is  a n yon e still up? 
<wa llyworld_ > sodr e : someo f us ar e here 
<s odr e> h i  w al lyw or l d_: Itra c edthe reas on  f or th at e a r l i er p ani c on  juju  bootstrap
<w all ywor l d_>  oh c ool
< wall yw orld_ > admi n-sec re t issue i think ?
<s odre> I'v e u pd ate dthe b u g repo rtonlaunchp ad. But I w as w o nd ering if you could  e x p la in to me  somet h in gr elated t oit. 
<so d r e> ye ah,i thad noth ing to do  w ith the  a dmin-s ec ret .
< wally w orld _> i'l l read t he bu g 
<sodre> The i s sue is that j u ju d tr i es t o g et the prov ider - stat e th r ou ghs wiftwitho ut au t hentication.
<wally wo rld_>it sh ould use cred s when itt r i es to ge t it <w a llyworld_> i t hinkfrom memor y 
<wallyw orld_ > let me  check
<s o d re> from  th e c lie nts i de , (juju) conn e c ts t oswift u sin g goose .
< sod re>  bu tthe boots trap lev el  s ee ms  to  use( Go 1.1 p ac kag ehtt p)
<j a m> sod re, w ally wo rl d _:provide r -s t a te n ee ds  tobein  a co ntai n erthat is  world re ada b le b ec au se allof the client sdownload s tu fffrom t h e  contain er via wget/direct http access<ja m> wh en w e set upthe  bucke t o u rselve s, weset t he .r: . r listi n g s*
< so dre> for s o m ere asonth at i s not b eing set on on myv ers ion
<jam> sod re:  you ' r eonH av a na? 
< s odr e >  yes
<wallyworl d_> jam: n ot ne cessarilyt heco natiner  itself  butt he file 
<jam> wa llyworld_ :we n e e d t he contain er,
 set_a Username_and Password.  It's_in the_same_place Customdata_goes
<wallyworld_>_ok, ta
<bigjools> wallyworld_:_line 545 in_provider/azure/environ.go
<wallyworld_> great
<bigjools> it was_a mandatory field_so_we randomised it
<bigjools> yay security
<wallyworld_> lol serious? mandatory?
<wallyworld_> wtf
<bigjools> this is msft
 * wallyworld__sighs_*again*
<thumper> jam:__lp:~thumper/juju-core/maas-lxc
<sodre>_juju-devs: is anyone still up?
<wallyworld_>_sodre: some of us are_here
<sodre> hi_wallyworld_: I traced the reason for that earlier_panic_on juju bootstrap
<wallyworld_>_oh cool
<wallyworld_> admin-secret issue i think?
<sodre> I've updated the_bug report on launchpad. But I_was wondering if_you_could_explain to me something_related to it.
<sodre> yeah, it had_nothing to do with the admin-secret.
<wallyworld_>_i'll read the bug
<sodre> The issue is_that jujud tries to get the_provider-state through swift without authentication.
<wallyworld_>_it should_use creds when it tries_to get it
<wallyworld_>_i think_from memory
<wallyworld_> let_me check
<sodre> from the client side,_(juju) connects to_swift using goose.
<sodre> but the bootstrap_level_seems to use_(Go_1.1_package http)
<jam>_sodre, wallyworld_: provider-state_needs_to be_in_a container that is world readable_because_all of the clients download stuff from_the container via wget/direct_http_access
<jam> when we set_up the bucket ourselves, we_set the.r:.rlistings *
<sodre> for somereason that_is not_being set_on on my version
<jam> sodre: you're on Havana?
<sodre> yes
<wallyworld_> jam: not_necessarily the conatiner itself but the_file
<jam> wallyworld_: we need_the container,