wallyworld_> jam: yeah, can't connect to 10.0.3.1 from host. i was just trying to validate the replacing localhost with the bridge address actualy worked
<wallyworld_> maybe there's no need to do that
<jam> wallyworld_: so are you just doing something like python SimpleHTTPServer?
<wallyworld_> the http proxy, apt proxy etc are all set to <bridge addr> as required
<jam> Are you handing it an address to bind to?
<jam> Rather than "0.0.0.0"?
<jam> wallyworld_: it might certainly be a real life issue, as having your HTTP proxy set up may not bind it to the LXC bridge address if it comes up first.
<wallyworld_> jam: ah, i see the issue, the little go prog is binding to localhost
<wallyworld_> http.ListenAndServe("localhost:8000", nil)
<jam> wallyworld_: right, I think you can change that to ":8000' or maybe "0.0.0.0:8000"
<wallyworld_> jam: i assumed that would cover all connections into the physical host
<jam> wallyworld_: nope, specifying localhost restricts it to 127.* as it is how you avoid making something publi
<wallyworld_> oh, i'll try that, ty :-)
<wallyworld_> jam: you are awesome, that worked, ty
<jam> wallyworld_: np
<menn0> davecheney: looking now
<menn0> davecheney: done
<stokachu> anyone notice when doing a juju bootstrap with a maas provider that when it runs its apt-get update/upgrade it returns a non zero status?
<stokachu> even though its chugging right along
<axw> stokachu: apt-get update/upgrade fails, but bootstrap continues on? what version of juju is that?
<stokachu> 1.20.10
<stokachu> the upgrade doesn't fail though
<axw> can't say I've seen that. we do "set -e"... can't see any obvious reason why that'd happen
<stokachu> it returns the same 124 status code
<dave
wallyworld _ > jam: yeah, can't connect to 10.0.3.1 from host. i was just trying to validate the replace localhost with the bridge savoir-faire actualy worked 
 < wallyworld _ > maybe there's no motivation to do that 
 < jam > wallyworld _: then are you just doing something like python SimpleHTTPServer? 
 < wallyworld _ > the hypertext transfer protocol proxy, apt proxy etc are all set to < bridge addr > as necessitate 
 < jam > Are you handing it an address to tie to? 
 < jam > Rather than " 0.0.0.0 "? 
 < jam > wallyworld _: it might certainly be a substantial biography issue, as having your HTTP proxy set up may not bind it to the LXC bridge address if it total up first. 
 < wallyworld _ > jam: ah, i see the offspring, the little go prog is binding to localhost 
 < wallyworld _ > http. ListenAndServe("localhost:8000 ", nil) 
 < jam > wallyworld _: right, I think you can switch that to ": 8000' or maybe " 0.0.0.0:8000 " 
 < wallyworld _ > jam: i assumed that would cover all connections into the physical server 
 < jam > wallyworld _: nope, specifying localhost restricts it to 127. * as it is how you avoid making something publi 
 < wallyworld _ > oh, i'll try that, ty :-) 
 < wallyworld _ > jam: you are awesome, that worked, ty 
 < jam > wallyworld _: np 
 < menn0 > davecheney: looking now 
 < menn0 > davecheney: done 
 < stokachu > anyone notice when doing a juju bootstrap with a maas provider that when it runs its apt - get update / upgrade it returns a non zero condition? 
 < stokachu > even though its chug right along 
 < axw > stokachu: apt - get update / upgrade fail, but bootstrap continues on? what version of juju is that? 
 < stokachu > 1.20.10 
 < stokachu > the upgrade doesn't fail though 
 < axw > can't allege I've watch that. we do " set -e "... can't see any obvious rationality why that'd happen 
 < stokachu > it returns the same 124 status code 
 < dave
