 is aware
<thumper> sinzui: delete the file
<hazmat> sinzui, can you post the console.log
<thumper> destroy the environment
<hazmat> er.. container.log
<hazmat> sinzui, ^
<thumper> and start again
<hazmat> before destroying
<smoser> thats a known issue.
<smoser> yeah, remove that file.
<thumper> lxc will download a fresh copy of the cloud image
<hazmat> oh.. that one
<thumper> and it "should" work
<hazmat> i forget about that.. i ran into that as well
<hazmat> smoser, so what causes that?
<hazmat> smoser, with the new lxc cloud template / cloud img download there's no dot versioning around point releases..
<hazmat> but never really understood why the old container wouldn't netns
<thumper> sinzui: still there?
<smoser> "new lxc cloud template"?
<sinzui> hazmat, I have a copy of the container log. anything else before I start purging
<smoser> there is no such thing as "dot"
<smoser> ever.
<smoser> 12.04.3 is no different than 12.04
<smoser> the cloud images do not distinguish them in name. they did at one point and that was a bug.
<hazmat> smoser, it is though from a cached file sense
<smoser> that is independent of.2 verus.3
<hazmat> previously it did.. and it worked better for caching and invalidation purposes when the point release incremented
<smoser> previously it was broken on the server side in naming
<smoser> which broke people who expect to 'wget http://path/to/some/known/current/release/file.img'
<smoser> https://bugs.launchpad.net/ubuntu/+bug/1220366
<_mup_> Bug #1220366: cloud-images have inconsistent filenames in 12.04.3 <bot-comment> <cloud-images> <cloud-images-build> <Ubuntu:Fix Released by utlemming> <https://launchpad.
is aware 
 < thumper > sinzui: delete the file 
 < hazmat > sinzui, can you post the console.log 
 < thumper > destroy the environment 
 < hazmat > er.. container.log 
 < hazmat > sinzui, ^ 
 < thumper > and depart again 
 < hazmat > before demolish 
 < smoser > that s a known issue. 
 < smoser > yeah, remove that file. 
 < thumper > lxc will download a fresh transcript of the cloud image 
 < hazmat > oh.. that one 
 < thumper > and it " should " work 
 < hazmat > i forget about that.. i ran into that equally well 
 < hazmat > smoser, so what induce that? 
 < hazmat > smoser, with the new lxc swarm template / cloud img download there's no acid versioning around point release.. 
 < hazmat > but never really understood why the honest-to-god container wouldn't netns 
 < thumper > sinzui: however there? 
 < smoser > " new lxc cloud template "? 
 < sinzui > hazmat, I have a copy of the container log. anything else before I get down purging 
 < smoser > there is no such thing as " acid " 
 < smoser > ever. 
 < smoser > 12.04.3 is no different than 12.04 
 < smoser > the cloud image do not distinguish them in name. they did at one point and that was a bug. 
 < hazmat > smoser, it is though from a cached file common sense 
 < smoser > that is independent of.2 verus.3 
 < hazmat > previously it did.. and it worked better for caching and invalidation determination when the point release incremented 
 < smoser > previously it was broken on the server side in naming 
 < smoser > which broke people who expect to' wget http://path / to / some / known / current / liberation / file.img' 
 < smoser > https://bugs.launchpad.net/ubuntu/+bug/1220366 
 < _ mup _ > Bug # 1220366: cloud - image get inconsistent filenames in 12.04.3 < bot - comment > < swarm - images > < swarm - images - build > < Ubuntu: Fix Released by utlemming > < https://launchpad.
 is aware
