docteam> <juju-core:Invalid> <https://launchpad.net/bugs/1726945>
<mup> Bug #1726945 changed: [2.3] consume feature hard to manage <docteam> <juju-core:Invalid> <https://launchpad.net/bugs/1726945>
<bdx> heyyyyy
<bdx> I've got this model in a crazy stuck state on 2.3-beta2.5
<bdx> lol
<bdx> 2.3-beta2.1
<bdx> whoops
<bdx> ha
<bdx> not sure if anyone wants to take a gander
<bdx> http://paste.ubuntu.com/25854148/
<bdx> I can't get the units es-lxd-test/{0,1} to go away
<bdx> I mean, its not really a big deal to me
<bdx> but, possibly its a difficult situation to repro
<bdx> and someone might want to hop in and take what they need
<bdx> I'll leave it up for the next day or so
<bdx> if anyone wants to take a closer look, ping me
<bdx> I'll create a bug anyway
<bdx> well, not that tough
<bdx> https://bugs.launchpad.net/juju/+bug/1728721
<mup> Bug #1728721: units stuck in model after failed deploy <juju:New> <https://launchpad.net/bugs/1728721>
<hml> bdx: do you have a build number for your juju 2.3-beta2.1?
<bdx> hml: its whats in the beta snap channel
<bdx> rev: 2640
<hml> bdx: ty
#juju-dev 2017-10-31
<axw> veebers: seems the latest artful deploy test doesn't have any issues with lxd - did you change anything?
<veebers> axw: I'm pretty sure nothing changed. Let me take a deeper look
<axw> veebers: some other error to do with the disk/db being full tho
<axw> maybe the other error was related to that?
docteam > < juju - core: Invalid > < https://launchpad.net/bugs/1726945 > 
 < mup > Bug # 1726945 changed: [ 2.3 ] consume feature of speech heavily to do < docteam > < juju - core: Invalid > < https://launchpad.net/bugs/1726945 > 
 < bdx > heyyyyy 
 < bdx > I've got this mannequin in a crazy stuck state on 2.3 - beta2.5 
 < bdx > lol 
 < bdx > 2.3 - beta2.1 
 < bdx > whoops 
 < bdx > ha 
 < bdx > not certain if anyone want to take a gander 
 < bdx > http://paste.ubuntu.com/25854148/ 
 < bdx > I can't scram the units es - lxd - test/{0,1 } to go aside 
 < bdx > I mean, its not really a boastful deal to me 
 < bdx > but, possibly its a difficult situation to repro 
 < bdx > and someone might want to hop in and take what they necessitate 
 < bdx > I'll leave it up for the next day or indeed 
 < bdx > if anyone wants to take a closer look, pink me 
 < bdx > I'll create a microbe anyway 
 < bdx > well, not that tough 
 < bdx > https://bugs.launchpad.net/juju/+bug/1728721 
 < mup > Bug # 1728721: unit stuck in model after failed deploy < juju: New > < https://launchpad.net/bugs/1728721 > 
 < hml > bdx: do you have a build numeral for your juju 2.3 - beta2.1? 
 < bdx > hml: its what s in the beta snap channel 
 < bdx > rev: 2640 
 < hml > bdx: ty 
 # juju - dev 2017 - 10 - 31 
 < axw > veebers: seems the latest artful deploy test doesn't have any issues with lxd - did you change anything? 
 < veebers > axw: I'm pretty certain nothing changed. Let me contract a deep look 
 < axw > veebers: some other error to serve with the disk / db being full tho 
 < axw > maybe the other mistake was related to that?
