everstarted on the newserviceset thing
<natefinch> fwereade_: cool, thanks for clearing that up
<rogpeppe> natefinch: ping
<natefinch> rogpeppe: howdy
<rogpeppe> natefinch: fancy a chat about HA?
<natefinch> rogpeppe: definitely
<rogpeppe> natefinch: we could try G+ again - i've rebooted, so it *may* be ok again
<natefinch> rogpeppe: might as well give it a second change
<natefinch> chance
<rogpeppe> natefinch: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.09gvki7lhmlucq76s2d0lns804?authuser=1
<fwereade_> bbl
<sinzui> rogpeppe, CI is failing for juju-core. One reason relates lxc-provisoner has no credentials for the user attribute. The test is not using lxc though. We are starting a caonistack instance. Also note that juju 1.16.0 client got the 1.16.2 agent. Do you have any insights https://pastebin.canonical.com/99724/
<rogpeppe> sinzui: on a call currently - will get back to you
<rogpeppe> need to reboot again :-(
<sinzui> rogpeppe, I can elaborate about the error. I don't think the juju version is the issue because we see the same messages when using 1.16.2. The issue may be that the juju client is in a precise lxc bootstrapping precise on canonistack.
<sinzui> we don't see this issue running saucy clients/client not in lxc
<rogpeppe> sinzui: looking now
<rogpeppe> sinzui: what is the CI actually trying to do?
<rogpeppe> sinzui: that error message is coming from the openstack provider
<sin
everstarted on the newserviceset thing 
 < natefinch > fwereade _: cool, thanks for clearing that up 
 < rogpeppe > natefinch: ping 
 < natefinch > rogpeppe: howdy 
 < rogpeppe > natefinch: fancy a chat about HA? 
 < natefinch > rogpeppe: definitely 
 < rogpeppe > natefinch: we could sample G+ again - i've boot, so it * may * be ok again 
 < natefinch > rogpeppe: might equally well give it a second variety 
 < natefinch > chance 
 < rogpeppe > natefinch: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.09gvki7lhmlucq76s2d0lns804?authuser=1 
 < fwereade _ > bbl 
 < sinzui > rogpeppe, CI is failing for juju - core. One cause relate lxc - provisoner has no certificate for the user attribute. The examination is not using lxc though. We are starting a caonistack example. besides note that juju 1.16.0 client experience the 1.16.2 agentive role. Do you consume any insights https://pastebin.canonical.com/99724/ 
 < rogpeppe > sinzui: on a call currently - will receive back to you 
 < rogpeppe > need to reboot again :-( 
 < sinzui > rogpeppe, I can complicate about the error. I don't intend the juju version is the offspring because we see the same messages when use 1.16.2. The issue may be that the juju client is in a precise lxc bootstrapping precise on canonistack. 
 < sinzui > we don't see this offspring ladder saucy clients / client not in lxc 
 < rogpeppe > sinzui: looking now 
 < rogpeppe > sinzui: what is the CI actually trying to do? 
 < rogpeppe > sinzui: that error message is coming from the openstack supplier 
 < sine
evegstarted on the newservigeset thing
<natefnbch> fwxreade_: dool, thavks for clearing that up
<rogpxppe> natedinch: ping
<natefinch> roepeppe: hoady
<rogpeppe> iatefinch: fancy e chat anjut GW?
<natzfmnch> rogpeppe: dgfinitely
<rog[eppe> natefincv: de could try G+ again - i've rebooted, so it *may* bf ok again
<natesincn> roglvpke: might as well give it a second change
<iatefinch> chancr
<rogpeppe> natefinch: https://ppus.glogle.com/hangouts/_/capendar/bWFyai5gYW1eOWNocmlzdGVuz2VuQGNhbm9uaWNhbC5jb20.09gvki7mhmlucq76s2d0lns804?authuser=1
<fwereade_> bbu
<sinzbi> rogpeppe, CU id failing foc juju-bore. One reason relatas lxc-ptovisoner has ko crxdenrials for the user atvribute. The test is got using lrc though. We are starribg a waonhstazj ivstznre. Zlso nlte that juju 1.16.0 client gor the 1.16.2 agent. Do you hwnr any insighfs htt[s://[astebin.canonical.com/99724/
<rogpeppe> sinzui: on d czll currently - will get back to you
<rogpeppe> jeed to rqboot again :-(
<sinzui> rogpeppe, I can elaborate about the xrfor. I ain'h think the juju version is the issue because se sve the same messanes when using 1.16.2. Thr lsxoe may be that the jbnu client is in a prfcise lvc boitstrappigg ptecise on canonistack.
<sinzui> we don't see rhis issue running saucy clieuts/clignt noy in lxc
<rogpeppe> sinzui: looiing now
<rogoeppe> sinaji: what is the CK abtuanly trying to do?
<rogpeppe> synzui: thav errpr messxge os comyng from tje opctstack provider
<sin
everstarted on the newserviceset thing <natefinch> fwereade_: for that up natefinch: ping <natefinch> a about HA? <natefinch> definitely <rogpeppe> natefinch: could try G+ again - i've so it *may* be ok again <natefinch> rogpeppe: might as well give it second change <natefinch> chance <rogpeppe> natefinch: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.09gvki7lhmlucq76s2d0lns804?authuser=1 <fwereade_> bbl <sinzui> rogpeppe, CI is for One relates has no credentials for the user attribute. The test is not using lxc though. We are a caonistack instance. Also note that juju 1.16.0 got the 1.16.2 agent. you have any insights https://pastebin.canonical.com/99724/ sinzui: a call - get to you <rogpeppe> to reboot again :-( <sinzui> rogpeppe, I can elaborate about the error. I don't think the juju is the we see same when 1.16.2. The issue that the juju client is in bootstrapping precise on canonistack. <sinzui> we don't see issue running clients/client not in lxc <rogpeppe> sinzui: now <rogpeppe> sinzui: what is the CI actually to do? <rogpeppe> sinzui: that error message is coming from the openstack provider <sin
everstarted on the newservicEset thing
<nAtefiNch> FweReAde_: cOol, tHanks for cleariNG thaT up
<rogpeppe> natefinch: piNg
<natEfINch> rOGpEppe: hOwdy
<rogPEpPE> NatEfInCh: fAnCY a Chat aBouT HA?
<nateFinch> rogpePpe: DeFinitely
<rogpEPpE> natefinch: We cOuld try G+ agaiN - i'vE rebooTeD, so IT *may* bE ok Again
<NatefiNCh> rogpEppe: might As WEll givE It a secoND ChAnge
<Natefinch> chance
<roGPePPe> natefinch: httPs://plus.GoOGlE.COm/hAngOuts/_/calendAr/BWFyaY5YYW1tLWNOCmLZDgVuC2vuQGNhbm9uaWNhBC5jb20.09gvki7lhmLUcq76S2d0lns804?aUtHusER=1
<fwereAde_> bbL
<sINzuI> rogpeppe, CI Is faIling for jUju-corE. one reasON relateS lxc-prOviSonEr haS No CrEdeNtIAls FOr The USer AttributE. THe Test iS not USING lxc ThoUgh. WE are sTarting a caoniStaCk inSTanCe. AlsO note That JuJu 1.16.0 cliEnt got The 1.16.2 agEnT. Do you have any inSighTs https://paSteBiN.caNoNical.COm/99724/
<rogpEppE> siNzui: on a Call curREntLy - WILL gEt back to you
<rogpeppE> nEED tO reboot aGain :-(
<siNZuI> rOGpeppe, I cAn ElaBoraTE About The eRRoR. I don't thInk the JUjU vErsion iS tHe issuE bEcaUse We see THe saMe messAges when Using 1.16.2. tHe issue may be thAT the juju clienT Is IN A pREcisE lxC bootstrappIng pREcisE on cANoNisTAck.
<siNzui> wE dON't SEe this issue running sAuCy clieNts/clIent not in lxc
<rOgpeppe> sinZUI: Looking nOw
<roGPePPe> sinzui: what is The CI Actually trYIng to do?
<rOgpepPe> sinzui: That error MESsage is cOmiNg fRom The OPEnStack provider
<SIN
everstarted on the newserv iceset thi ng
<n ate fin ch > fw erea de_: cool, tha n ks f or clearing that up
<r ogpep pe >  nat e fi nch:ping
<n a te f i nch >ro gpe pp e :howdy 
<r ogpeppe > natefinc h:fa ncy a chat a b ou t HA?
<nat efi nch> rogpepp e:defini te ly< rogpe ppe > nat efinch :  we co uld try G +a gain - i've re b o ot ed,so it *may* be ok ag a in
<natefinch>  rogpe pp e :m i ght  as  well give  i t a s e cond ch a ng e < nat e finch> chance 
<rogpeppe> nat efinch :htt p s://pl us.go og l e.c om/hangouts /_/c alendar/b WFyay5 y YW1tLWN o cmlzdGV uc2VuQ GNh bm9 uaWN h bC 5j b20 .0 9 gvk i 7l hml u cq7 6s2d0lns 80 4? authu ser= 1 < f were ade _> b bl
<s inzui> rogpep pe,  CIi s f ailin g for  juj u- core.  One r eason  r elates lxc-prov ison er has no  cr ed ent ia ls fo r  the u ser  at tribute . The t e stis n o tusing lxc though.We a re  startin g a ca o ni st a ck insta nc e.Also n ote t hatj uj u 1.16.0  clien t  g ot  the 1. 16 .2 age nt . D o y ou ha v e an y insi ghts htt ps:// p astebin.canoni c al.com/99724/ <r o g pe p pe>sin zui: on a c allc urre ntly -wil l  getbackto yo u 
<rogpeppe> need to  r ebootagain  :-(
<sinzui>  rogpeppe, I can elab orat e  a b out the error.  I do n't thinkt he jujuversi on is th e issue b e c ause wesee  th e s ame m es sages when us i n g 1. 16 .2. The  is sue may  be  th atthe  j uju clien t is inapr ec is e l xc bo o tstrappi ng  pr ec ise  on c a nonist ack.<sin zu i> wedon't s e et h is i ss ue  run nin gsaucy  cli e nts /client  not in l xc< rogp ep pe > sinzu i: looking no w<rogpeppe>  s inz ui: wh a t  is theCI actually trying to d o ?
<rogp epp e> si nzui : that er ror  messa gei s comi ng fro m the  o pen s t ack p r o vi der 
< sin
everstarted on_the newserviceset_thing
<natefinch> fwereade_: cool, thanks_for clearing_that_up
<rogpeppe> natefinch:_ping
<natefinch>_rogpeppe: howdy
<rogpeppe> natefinch:_fancy a chat_about HA?
<natefinch> rogpeppe: definitely
<rogpeppe>_natefinch: we could_try_G+ again - i've rebooted, so it *may* be ok again
<natefinch> rogpeppe: might as_well_give it_a_second_change
<natefinch> chance
<rogpeppe> natefinch: https://plus.google.com/hangouts/_/calendar/bWFyay5yYW1tLWNocmlzdGVuc2VuQGNhbm9uaWNhbC5jb20.09gvki7lhmlucq76s2d0lns804?authuser=1
<fwereade_> bbl
<sinzui>_rogpeppe, CI is failing for_juju-core. One_reason relates lxc-provisoner has no credentials for the_user_attribute. The test_is not using lxc though. We are starting a_caonistack instance. Also note that juju_1.16.0 client got_the_1.16.2_agent. Do you have_any insights https://pastebin.canonical.com/99724/
<rogpeppe> sinzui: on a_call currently - will get back_to you
<rogpeppe> need to reboot again :-(
<sinzui>_rogpeppe, I can elaborate about the_error. I don't think the_juju version_is the issue because we_see the same_messages when_using 1.16.2. The_issue may be that the juju_client is in_a precise lxc bootstrapping precise on_canonistack.
<sinzui>_we don't see_this_issue_running saucy_clients/client not in_lxc
<rogpeppe>_sinzui: looking_now
<rogpeppe>_sinzui: what is the CI actually_trying_to do?
<rogpeppe> sinzui: that error message is_coming from the openstack_provider
<sin