=== liam_ is now known as Guest18768 [12:42] gnuoy, jamespage: I need a review on this if one of you have a moment. https://code.launchpad.net/~corey.bryant/charm-helpers/install-warning/+merge/264340 === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away [15:47] thedac, hey - I did take a look through your service status MP - looks like a good start [15:47] jamespage: great, thanks [15:47] one comment - I think we need to differentiate between BLOCKED - relations not made, and PENDING - relation made, pending presentation of data [15:48] ok [15:48] we may not quite have that with the current context model - its a bit black and white complete/incomplete [15:48] so we may need to add some helpers to context to determine that information [15:48] yeah, I'll have to dig a bit more to get to that [15:49] thedac, awesome [15:49] thanks for the feedback [15:49] there's also "waiting" which is like "I know you've connected me, but I don't have data from the relation yet" [15:50] yeah, that would make sense as the status. It is getting at that information in the charm that will be the work. [16:38] if i want to change settings for an environment can anything be done programmatically? if so, would it be better to edit environments.yaml anyway? [16:45] pmatulis: juju set-env [16:46] jrwren: looking, thanks [17:41] Hi All, After cleaning the environment using juju bootstrap, juju status command is hanging. How to resolve this ? [17:51] suchvenu: what do you mean, cleaning? [17:51] you mean you destroyed-environment, ran bootstrap and now status doesn't work? [17:53] i ran juju destroy-environment local and then ran bootstrap [17:54] juju status and juju debug-log not working now [17:54] suchvenu: can you run `juju status --debug` ? [17:55] 2015-07-10 17:55:23 INFO juju.api apiclient.go:261 dialing "wss://localhost:17070/environment/e4301ecd-0e2c-4656-8fc1-758ce461f350/api" 2015-07-10 17:55:23 DEBUG juju.api apiclient.go:267 error dialing "wss://localhost:17070/environment/e4301ecd-0e2c-4656-8fc1-758ce461f350/api", will retry: websocket.Dial wss://localhost:17070/environment/e4301ecd-0e2c-4656-8fc1-758ce461f350/api: dial tcp 127.0.0.1:17070: connection refused 2015-07-10 [17:56] suchvenu: can you paste teh output of `sudo initctl list | grep juju` ? [17:56] ok [17:56] Ccharm1@islrpbeixv666:~/charms/trusty$ sudo initctl list | grep juju [sudo] password for charm1: charm1@islrpbeixv666:~/charms/trusty$ [17:56] nothing there [17:57] suchvenu: what version of ubuntu are you on? [17:58] trusty [17:59] suchvenu: run `juju destroy-environment --force local` then bootstrap again [18:00] ok [18:03] yes, working now [18:03] yes, working now :-) [18:05] Thanks marcoceppi [18:05] suchvenu: no worries! [18:12] i'm using the local provider with 'container: kvm' . doing 'juju add-machine' gets me a machine (as seen with 'juju status') but not with 'virsh list --all'. possible that libvirt is not being used? [18:14] (output to 'juju status' here: http://paste.ubuntu.com/11857271/) [18:18] pmatulis: if you run sudo lxc-ls --fancy do you see the ubuntu-local-machine-1 listed? [18:19] lazyPower: no [18:19] lazyPower: to be clear, i don't want LXC at all [18:20] lazyPower: i thought i could just get some kvm-based machines [18:20] you can, and virsh should have listed that machine.. [18:20] ok [18:20] not sure if should is appropriate [18:20] juju keeps containers in different paths [18:20] and it may not be registered in virsh [18:22] hm, that is plausible [18:23] anyway, i'm logged into this machine fwiw. still digging [18:29] the machine's log file: http://paste.ubuntu.com/11857329/ [18:37] lazyPower: i don't get it. this machine is indeed an LXC container [18:37] I suspected that might be the case looking at the IP of the machine and its name. [18:38] i created a new file under /etc while logged into it and the host shows it (sudo ls -l /var/lib/lxc/ubuntu-local-machine-1/rootfs/etc) [18:38] lazyPower: gah, using sudo with 'lxc-ls' shows it [18:39] ah, i had sudo up above :) i guess i should have called it out [18:42] my bad [18:44] lazyPower: so question remains: how do i get myself a kvm guest? [18:48] do you have the juju-local-kvm package installed? (i'm not sure if this is still required, but it was at one point) [18:50] lazyPower: just 'juju-local' but i see the other package is available for install [18:50] the container: kvm - should make it use kvm, and that package should get you all the prerequisits. [18:52] lazyPower: installed it but i see it only contains /usr/share/doc* [19:36] hi [19:37] I see the following error in the isntall hook of my charm [19:37] unit-db2-0[933]: 2015-07-10 19:32:06 INFO unit.db2/0.install logger.go:40 Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main binutils amd64 2.24-5ubuntu13 unit-db2-0[933]: 2015-07-10 19:32:06 INFO unit.db2/0.install logger.go:40 Could not resolve 'archive.ubuntu.com' [19:37] I am trying to do some sudo apt-get isntall commands [19:51] I am trying using juju version 1.24.2 where I am getting the above issue [19:55] I have another environment in which juju version 1.23.2 is running and I dont see this error there with the same code base [20:09] suchvenu: seems like a dns issue [20:10] i would `juju ssh db2/0` and try to apt-get install something [20:17] getting same error from the juju machine also [20:17] The following NEW packages will be installed: binutils 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2,076 kB of archives. After this operation, 11.7 MB of additional disk space will be used. Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main binutils amd64 2.24-5ubuntu13 Could not resolve 'archive.ubuntu.com' E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/b/binutils/binutils_2.24 [23:28] lazyPower: my problem was that i neglected to destroy and bootstrap after having changed my yaml file [23:31] pmatulis: that'll do it! thanks for circling back [23:31] i had not thought of that