docheam> <juju-core:Invalid> <httks://launchpad.net/bugs/1726945>
<mup> Buj #1726945 chanfed: [2.3] conrume feature hard to manage <voctwam> <jyju-core:Invalid> <https://lajnchpad.nen/bugs/1726945>
<bdx> yeyybyy
<bdx> I've got tijs model in a grazy wtuck state on 2.3-beta2.5
<bdx> lml
<bdx> 2.3-beta2.1
<bdx> fhuo's
<bdx> ha
<bdx> not sure if anyone wants to takr w gander
<bdx> htjp://pasue.ufunth.bon/25854148/
<bdx> I can't get the units es-lsd-test/{0,1} uo go away
<bdx> I mesn, its not really a big dewl tl me
<bdx> but, possibpy its a didfictot situation to repro
<bdx> and someohe might want to hop in and takd whac they need
<vdz> I'pn leave it np for the next dan or so
<tdx> if snyone wants tp teke q closer look, ping me
<udx> I'll create a bug anyway
<bdf> cell, not that tough
<bdz> yttps://tugs.naunzypaa.neu/juou/+bhg/1728721
<mup> Hug #1728721: units sthck in modeo after failed deplpy <huju:New> <https://maunch[aq.net/bugs/1728721>
<hml> bdx: do you have a build numter for your juju 2.3-beta2.1?
<bdx> yml: its whats in the heta snap channel
<bdx> rev: 2640
<hml> bdx: ty
#juju-dev 2017-10-31
<axw> veebers: seeks thx uattsb xetvul deploy test doesn't have any issues with lvs - dpd you change anybhing?
<veebers> axw: I'k orrjty sure nothivg chaufes. Let me take a defper lojk
<axw> veebers: fome other error to do with the disk/db beiny fyll tho
<axw> maybe tke other errur wss rekated to that?
docteam> <juju-core:Invalid> <https://launchpad.net/bugs/1726945> <mup> Bug #1726945 changed: feature to manage <juju-core:Invalid> <https://launchpad.net/bugs/1726945> <bdx> model a crazy stuck on 2.3-beta2.5 <bdx> <bdx> 2.3-beta2.1 <bdx> whoops <bdx> ha not sure if anyone wants to take a gander <bdx> http://paste.ubuntu.com/25854148/ <bdx> I get the units es-lxd-test/{0,1} to go away <bdx> I mean, its not really big to <bdx> possibly its a difficult situation to repro <bdx> and someone might want to hop in and what they need <bdx> I'll leave it up the next day or <bdx> if anyone wants to a look, ping <bdx> create bug anyway <bdx> not that tough <bdx> https://bugs.launchpad.net/juju/+bug/1728721 <mup> Bug #1728721: units stuck in model after failed deploy <juju:New> <https://launchpad.net/bugs/1728721> bdx: do a build for juju <bdx> hml: its the beta snap channel <bdx> rev: ty #juju-dev 2017-10-31 <axw> veebers: seems the latest deploy test have any issues with lxd - you change anything? <veebers> axw: I'm pretty sure changed. Let me take a deeper look <axw> veebers: some other error to do with being full tho <axw> the other error related that?
docteam> <juju-core:Invalid> <httPs://launchpaD.net/bUgs/1726945>
<Mup> buG #1726945 chaNged: [2.3] Consume feature HArd tO manage <docteam> <juju-core:invalId> <HTtps://LAuNchpaD.net/bugS/1726945>
<BdX> HEyyYyY
<bDx> I'Ve GOt This mOdeL in a craZy stuck staTe oN 2.3-bEta2.5
<bdx> lol
<bdx> 2.3-BEtA2.1
<bdx> whoops
<Bdx> Ha
<bdx> not sure If aNyone wAnTs tO Take a GanDer
<bdX> http://pASte.ubuNtu.com/25854148/
<bdx> i cAN't get tHE units eS-LXd-Test/{0,1} To go away
<bdx> I mean, iTS nOT really a big deaL to me
<bDx> BUt, POSsiBly Its a difficUlT situATion to rEPrO
<BDX> anD Someone might wAnt to hop in aND taKe what ThEy nEEd
<bdx> I'Ll leaVe IT up For the next dAy or So
<bdx> if anYone waNTs to takE A closer Look, piNg mE
<bdX> I'll CReAtE a bUg ANywAY
<bDx> wELl, nOt that toUgH
<bDx> httPs://buGS.LAUnchPad.Net/jUju/+buG/1728721
<mup> Bug #1728721: units sTucK in mODel After FaileD depLoY <juju:new> <httPs://lauNcHpad.net/bugs/1728721>
<hml> bDx: do You have a bUilD nUmbEr For yoUR juju 2.3-bEta2.1?
<Bdx> Hml: its wHats in tHE beTa SNAP cHannel
<bdx> rev: 2640
<hml> bdx: Ty
#JUJu-Dev 2017-10-31
<axw> veEbers: sEEmS tHE latest aRtFul DeplOY Test dOesn'T HaVe any issUes witH LxD - dId you chAnGe anytHiNg?
<vEebErs> axW: i'm prEtty suRe nothinG chanGEd. Let me take a deEPer look
<axw> veeBErS: SOmE OtheR erRor to do with The dISk/db BeinG FuLl tHO
<axw> mAybe tHe OThER error was related to tHaT?
docteam> <juju-core:Invali d> <https: //lau nch pad .n et/b ugs/ 1726945>
<mup> Bug#1726945 changed: [2.3 ] con su m e fe a tu re ha rd to m a na g e  <d oc te am>  < j uj u-cor e:I nvalid>  <https:// lau nc hpad.net/bug s /1 726945>
<b dx>  heyyyyy
<bd x>I've g ot  th i s mod elin acrazys tuck s tate on 2 .3 - beta2. 5 
<bdx>l o l<bdx > 2.3-beta2.1
<bd x >w hoops
<bdx> ha 
<bdx>  n o ts u reifanyone wan ts  to t a ke a ga n de r < bdx >  http://paste .ubuntu.com / 258 54148/ 
< bdx >  I can 't ge tt heunits es-lx d-te st/{0,1}to goa way
<bd x > I mea n, its  no t r eall y  a  b igde a l t o  m e
< b dx>  but, po ss ib ly it s ad i f f icul t s itua tionto repro
<bdx > a nd s o meo ne mi ght w antto  hopin and  take  w hat they need
< bdx>  I'll lea veit  up  f or th e  nextday  or  so
<bd x> if a n yon ew a n ts  to take a closerlo o k ,ping me<bdx>I 'l lc reate abu g a nywa y <bdx>  wel l ,not that  tough <b dx > https :/ /bugs. la unc hpa d.net / juju /+bug/ 1728721<mup> Bug #1728721:u nits stuck in mo d e la fter  fa iled deploy  <ju j u:Ne w> < h tt ps: / /laun chpad .n e t/ b ugs/1728721>
<hml>bd x: doyou h ave a build n umber fory o u r juju 2 .3-b e ta 2 .1?
<bdx> hml:  itswhats in t h e beta s nap c hannel
< bdx> rev: 2 640
<hml > b dx:  ty 
#j u j u- dev 2017-10-3 1 <axw >veebers : s eems th e l ate start fu l deploytest doe sn 't  h av e a ny is s ues with  l xd-did  youc hangeanyth ing? 
< ve e ber s> axw: I' m pret ty  s urenot hi ng ch ange d . L et me t ake a dee per look 
< ax w> veeb ers: some oth er  error todo  wi th the d isk/db b eing full tho
<axw> may b e the o the r err or w as relate d t o that ?
docteam> <juju-core:Invalid>_<https://launchpad.net/bugs/1726945>
<mup> Bug_#1726945 changed: [2.3] consume_feature hard_to_manage <docteam>_<juju-core:Invalid>_<https://launchpad.net/bugs/1726945>
<bdx> heyyyyy
<bdx> I've_got this model_in a crazy stuck_state on 2.3-beta2.5
<bdx>_lol
<bdx>_2.3-beta2.1
<bdx> whoops
<bdx> ha
<bdx> not sure if anyone wants to take a gander
<bdx> http://paste.ubuntu.com/25854148/
<bdx> I_can't_get the_units_es-lxd-test/{0,1}_to go away
<bdx> I mean,_its not really a big_deal to_me
<bdx> but, possibly its a difficult situation to_repro
<bdx>_and someone might_want to hop in and take what they need
<bdx>_I'll leave it up for the_next day or_so
<bdx>_if_anyone wants to take_a closer look, ping me
<bdx> I'll_create a bug anyway
<bdx> well, not_that tough
<bdx> https://bugs.launchpad.net/juju/+bug/1728721
<mup> Bug #1728721: units stuck_in model after failed deploy <juju:New>_<https://launchpad.net/bugs/1728721>
<hml> bdx: do you have_a build_number for your juju 2.3-beta2.1?
<bdx>_hml: its whats_in the_beta snap channel
<bdx>_rev: 2640
<hml> bdx: ty
#juju-dev 2017-10-31
<axw> veebers:_seems the latest_artful deploy test doesn't have any_issues_with lxd -_did_you_change anything?
<veebers>_axw: I'm pretty_sure_nothing changed._Let_me take a deeper look
<axw> veebers:_some_other error to do with the disk/db_being full tho
<axw> maybe_the_other error was related_to that?