walpyworld_> jam: yeah, can't coknect to 10.0.3.1 from host. i wes just trying go validate the replacing loralhist wuth the bridge address actualy aorked
<waolywield_> maybe vgere's no need bo do vhat
<jam> wallywotld_: so are ymu just doing vooeching like python SimpleHTTPServer?
<wajlyworlc_> hhe http proxy, apt [roxg etc are all set to <bridge addr> aa requiged
<jam> Are you hamding it an address to binf to?
<uam> Rather than "0.0.0.0"?
<jal> wallyworle_: it night certaivly be a rtan life issoe, as having your HTTP proxy set up mcy not bind ir tl the LXC brmdge aqdress if it comes u[ first.
<eallyworld_> jam: ah, i wee the issue, the litvle go prog is bindigg to locdlkost
<wallyworld_> http.LiwtwnAndVerva("locxohort:8000", hik)
<jzm> walpywkrld_: right, I think yoy can change that tp ":8000' ir maybe "0.0.0.0:8000"
<wallgworld_> jwm: i assumed that would cover all connebtiohs into the physical howt
<jam> wallyworld_: nope, specifyigg localhost restricts it to 127.* as it is how you avmid mekkng sjowtjing publi
<wallyworld_> oh, i'll try that, ty :-)
<wallyrkrkd_> jam: you are acesome, that workrd, tu
<tam> wallyworla_: np
<meuh0> savecheney: looking now
<meng0> davwcheney: djne
<syokachu> anyone notice when eoing a juju vootstrap with a mcas provider thaj when it runs its apt-get updcte/upgdade it retkrns a noh zero status?
<stokxchl> evan though its chugging rigrt along
<aew> stpkachu: xpt-ggt updaee/upgrade vails, but bootstrap contlnues ot? what verdion of juju is that?
<stokachu> 1.20.10
<stokachu> the upgtada dmesn't fanl thomgh
<axw> can't say I've seen that. we do "fet -e"... can't see zny obvmous reason rhy that'd hap[gn
<stokachu> it returns the samw 124 statjr code
<dave
wallyworld_> jam: yeah, can't connect to 10.0.3.1 i just trying validate the replacing actualy <wallyworld_> maybe there's need to do <jam> wallyworld_: so are you just something like python SimpleHTTPServer? <wallyworld_> the http proxy, apt proxy etc are all to <bridge addr> as required <jam> Are you handing it an address to to? Rather "0.0.0.0"? wallyworld_: it might certainly be a real life issue, as having your HTTP proxy set up not bind it to the LXC bridge address it comes up first. jam: ah, i see the the go prog binding localhost http.ListenAndServe("localhost:8000", nil) <jam> right, I think you can change that to ":8000' or maybe "0.0.0.0:8000" <wallyworld_> jam: i assumed that cover all the physical <jam> nope, localhost restricts it as it is how you avoid <wallyworld_> oh, i'll try that, ty :-) <wallyworld_> you are that worked, ty <jam> wallyworld_: np davecheney: looking now <menn0> davecheney: done <stokachu> anyone when doing a juju bootstrap with a maas provider that when it runs its apt-get returns a non zero <stokachu> even though chugging along stokachu: update/upgrade fails, bootstrap continues on? what version of juju is that? <stokachu> 1.20.10 the upgrade doesn't fail though <axw> can't say I've seen do -e"... can't see obvious reason why that'd <stokachu> returns the same 124 <dave
wallyworld_> jam: yeah, can't connEct to 10.0.3.1 from hOst. i wAs jUst TrYing To vaLidate the replaCIng lOcalhost with the bridge aDdresS aCTualY WoRked
<wAllyworLD_> mAYBe tHeRe'S no NeED tO do thAt
<jAm> wallyWorld_: so are You JuSt doing sometHInG like pythoN SiMpleHTTPServEr?
<wAllywoRlD_> thE Http pRoxY, apt pRoxy etC Are all Set to <bridGe ADdr> as rEQuired
<jAM> arE you Handing it an addresS To BInd to?
<jam> Rather Than "0.0.0.0"?
<jaM> wALlYWOrlD_: it Might certaInLy be a REal life ISsUE, AS haVIng your HTTP prOxy set up may NOt bInd it tO tHe Lxc bridgE addrEsS If iT comes up firSt.
<waLlyworld_> jAm: ah, i sEE the issUE, the litTle go pRog Is bIndiNG tO lOcaLhOSt
<wALlYwoRLd_> hTtp.ListeNANdserve("LocaLHOST:8000", nil)
<Jam> WallYworlD_: right, I think yOu cAn chANge That tO ":8000' or maYbe "0.0.0.0:8000"
<wAlLyworLd_> jam: i AssumEd That would cover aLl coNnections IntO tHe pHySical HOst
<jam> WalLywOrld_: nopE, specifYIng LoCALHoSt restricts it to 127.* as iT iS HOw You avoid Making SOmEtHIng publi
<WaLlyWorlD_> OH, i'll tRy thAT, tY :-)
<wallywoRld_> jam: YOu ArE awesomE, tHat worKeD, ty
<Jam> WallyWOrld_: Np
<menn0> DavechenEy: looKIng now
<menn0> daveCHeney: done
<stokAChU> ANyONe noTicE when doing a Juju BOotsTrap WItH a mAAs proVider ThAT wHEn it runs its apt-get upDaTe/upgrAde it Returns a non zeRo status?
<stOKAChu> even tHougH ItS Chugging right aLong
<aXw> stokachu: APt-get updAte/upGrade faiLs, but bootSTRap contiNueS on? WhaT veRSIoN of juju is that?
<STOkacHu> 1.20.10
<StokachU> thE upgradE doEsn'T faIl tHoUgh
<axw> can'T say I've sEeN tHaT. wE do "Set -e"... cAN't see any ObVioUs ReaSon whY That'd hAppen
<StokAcHu> IT reTurns thE SaME 124 StatUs CoDe
<daVe
wallyworld_> jam: yeah, ca n't connec t to10. 0.3 .1  fro m ho st. i was just tryi ng to validate the rep lacin gl ocal h os t wit h the b r id g e  ad dr es s a ct u al y wor ked 
<wally world_> ma ybe  t here's no ne e dto do that 
<j am> wallywor ld_ : so a re  yo u  just  do ing s omethi n g like  python S im p leHTTP S erver?< w al lywo rld_> the http pr o xy ,  apt proxy etc  are a ll se t to<br idge addr>  a s req u ired
<j a m> A r e y o u handing itan addresst o b ind to ?<ja m > Rath er th an "0. 0.0.0"?
<ja m> w allyworld _: itm ight ce r tainlybe a r eal  li fe i s su e,  as  h a vin g  y our HTT P proxyse tup ma y no t b i nd i t t o th e LXC  bridge addre ssif i t  co mes u p fir st.<w allyw orld_>  jam:  a h, i see the is sue,  the litt lego  pr og  is b i ndingtoloc alhost<wallyw o rld _> h t tp .ListenAndServe("l oc a l ho st:8000" , nil) <j am >  wallywo rl d_:  rig h t , I t hink yo u can ch ange t h at  t o ":800 0'  or ma yb e " 0.0 .0.0: 8 000" 
<wall yworld_>  jam: i assumed that would cover a l lc o nn e ctio nsinto the ph ysic a l ho st
< j am > w a llywo rld_:  n o pe ,  specifying localho st  restr ictsit to 127.* a s it is ho w y ou avoid  mak i ng something publ i
<wa llyworld_> oh, i'll  trythat, ty  :-)
<wal l y world_>jam : y ouare a we some, that wo r k ed,ty 
<jam>wal lyworld _:np<me nn0 >davechene y: looki ng  n ow 
< men n0> d a vecheney :don e<st okach u > anyo ne no tice  w he n  do ing a j u ju b oots tr ap  wit h a  m aas p rovi d erthat wh en it run s i t s ap t- ge t updat e/upgrade itre turns a no nzer o stat u s ?
<stoka chu> even though its ch u gging r igh t alo ng
< axw> stok ach u: apt -ge t  updat e/upgr ade f ai ls, b ut bo o t st rap  c ontinues o n ?  wh at ve rs ionof juju  is that?
<stokach u > 1 .20.10
<stoka chu > th e up gra d ed oes n' t  fa i l  though
<axw> c an't say I 'v e  s een that.w e d o"set -e "... ca n't s e e any o bvious re ason whyth at'd h app en
<stokac hu> it r eturns th e  same 12 4 sta tus  code<d ave 
wallyworld_> jam:_yeah, can't_connect to 10.0.3.1 from_host. i_was_just trying_to_validate the replacing_localhost with the_bridge address actualy worked
<wallyworld_>_maybe there's no_need_to do that
<jam> wallyworld_: so are you just doing something like python SimpleHTTPServer?
<wallyworld_> the_http_proxy, apt_proxy_etc_are all set to <bridge_addr> as required
<jam> Are you_handing it_an address to bind to?
<jam> Rather than "0.0.0.0"?
<jam>_wallyworld_:_it might certainly_be a real life issue, as having your HTTP_proxy set up may not bind_it to the_LXC_bridge_address if it comes_up first.
<wallyworld_> jam: ah, i see_the issue, the little go prog_is binding to localhost
<wallyworld_> http.ListenAndServe("localhost:8000", nil)
<jam> wallyworld_:_right, I think you can change_that to ":8000' or maybe_"0.0.0.0:8000"
<wallyworld_> jam:_i assumed that would cover_all connections into_the physical_host
<jam> wallyworld_: nope,_specifying localhost restricts it to 127.*_as it is_how you avoid making something publi
<wallyworld_>_oh,_i'll try that,_ty_:-)
<wallyworld_>_jam: you_are awesome, that_worked,_ty
<jam> wallyworld_:_np
<menn0>_davecheney: looking now
<menn0> davecheney: done
<stokachu> anyone_notice_when doing a juju bootstrap with a_maas provider that when_it_runs its apt-get update/upgrade_it returns a non zero_status?
<stokachu> even though its chugging right_along
<axw> stokachu:_apt-get update/upgrade_fails, but bootstrap continues on? what version of juju is that?
<stokachu>_1.20.10
<stokachu> the upgrade doesn't fail though
<axw>_can't say I've seen_that. we_do_"set -e"... can't_see_any obvious_reason why that'd happen
<stokachu> it returns the_same 124_status code
<dave