=== kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === dimitern is now known as dimitern_off === Amir_ is now known as Guest21093 === TimNich_ is now known as TimNich === TimNich_ is now known as TimNich === TimNich_ is now known as TimNich [11:43] Hey there! I'm trying to deploy juju on a public openstack provider(cloudvps) but when bootstrapping I get the following message: http://privatepaste.com/afbed44133 [11:43] any clue? [12:05] Hi! I have added a unit to a service but it's stuck in pending. There is no /var/log/juju/unit-*.log on the server but the output of /var/log/juju/machine-*.log shows an error: http://privatepaste.com/0a4646aa53 [12:05] Does anyone know what is the problem? [12:55] Roconda: some debug info to look into with a quick google search of your error: http://askubuntu.com/questions/475348/juju-bootstrap-no-data-for-cloud https://bugs.launchpad.net/juju-core/+bug/1242476 [12:55] Bug #1242476: Bootstrap fails with --upload-tools on private openstack cloud

[12:55] Roconda: basically checking the images available and the url for the list of images/etc [13:07] hello everone [13:07] *everyone [13:08] Someone here knows a bit about LXC issues with Juju? [13:25] rick_h_: thanks! Got it working. Had to add an image manually and add --meta-source and --upload-tools to the bootstrap command [13:31] Roconda: awesome [13:32] Nice === kadams54-away is now known as kadams54 [14:14] xetqL: what's your question? [14:40] hi marcoreppi, i'm trying to deploy some services with juju and i wish i could create lxc container on remote machines (with maas) but my lxc container are spinning in pending ... [14:41] I think it's a dns problem because i cannot fetch some archive but the remote machine itself is connected to internet and can ping google it's just the lxc [14:42] I can deploy service on root container without any problem === kadams54 is now known as kadams54-away [15:01] xetqL: logs for that machine would be very helpful, /var/log/juju/machine-#.log for example on the host where you're trying to spin up LXC machines [15:06] hello [15:15] a lot of error /dev/mapper/control: open failed: Operation not permitted [15:15] Failure to communicate with kernel device-mapper driver. [15:15] Check that device-mapper is available in the kernel. [15:15] Command failed [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty/main bridge-utils amd64 1.5-6ubuntu2 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty/main msr-tools amd64 1.3-2 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty/main cpu-checker amd64 0.7-0ubuntu4 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty/main liberror-perl all 0.17-1.1 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main git-man all 1:1.9.1-1ubuntu0.1 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://archive.ubuntu.com/ubuntu/ trusty-updates/universe rsyslog-gnutls amd64 7.4.4-1ubuntu2.5 [15:15] Temporary failure resolving 'archive.ubuntu.com' [15:15] Err http://security.ubuntu.com/ubuntu/ trusty-security/main git-man all 1:1.9.1-1ubuntu0.1 [15:15] Temporary failure resolving 'security.ubuntu.com' [15:15] <4>init: plymouth-upstart-bridge main process (888) terminated with status 1 [15:16] Stopping landscape-client daemon [15:16] ...fail! [15:16] * Stopping rsync daemon rsync [15:16] ...done. [15:16] * Stopping open-vm guest daemon vmtoolsd [15:16] ...done. [15:16] * Asking all remaining processes to terminate... [15:16] ...done. [15:16] * All processes ended within 1 seconds... [15:16] ...done. [15:16] * Deactivating swap... [15:16] ...fail! === Guest62484 is now known as rcj [15:46] I am running ubuntu-14.04.2 and juju 1.21.3 building and openstackHA. I attempted to start 3 sessions of rabbitmq in lxc. Instances 0 and 2 started just fine, instance 1 failes to start rabbitmq. /var/log/rabbitmq/startup_log contains:Error description: [15:46] {could_not_start,rabbit, [15:46] {bad_return, [15:46] {{rabbit,start,[normal,[]]}, [15:46] {'EXIT', [15:46] {rabbit,failure_during_boot, [15:46] {error, [15:46] {timeout_waiting_for_tables, [15:46] [rabbit_user,rabbit_user_permission,rabbit_vhost, [15:46] rabbit_durable_route,rabbit_durable_exchange, [15:46] rabbit_runtime_parameters, [15:46] rabbit_durable_queue]}}}}}}}; What is it doing wrong and how do I correct it? I would like to understand what went wrong so I can avoid it on the retry and successive builds. === kadams54-away is now known as kadams54 [16:11] drbidwell: please use pastebins for multiline output and post link in irc channels.. paste.ubuntu.com [16:12] xetqL: ^ === kadams54 is now known as kadams54-away [17:42] aisrael: when you reviewed this mongodb MP did you get a collision during the merge? [17:43] https://code.launchpad.net/~james-page/charms/trusty/mongodb/kilo-support/+merge/247123 <- that guy [18:55] lazyPower: you know what? I did, and forgot to mention it. Another merge must have updated charm helpers as well (which is all this one is doing, too) [18:55] aisrael: that MP was declined by you :) [18:55] aisrael: no rush - but when you get that sorted ping me and i'll approve the final outcome. [18:55] lazyPower: another another one :) One already approved [18:55] ah ok [18:55] so one got merged then? [18:56] i'm multi-tasking and admittedly didnt look @ the mongodb charm tree in teh store to see what was up there. [18:57] an update of charm-helpers, but it may not be current enough for kilo support, which is why I approved james page's merge [18:59] I can follow up on that MP and ask directly [18:59] seems like the correct path forward [19:01] Thanks, lazyPower. [19:01] cheers === arbrandes_ is now known as arbrandes === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === ericsnow is now known as ericsnow_afk [23:13] So today i've been playing around with juju and openstack. Found some issues when trying to bootstrap that it could not assign a floating ip and could not connect to the spawned juju machine. I've tried setting [23:13] 'authorized-keys-path: /home/vagrant/.ssh/' but it doesn't seem to work. [23:24] anyone has a clue? [23:24] Roconda: are you sure that setting takes a directory rather than a filename? [23:28] sarnold: just tried it, not working, time out. [23:29] Roconda: does ssh to that host work? [23:29] sarnold: yes, it just prompts a passwd auth instead of logging in [23:40] ERROR juju.cmd supercommand.go:323 failed to bootstrap environment: waited for 2m0s without being able to connect: Permission denied (publickey,password). [23:51] Roconda: are you on an OSX host running the juju vagrant image to interface with your openstack env? [23:52] lazyPower: nope, elementary OS [23:53] Roconda: ok, makes sense i was trying to figure out where vagrant fit into the overall thing [23:53] allright - so your Openstack Env is stood up and you're trying to bootstrap into that OpenStack env correct? [23:54] lazyPower: yep