/srv/irclogs.ubuntu.com/2017/05/31/#juju.txt

jac_cplaneis there anyway to change the admin_domain for keystone ?    it seems that keystone charm creates admin_domain as default.  I need to have this charm create the domain "default" instead of admin_domain00:59
=== scuttlemonkey is now known as scuttle|afk
kjackalGood morning Juju world!07:46
Hetfieldmorning all. i have deployed an openstack cloud via juju. now i want to deploy services adding the same openstack in the juju cloud08:15
Hetfieldunfortunately it fails08:15
Hetfieldjuju add-cloud openstack1 tenant-demo-env.yaml ERROR cannot unmarshal yaml cloud metadata: yaml: unmarshal errors:   line 4: cannot unmarshal !!str `userpass` into []cloud.AuthType08:16
Hetfieldthis is the yaml08:16
Hetfieldhttps://paste.ubuntu.com/24724275/08:16
=== Salty is now known as Guest45701
Hetfieldok, i fixed it by using [userpass] syntax09:00
NazHi, Whenever I create an new service, the first TYPICAL ERROR message I get from juju debug-log reads like follows:  "unit-name-1: 11:54:06 ERROR juju.worker.dependency "metric-collect" manifold worker returned unexpected error: failed to read charm from: /var/lib/juju/agents/unit-name-1/charm: stat /var/lib/juju/agents/unit-name-1/charm: no such file or directory"09:00
=== disposable3 is now known as disposable2
=== mimizone_ is now known as mimizone
=== SaMnCo_ is now known as SaMnCo
NazHowever, Sshing to the related machine, and checking the full, it's found indeed however, the owner and the group are ROOT:ROOT09:01
Nazroot@juju-8aa58b-21:/var/lib/juju/agents/unit-name-1/charm# pwd /var/lib/juju/agents/unit-name-1/charm09:01
Nazroot@juju-8aa58b-21:/var/lib/juju/agents/unit-name-1/charm# ll total 583 drwxr-xr-x 15 root root     30 May 31 08:54 ./ drwxr-xr-x  4 root root      7 May 31 08:54 ../ drwxr-xr-x  2 root root      8 May 31 08:54 actions/ -rw-r--r--  1 root root    670 May 31 08:54 actions.yaml drwxr-xr-x  2 root root      3 May 31 08:54 bin/ -rw-r--r--  1 root root 249687 May 31 08:54 name.svg -rw-r--r--  1 root root   6659 May 31 08:54 config.yaml -rw-r--r09:02
NazIs it because, no metrics are yet defined on such charm? But why would it necessitates to call metric-collect as first thing?09:05
mattywNaz, that looks like this bug: https://bugs.launchpad.net/juju/+bug/165625809:15
mupBug #1656258: metric-collect returned unexpected error <logging> <metrics-collector> <juju:Fix Committed by cmars> <juju 2.1:Won't Fix> <https://launchpad.net/bugs/1656258>09:15
Naz@Mattyw, Yes, correct, thank you, it's mentioned that this bug is fixed in 2.2.rc1 and won't be fixed in 2.1.209:21
mattywNaz, I don't think it's a problem though - the unit should continue working as expected09:21
Naz@Mattyw, Yup, correct :)09:21
NazExcuse me, I am still learning, I shall check the issues in bug repositories next time :)09:23
mattywNaz, no problem - I only knew the bug was there because I remember discussing it a few weeks ago09:23
Naz@Mattyw, Great, thank you my friend, you are the man :)09:24
NazI see: "The current stable version of Juju is 2.1.3 and is recommended for everyday production use."09:26
NazI am running on 2.1.2! How could I upgrade to latest stable without losing my models/apps?09:26
Nazhttps://jujucharms.com/docs/stable/reference-install, isn't it for install from scratch?09:27
NazFound it :), juju upgrade-juju --agent-version 2.1.309:36
chrome0Question regarding network spaces: afaict juju/state/machine_linklayerdevices.go , it seems that in order for a space to be considered as available on a host, that host must have a iface *with an ipaddr* in the spaces subnet, is that correct?09:51
chrome0The problem is, I'd like to have a metal deployed by maas 2.2, with a bridge iface in a vlan'ed space but w/o ipaddr, and handing out ipaddr only in containers09:55
chrome0Those are pub ipv4 addr and therefore scarce09:55
chrome0Getting an error message when deploying a test container -- cannot start instance for machine "1/lxd/2": unable to setup network: host machine "1" has no available device in space(s) "space-api"09:57
chrome0But, icb reading that source wrong, IANAGoDeveloper09:59
chrome0Fwiw, this is maas 2.2 and juju 2.1.310:00
=== MmikeM is now known as Mmike
chrome0Interestingly, in the above ^^ ctxt, the constraints matcher seems less picky. I can add-machine --constraints spaces=space-api and get the machine deployed (it warns about an address-less device though)10:43
rick_hchrome0: so I know that the goal is to support what you're doing. I don't think we're there to support it yet. jam is the best person to confirm if there's any trick to getting it working under current conditions11:15
rick_hmaybe wpk11:15
jamrick_h: I'm missing the context from chrome0 had to restart my comp11:21
rick_hjam: ah sorry, he's wanting to use maas to get the host w/o an ipaddr on the device passed to the container11:21
jamrick_h: chrome0: wpk has been digging more closely into being able to represent what space a device is in when it doesn't have an IP address, but right now, when we try to link up charms to devices, etc11:23
jamwe explicitly enumerate devices, find their IP addresses, and then compare them to the subnets we know about11:23
jamwe want to change that, but its the current logic11:23
jamso again, you can probably get the right machine11:23
jambut things like binding the charm to the right device won't quite work right11:24
rick_hty jam11:29
burton-ausaxw_ develop branch seems in a high activity right now...11:54
burton-ausaxw_ Updates were rejected because the tip of your current branch is behind its remote counterpart.11:54
burton-ausaxw_ solved11:57
chrome0Thanks rick_h and jam , was afraid you'd say that. Is there a bug filed about this? If not I'll create one12:25
jamchrome0: there is a bug, but i'd have to look it up12:47
chrome0Cheers, I'll see if I can find it12:48
jamchrome0: https://bugs.launchpad.net/juju/+bug/165937612:49
mupBug #1659376: should be a way to specify space binding for maas "unconfigured" interface <cdo-qa-feature> <network> <oil> <oil-2.0> <uosci> <OpenStack neutron-gateway charm:New> <juju:Triaged> <neutron-gateway (Juju Charms Collection):Invalid> <https://launchpad.net/bugs/1659376>12:49
jamI think is the one I was thinking12:49
chrome0Yup, my usecase is a bit different but this should cover it12:52
=== scuttle|afk is now known as scuttlemonkey
lazyPowerSimonKLB: i summon thee (if you're summonable)14:50
SimonKLBlazyPower: whats up?14:50
lazyPowerSimonKLB: i'm tapping Cynerva to lend a hand with our networking conundrum while i step away to run some quick errands14:51
Cynervao/14:51
SimonKLBhey!14:51
lazyPowerCynerva: this is simon, he's got an issue with pod networking in lxd14:51
Cynervahowdy14:51
Cynervaokay14:51
lazyPoweri thought it was kube-proxy related but that doesn't appear to be the case14:51
lazyPowercant resolve VIP's in a lxd worker's pods :|14:51
Cynervahmm14:51
SimonKLBi am able to access the service IPs from the worker host14:52
SimonKLBso i think the forwarding is fine14:52
SimonKLBservice -> pod that is14:52
SimonKLBbut pod -> service is not working14:53
Cynervaokay, thinking for a bit14:53
SimonKLBalso, i can see the traffic on the cni0 interface14:53
Cynervai'm trying to remember, i've seen something like this before but don't remember the circumstances14:54
Cynervais this across workers? or pod->service within a single worker?14:55
SimonKLBsingle worker14:55
Cynervaokay, i dunno14:59
Cynervai'm suspicious kube-proxy is still doing something weird14:59
Cynervawith traffic that comes from the pod IP range14:59
CynervaSimonKLB: can you send me the output of `iptables-save` and `cat /var/snap/kube-proxy/current/args` from the worker?15:00
SimonKLByup15:00
roadmrhello jujuers. I have a couple of subordinate charms in "allocating - waiting for machine" state (weird for a subordinate! the machine it's being deployed to has already been provisioned and the main service is ok). The log says this: 2017-05-31 08:29:17 ERROR juju.worker.proxyupdater proxyupdater.go:164 can't connect to the local LXD server: LXD socket not found; is LXD installed & running?15:44
roadmrany ideas why it seems to want lxd?15:44
Hetfieldhi all, i had to open a bug for kubernetes bundle not honoring proxy settings16:12
Hetfieldhttps://bugs.launchpad.net/bugs/169474316:12
mupBug #1694743: kubernetes-[master,worker] snap install fail due to missing proxy <Juju Charms Collection:New> <https://launchpad.net/bugs/1694743>16:12
Budgie^Smoreo/ juju world16:31
vlad_Hey quick question if anyone has the time... I'm just running the base openstack bundle on juju and wondering how I connect to the cloud it deploys? I can figure out how to shell into the nodes, but have no idea where the credentials are for the openstack cloud18:07
mmcchi vlad_ - there are notes in the Readme for the openstack-base bundle about how to connect. See the section "Accessing the cloud" at https://jujucharms.com/openstack-base/18:15
mmccactually, start two paragraphs earlier at "Ensuring it's working" :)18:16
mmccit suggests you download the bundle, but you could alternatively just get this file https://api.jujucharms.com/charmstore/v5/openstack-base/archive/novarc18:17
mmccfor the default env vars that'll let the clients log in18:17
vlad_Ahhh that's the exact file I was looking for sorry didn't see the link to it my mistake18:18
vlad_mmcc: thanks kindly18:19
mmccvlad_: you're welcome, glad I could help!18:19
=== Guest____ is now known as bladernr-lex
tychicusI realize that this probably goes against the cattle vs pet convention, but is it possible to specify the hostname or naming convention for a new machine?21:00

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