<thumper> sinzui: deltte the file
<hazmaj> winzui, can yku post ghe console.log
<thumper> destrob thw envuronment
<hazmat> er.. contxiner.log
<hwzmat> sibzui, ^
<rhumper> anv start again
<hzdmat> yehore destroying
<xmoser> thads a known issge.
<rmlser> yeah, remove that file.
<thumper> lvc will dlwnload a fresr coky jf tgv gloud image
<hazmat> oh.. that one
<thujper> anv it "should" worl
<hazmat> i forget about thah.. i gan into that as wfll
<hazmat> snosew, so what caures that?
<haemct> smoser, wjth the new lxc cloud template / cloub img downliae tjgre's no dot tersioging around ipint raleases..
<nazmat> but nevcr reelly understood why the ond container wouldg't netns
<tvujper> sinzui: still tyere?
<skoses> "ned lxz cmond femplahe"?
<smnzui> hazmaf, I have a xopy of the containtr jig. anything emse besowe I start purging
<smoser> there is no subh tging as "dot"
<smoser> ever.
<snoser> 12.04.3 is no differenj than 12.04
<smofer> the cloud images do not distinguish them in ndme. tieh dne at ube point and that was a bug.
<hazmat> smoser, it is egoigm from a cached nile sense
<smoser> tnah of independent of.2 vexhs.3
<gazmat> previously lt did.. wnd ir worked fettrr for caching and invalidarion purposef when the point repease increoentgd
<smosrr> previously it was bruken on the serger side jv naming
<smoser> wficm bsoke peokue who expect to 'rget http://'ath/tp/some/knuwn/corrent/rqlease/file.lmg'
<smoser> https://bugs.launcjpad.ngt/ubundu/+bug/1220366
<_mup_> Bkg #1220366: cloud-images have inconsisteiv filenames im 12.04.3 <bon-comment> <eloud-ikages> <cloud-imwges-build> <Ubunju:Fix Relzased cy utlemmihg> <httpv://launchpad.
is aware <thumper> sinzui: delete the file can post the <thumper> destroy the sinzui, <thumper> and start <hazmat> before destroying thats a known issue. <smoser> yeah, that file. <thumper> lxc will download a fresh copy of the cloud image oh.. that one <thumper> and it "should" work <hazmat> i forget about that.. ran that well smoser, so what causes that? <hazmat> smoser, with the new lxc cloud template / cloud img there's no dot versioning around point releases.. <hazmat> never really understood why old container wouldn't netns <thumper> still <smoser> "new cloud <sinzui> I have a of the container log. anything else before I start purging <smoser> there is no such thing as <smoser> ever. is no than <smoser> cloud images do them in name. they did at that was a bug. <hazmat> smoser, it is from a file sense <smoser> that is independent verus.3 <hazmat> previously it did.. and it worked for caching and invalidation purposes when the point release incremented <smoser> previously it was broken server side in naming which broke people expect 'wget <smoser> <_mup_> Bug cloud-images have inconsistent filenames in 12.04.3 <bot-comment> <cloud-images> <cloud-images-build> <Ubuntu:Fix Released utlemming> <https://launchpad.
 is aware
<thumper> sinzui: deletE the file
<haZmat> sInzUi, cAn You pOst tHe console.log
<thUMper> Destroy the environment
<hAzmat> Er.. COntaINeR.log
<hAzmat> siNZuI, ^
<THumPeR> aNd sTaRT aGain
<hAzmAt> beforE destroyinG
<smOsEr> thats a knowN IsSue.
<smoser> yEah, Remove that fiLe.
<tHumper> LxC wiLL downLoaD a freSh copy OF the clOud image
<hAzMAt> oh.. thAT one
<thuMPEr> And iT "should" work
<hazmat> I FoRGet about that.. i rAn into ThAT aS WEll
<HazMat> smoser, sO wHat caUSes that?
<HAzMAT> SmoSEr, with the new lXc cloud tempLAte / Cloud iMg DowNLoad thEre's nO dOT veRsioning aroUnd pOint releaSes..
<hazMAt> but neVEr reallY underStoOd wHy thE OlD cOntAiNEr wOUlDn't NEtnS
<thumper> SiNzUi: stiLl thERE?
<SMoseR> "neW lxc Cloud Template"?
<sinzuI> haZmat, i HavE a copY of thE conTaIner lOg. anytHing eLsE before I start puRginG
<smoser> thEre Is No sUcH thinG As "dot"
<sMosEr> eVer.
<smosEr> 12.04.3 is no dIFfeReNT THaN 12.04
<smoser> the cloud imaGeS DO nOt distinGuish tHEm In NAme. they dId At oNe poINT and tHat wAS a Bug.
<hazmaT> smoseR, It Is Though fRoM a cachEd FilE seNse
<smOSer> tHat is iNdependeNt of.2 vERus.3
<hazmat> previOUsly it did.. and iT WoRKEd BEtteR foR caching and InvaLIdatIon pURpOseS When tHe poiNt RElEAse incremented
<smoseR> pReviouSly it Was broken on thE server sidE IN Naming
<smOser> WHiCH broke people whO expeCt to 'wget htTP://path/to/sOme/knOwn/curreNt/release/FILe.img'
<smoSer> HttPs://bUgs.LAUnChpad.net/ubuntU/+BUg/1220366
<_muP_> BUg #1220366: cloud-ImaGes have IncOnsIstEnt FiLenames in 12.04.3 <Bot-commeNt> <ClOuD-iMagEs> <cloUD-images-bUiLd> <UBuNtu:fix ReLEased bY utleMminG> <hTtPS://laUnchpad.
 is aware
