/srv/irclogs.ubuntu.com/2016/05/02/#juju.txt

pmatulisNAME     OWNER        STATUS     LAST CONNECTION00:26
pmatulisadmin*   admin@local  available  2016-04-2800:26
pmatulisdefault  admin@local  available  2016-04-2800:26
admcleod1is it possible to get model and controller name from inside a unit?01:36
stubtvansteenburgh: Others have seen that too. Looks like there is a race condition buried in there that I can't see. I'll need a set of logs to trawl through to track it down.02:49
rick_h_admcleod1: no, you can from the client, but things like controller name are client defined and it's all UUIDs in the other end.02:49
bwallisHey, anyone noticing a massive slowdown on launchpad/most canonical hosted sites?05:37
bwallisMessing around with a juju deployment, and grabbing the tools for the initial bootstrap is taking a crazy amount of time05:38
bwallisDoing manual wgets is really slow too, 15-20KB/s05:39
blr_bwallis: well, glad I'm not the only one. Looking into it.05:40
bwallisyea I've been going nuts trying to figure this out all afternoon, never thought slow responses from the tools host was causing it05:42
bwallisif there's a mirror somewhere let me know :), I don't think there is though05:43
blr_bwallis: out of interest, what country are you in?05:59
bwallisUS06:00
bwallisCA specifically06:00
bwallisI got around apt issues by just using other mirrors, but as far as I know there's no mirror of streams.canonical.com or launchpad06:01
bwallisWhich sucks, bootstraps just sit here all day:06:01
bwallis2016-05-01 22:59:59 DEBUG juju.environs.simplestreams simplestreams.go:674 using default candidate for content id "com.ubuntu.juju:devel:tools" are {20160220 mirrors:1.0 content-download streams/v1/cpc-mirrors.sjson []}06:01
bwallisWow, something just happened?06:05
bwallisA bootstrap completed06:05
=== blr_ is now known as blr
jose\o/ let us know if you need any more help06:29
bwalliswill do, still seems to be slow, but it sped up enough to deploy one machine06:44
bwallisgoing to see how it goes with others06:44
bwallisspoke too soon I think :( failed to download the agent tools06:53
Sharani have created one dummy charm and deployed but this charm is going in a error state06:55
Sharanits showing "Waiting for agent initialization to finish"06:56
Sharanmodel: default machines:   "0":     juju-status:       current: error       message: no matching tools available       since: 02 May 2016 11:41:21+05:30     instance-id: pending     machine-status:       current: pending       since: 02 May 2016 11:41:07+05:30     series: trusty services:   testcharm:     charm: local:trusty/testcharm-0     exposed: false     service-status:       current: unknown       message: Waiting for agent initia06:57
bwallisis there a reason the juju "controller" doesn't appear as a machine to deploy services on in a MaaS deployment now?08:18
bwallisthis is with beta608:18
sharanjuju1.25 version, we used to get the log files in the path "/var/log/juju/unit-testcharm-0.log", but in juju2.0 version where do we find these log files?10:29
magicaltroutsame place sharan10:30
sharani didn't get, i have only "/var/log" after that there is no "juju" folder instead i found "lxd" folder10:31
magicaltroutdunno but all my charms log to the same place in v2 as v10:32
magicaltrout110:32
sharanok i have installed juju2.0 on Z-machine10:32
sharanso i was trying to find the log files10:32
sharanif i get into the "/var/log/lxd/juju-a938c2eb-4141-4a2d-89b6-71a20fa0d296-machine-3" i will get "forkstart.log,  lxc.conf,  lxc.log" files10:33
iceyis it possible to get the postgresql charm to install postgres 9.5?12:51
marcoceppiicey: it might be, stub would know12:53
marcoceppiicey: if you deploy on xenial12:54
iceymarcoceppi: I was poking around with it, but it looks like it's explicitly setting supported as <= 9.412:54
iceyand marcoceppi, I just raised a bug about it not deploying on xenial :)12:54
marcoceppioic12:54
=== cmars` is now known as cmars
shruthimahi all, I have pushed the IBM-IM charm to the store, with a new charm publish commands, but how to attach the bug .....?!!!!14:13
shruthimaBefore pushing in this new way i have pushed into lanchpad and raised a bug (https://bugs.launchpad.net/charms/+bug/1575746) and linked to trunk branch. Do i need to change it ?14:14
mupBug #1575746: New Charm: IBM Installation Manager <Juju Charms Collection:New> <https://launchpad.net/bugs/1575746>14:14
shruthimayes 1575746 is the bug i have created for IBM-IM ,but that bug i have linked to trunk branch ..!!!do i need to link it to cs:~ibmcharmers/trusty/ibm-im-0...??14:20
shruthimaI have done some alignment changes to Readme to IBM-IM ...Now what is the process to merge this changes in to IBM-IM charm in charm store???14:26
shruthimaplease can anyone suggest on the same??14:29
=== thedac is now known as dames
shruthimahi kwmonroe/Mbruzek, I have done some alignment changes to Readme in IBM-IM ...Now what is the process to merge this changes in to IBM-IM charm in charm store???14:50
mbruzekHello shruthima you can follow these instructions: https://jujucharms.com/docs/stable/authors-charm-store#submitting-a-fix-to-an-existing-charm14:52
magicaltroutnot enough question marks shruthima! ;)14:53
mbruzekBasically fix this readme in a branch and submit a merge proposal to get it added to the review queue.14:53
shruthimaok and I have pushed the IBM_IM charm to the store, with a new charm publish commands, but how to attach the bug here.....!!!! Before pushing in this new way i have pushed into lanchpad and raised a bug (https://bugs.launchpad.net/charms/+bug/1575746) and linked to trunk branch. Do i need to change it ?14:55
mupBug #1575746: New Charm: IBM Installation Manager <Juju Charms Collection:New> <https://launchpad.net/bugs/1575746>14:55
mbruzekOh I see you are using the new process14:56
mbruzekThat is great, let me check this link out14:57
shruthimaok14:57
mbruzekshruthima: So you have some changes to the README.md file you would like to make?15:03
shruthimayes i have some alignment changes15:04
mbruzekshruthima: I didn't know you were using the new way before, so I gave you the wrong link: https://jujucharms.com/docs/devel/authors-charm-store#submitting-a-new-charm15:04
mbruzekYou should be able to `charm push` those changes into the ibm-im charm in the store.15:05
mbruzekthe result from that command will likely be ibm-im-1 rather than zero.  I already see the ibm-im charm in the review queue, because you filed a bug. So everything seems correct. You can change the charm code as much as you like before the review.15:06
shruthimahmm thats fine ,actually i had a doubt if we push again with charm push command will it merge with the old one..15:07
mbruzekAfter you push another version up, you should update the bug  with something like this: "please review ibm-im-#" where # is the revision you want reviewed.15:08
shruthimaok u mean bug description?15:09
shruthimambruzek: ok u mean to update bug description ?15:15
mbruzekOr just add a comment, which ever is easier15:15
shruthimambruzek : ok so new process is only to reflect in charm store ...next to raise a bug and link to trunk branch we need to follow the same old process is it ..?15:18
mbruzekshruthima: Yes, we have been working hard on the new process and review queue, but those changes have not been released.15:21
=== CyberJacob_ is now known as CyberJacob
mbruzekshruthima: so for now we need to use the bug to track this change so it can be reviewed.15:22
=== CyberJacob is now known as Guest29413
shruthimambruzek : ok thank you for the information :)15:22
=== marlinc_ is now known as marlinc
mbruzekshruthima: Yes and thanks for asking these questions in #juju, I am sure the questions are useful for other people in this room15:23
=== cargonza_ is now known as cargonza
=== arosales_ is now known as arosales
shruthimahmmm :)15:24
=== hazmat_ is now known as hazmat
mbruzekDoes anyone know how to get to the controller machine in juju 2.0.beta ?15:37
mbruzekOne of my machines failed to provision and has no ip address. I want to get the logs from the controller to add to the bug.15:37
mbruzekbut I don't know how to refer to the controller with juju commands.15:38
aisraelmbruzek: Also wondering about that. I've only found logs once a machine has been created. Before that, debug-log has nothing.15:39
mbruzekaisrael: Yeah this machine is *not* being created and I don't know why.15:40
LiftedKiltmbruzek: juju switch admin; juju ssh 0 ?15:41
mbruzekLiftedKilt: yes that works, thank you for the information.15:43
mbruzekWe should add that to a document somewhere. aisrael do you have a suggested location?15:43
aisraelOhh, good find LiftedKilt.15:45
aisraelmbruzek: https://jujucharms.com/docs/master/developer-debugging15:45
aisraelmbruzek: Do you want to open a bug against docs, or should I?15:45
mbruzekaisrael: I will do that, and create the text which you can review15:45
LiftedKiltmbruzek: yeah it's a little obtuse that machine 0 is hidden in the admin model - you intuitively expect juju machine to show all the machines, but it shows the machines in the selected model.15:45
aisraelmbruzek: ack15:45
mbruzekLiftedKilt: It makes sense to me now you explained it to me.15:46
mbruzekLiftedKilt: thank you for sharing that information with me15:46
LiftedKiltmbruzek: for sure15:46
jcastrohttp://askubuntu.com/questions/755885/is-there-a-way-to-adjust-the-interval-for-the-update-status-hook15:54
jcastroany help on this one?15:54
mbruzekaisrael: Please review my addition: https://github.com/juju/docs/pull/106116:24
DavidRamaoue omw16:25
DavidRamaoups sorry16:25
jcastrobdx: any word from the devopsdays pdx people on if your talk was accepted?16:45
natefinchanyone online who knows about the deployer code?  Seems there's an incompatibility with some TLS changes I made in core last week16:53
tvansteenburghnatefinch: are you talking about the juju-deployer python project, or the new golang deployer code?17:09
natefinchtvansteenburgh: python17:10
tvansteenburghnatefinch: i'm one of the maintainers17:11
natefinchtvansteenburgh: I changed juju-core to only support TLS 1.2 last week... looks like CI found an incompatibility with deployer: http://reports.vapour.ws/releases/3938/job/maas-1_9-deployer-2x/attempt/49#highlight17:12
tvansteenburghnatefinch: okay, i'll take a look soonish17:14
tvansteenburghdpb: fyi ^17:14
natefinchtvansteenburgh: thanks, let me know if there's anything I can do to help... the bug is here: https://bugs.launchpad.net/juju-core/+bug/157669517:15
mupBug #1576695: Deployer cannot talk to Juju2 (on maas2) because :tlsv1 alert protocol version <ci> <deployer> <maas-provider> <regression> <juju-core:Triaged> <https://launchpad.net/bugs/1576695>17:15
tvansteenburghdpb1_: ^17:15
tvansteenburghnatefinch: cool, thanks17:15
=== natefinch is now known as natefinch-lunch
lazyPowertvansteenburgh - do we have a shorter method to determine which unit is a leader in an amulet test, than sentry.run() in a loop?17:32
tvansteenburghlazyPower: nope17:32
lazyPowercool, should i add that under some "common use cases" for the amulet docs?17:33
tvansteenburghlazyPower: either that, or file a bug and we can add a get_leader(service) or something17:34
lazyPowersounds good to me17:34
lazyPowerhttps://github.com/juju/amulet/issues/13117:36
bwallisanyone still experiencing really slow speeds to launchpad/most US hosted ubuntu sites?17:41
bwalliswas happening last night as well17:41
=== natefinch-lunch is now known as natefinch
suchvenuHi18:39
suchvenuI am getting the following error when I did,  juju destroy-environment local18:40
suchvenuERROR cannot connect to API: unable to connect to "wss://10.0.3.1:17070/environment/c9759ee0-88cc-403d-8b6c-aa4e628bf17d/api"18:40
suchvenuAny idea on thsi error ?18:40
LiftedKiltthe openstack-lxd bundle on xenial leaves ceph broken - all the pgs are stuck in creation18:42
LiftedKilthas anyone worked with that or found a fix? It works on trusty, so it must be a xenial quirk18:42
lazyPowersuchvenu - which juju version?18:55
suchvenu1.2518:57
suchvenuUbuntu Trusty version18:58
lazyPowersuchvenu - sudo lxc-ls --fancy, do you see any lxc containers listed?18:58
lazyPoweroo local provider, hang on there's a service you should have running not a container18:59
suchvenucharm@islrpbeixv665:~/charms/trusty/ibm-db2$ sudo lxc-ls --fancy [sudo] password for charm: NAME                       STATE    IPV4  IPV6  AUTOSTART --------------------------------------------------------- juju-precise-lxc-template  STOPPED  -     -     NO juju-trusty-lxc-template   STOPPED  -     -     NO charm@islrpbeixv665:~/charms/trusty/ibm-db2$19:01
lazyPowersuchvenu - sorry that was a redherring. Its been a moment since i've used the local provider on 1.2519:05
lazyPowersuchvenu - can you pastebin the output of initctl list for me?19:06
suchvenuhttp://pastebin.ubuntu.com/16194903/19:09
=== bsod90 is now known as pacavaca
lazyPowersuchvenu - juju destroy-environment -y --force local19:17
lazyPowersuchvenu - as you were trying ot remove it, this will clean up the stale configuration files, and you can re-bootstrap afterwords19:18
lazyPoweri didn't see the upstart job listed for the local environment, so i think it just didn't complete the job of cleaning up after itself from a prior juju destroy-environment.19:18
suchvenuok19:19
tvansteenburghstub: https://bugs.launchpad.net/postgresql-charm/+bug/1577544 fyi19:37
mupBug #1577544: Connection info published on relation before pg_hba.conf updated/reloaded <PostgreSQL Charm:New> <https://launchpad.net/bugs/1577544>19:37
=== FourDollars_ is now known as FourDollars
=== Tribaal_ is now known as Tribaal
=== blr_ is now known as blr
thedacgnuoy: See my last comment on https://review.openstack.org/#/c/308070/ and consider a +220:51
=== natefinch is now known as natefinch-afk
pacavacahey guys! when I'm doploying something (openstack) using juju, each machine gets several lxc containers and one called juju-xenial-template (smth like this). I noticed that this template container already has some predefined configuration for my NICs (eth0 and eth1). In particular, it assigns static IPs on one of them and I don't want that. How do I change this template (for all nodes), so that IPs are21:32
pacavacaalways assigned by DHCP?21:33
cory_fukwmonroe: You got a PR for that layer-basic change?22:11
kwmonroei do not cory_fu.  i'm not sure it's good. http://paste.ubuntu.com/16196042/  do i need to pip install requirements.txt?  should i activate vs including PATH extensions?  is there potential conflict with .venv for other charms (ie, should i call it .venv-newer-tox)?22:13
magicaltroutkwmonroe: you in for the full conference or just flying in and out?22:14
kwmonroemagicaltrout: i'm in it for the long haul.  Sun-Thu.22:14
cory_fuYou don't need to pip install requirements, because tox will handle that.  However, since it's currently doing a sudo pip install, why not just stick with that?22:14
magicaltroutnice22:14
magicaltroutthey speak funny in canada22:14
kwmonroei'll learn 'em22:15
magicaltrouthehe22:15
kwmonroecory_fu: not sure what you mean by "why not just stick with that".22:18
cory_fukwmonroe: http://pastebin.ubuntu.com/16196470/22:21
cory_fukwmonroe: https://github.com/juju-solutions/layer-basic/pull/6622:24
* magicaltrout writes some slides22:33
magicaltroutbetter late than never22:33
kwmonroecory_fu: marcoceppi:  quick tox fix for charmbox: https://github.com/juju-solutions/charmbox/pull/33/files22:41
kwmonroethis moves the tox fix to cb instead of layer-basic's Makefile since you guys are in such violent disagreement over cory's pull 6622:42
marcoceppikwmonroe cory_fu I'd prefer this, I've honestly put tox in a venv that I activate when i do charm testing stuff, this fixes it where you need it, but we still need to consolidate charm test for charm 2.2 to be docker/lxd ootb22:42
cory_fumarcoceppi: Why isn't it using charmbox?  That's what we've standardized on for all of our CI infra22:43
marcoceppicory_fu: because, time.22:43
marcoceppicory_fu: also, the openstack engeineers depend on the old test runner22:43
marcoceppiwe need to get them onto bundletester, then get charm test to just boot the charmbox container and run tests22:44
admcleod1is there any way to get info about a unit, from within another unit, without a relation to it22:50
marcoceppiadmcleod1: no, not really22:51
marcoceppiadmcleod1: charms only know about what they are connected to, implicit querying of other services would lead to a disaster of having toplogies that require other services but without an explicit relation for the operator to know they're logically connected22:51
cory_fuadmcleod1: juju run service/0 'unit-get private-address'22:52
admcleod1cory_fu: from with another unit though22:53
admcleod1marcoceppi: right22:53
cory_fuadmcleod1: But what you really want to do is make sure you expose the namenode and make sure that the namenode is listening on all addresses and then it should work22:53
cory_fuadmcleod1: With a relation.  For the dfs-copy action, we should make it work with the public address22:54
admcleod1cory_fu: there is that, but will trying to copy data over the public address be an issue with some installations?22:54
admcleod1s/address/interface22:54
cory_fuIt should work, too, we're probably just missing one of: listen on all addresses (0.0.0.0), open-port on the correct port, juju expose namenode22:54
cory_fuYes, it's not ideal, but you don't really have any choice if one of the namenodes is not juju deployed.  For two juju deployed services, we'd want the relation, like we discussed22:55
admcleod1yeah true22:55
cory_fuAnyway, I have to EOD22:56
admcleod1cya22:56
magicaltroutcory_fu's mrs has him tied around her little finger.....22:57
magicaltroutoh no, he's just sensible and doesn't work 18 hour days22:57
kwmonroeadmcleod1: if you're going to adjust apache-hadoop-namenode to listen on all interfaces, you can do something like i did for bigtop recently: https://github.com/juju-solutions/layer-apache-bigtop-namenode/commit/ac0c472707e1f48ccbf416f1c1eb2e189b6bd8e922:59
admcleod1kwmonroe: i guess ill have to, seems a bit dodgy though23:01
admcleod1kwmonroe: maybe an action to do it temporarily?23:03
kwmonroeadmcleod1: make it less dodge by creating a new dist.yaml port called "dfs-copy" that's "exposed_on: totally_dodgie", then make the action expose "totally_dodgie", do the copy, then unexpose it.23:04
admcleod1heh23:07
admcleod1kwmoroe: yeah but more because its listening on all interfaces23:07
admcleod1kwmonroe: ^23:07
kwmonroeoh, i don't think it's too spookie to listen on all interfaces.  any when we migrate services to hosts with different IPs, it's nice to not have to reconfigure.23:10
admcleod1kwmonroe: i know a few network admins who might disagree.. but ok lets do it! :}23:20

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!