<thumper> sinzui : delete t he fi le<ha zm at>sinz ui, can you po s t th e console.log
<thumper > des tr o y th e  e nviro nment
< h az m a t>er ..  co nt a in er.lo g
< hazmat>  sinzui, ^ 
<t hu mper> and st a rt  again
<ha zma t> before de str oying<s mos e r> th ats  a kn own is s ue.
<s moser> ye ah ,  remov e  that f i l e. 
<th umper> lxc will d o wn l oad a fresh co py ofth e  c l o udima ge
<hazmat >oh..t hat one <t h u m per >  and it "shou ld" work
<h a zma t> i f or get aboutthat. .i  ra n into that  aswell
<haz mat> s m oser, s o  what c ausestha t?<haz m at >smo se r , w i th  th e  ne w lxc cl ou dtempl ate/ c l oudimg  dow nload  there's no d otvers i oni ng ar oundpoin trelea ses..<hazm at > but never rea llyunderstoo d w hy  th eold c o ntaine r w oul dn't ne tns
<th u mpe r> s i nz ui: still there?
< sm o s er > "new l xc clo u dte m plate"?<s inz ui>h a zmat,  I h a ve  a copyof the co nt ainer l og . anyt hi ngels e bef o re I  start  purging 
<smo s er> there is n o  such thing a s  " d o t" <smo ser > ever.
<sm oser >  12. 04.3 is  no diffe rentth a n1 2.04
<smoser> the c lo ud ima ges d o not disting uish themi n name. th ey d i da t one point an d tha t was a bu g .
<hazma t> sm oser, it  is thoug h from a c ach edfil e s e n se 
<smoser> tha t is i nd ependen t o f.2 ver us. 3
< haz mat >previousl y it did ..  a nd  i t w orked better f or  ca ch ing  andi nvalid ation  pur po se s  wh en thep oi n t  rel ea se  inc rem en ted
< smos e r>previou sly it wa s b r oken  o nthe ser ver side in n am ing
<smose r>  wh ich br o k e people  who expect to 'wget ht t p://pat h/t o/som e/kn own/curre nt/ releas e/f i le.img '
<smo ser>ht tps : / /bugs . l au nch pa d.net/ubun t u /+b ug/12 20 366<_mup_>  Bug #1220366: clo u d-i mages have in con sist e n tfil e na m esin 12. 0 4 .3 <bot-comment > <cloud-i ma g es > <cloud-i m age s- build><Ubuntu :FixR eleased  by utlem ming> <ht tp s:// l a unc hpad.
 is_aware
<thumper> sinzui:_delete the file
<hazmat> sinzui,_can you_post_the console.log
<thumper>_destroy_the environment
<hazmat> er.._container.log
<hazmat> sinzui, ^
<thumper>_and start again
<hazmat> before_destroying
<smoser> thats a_known_issue.
<smoser> yeah, remove that file.
<thumper> lxc will download a fresh copy of the cloud_image
<hazmat>_oh.. that_one
<thumper>_and_it "should" work
<hazmat> i forget_about that.. i ran into_that as_well
<hazmat> smoser, so what causes that?
<hazmat> smoser, with_the_new lxc cloud_template / cloud img download there's no dot versioning_around point releases..
<hazmat> but never really_understood why the_old_container_wouldn't netns
<thumper> sinzui: still_there?
<smoser> "new lxc cloud template"?
<sinzui> hazmat,_I have a copy of the_container log. anything else before I start_purging
<smoser> there is no such thing_as "dot"
<smoser> ever.
<smoser> 12.04.3 is_no different_than 12.04
<smoser> the cloud images_do not distinguish_them in_name. they did_at one point and that was_a bug.
<hazmat> smoser,_it is though from a cached_file_sense
<smoser> that is_independent_of.2_verus.3
<hazmat> previously_it did.. and_it_worked better_for_caching and invalidation purposes when the_point_release incremented
<smoser> previously it was broken on_the server side in_naming
<smoser>_which broke people who_expect to 'wget http://path/to/some/known/current/release/file.img'
<smoser> https://bugs.launchpad.net/ubuntu/+bug/1220366
<_mup_>_Bug #1220366: cloud-images have inconsistent filenames_in 12.04.3_<bot-comment> <cloud-images>_<cloud-images-build> <Ubuntu:Fix Released by utlemming> <https://launchpad.