/srv/irclogs.ubuntu.com/2017/03/23/#juju-dev.txt

anastasiamacwallyworld: thumper:axw:babbageclunk: PTAL https://github.com/juju/juju/pull/7143, fixes a bug :D00:04
anastasiamacmore like a gap than a broken functionaility...00:04
babbageclunkanastasiamac: just having lunch, but I'll take a look afterwards (if someone else doesn't!)00:06
anastasiamacbabbageclunk: \o/00:07
wallyworldanastasiamac: babbageclunk: i'm not sure we've agreed to the approach yet. it's under discussion via email00:17
wallyworldwe need to get agreement what they want to do is supported and correct first00:18
anastasiamacwallyworld: obviously not parties are on this email trail.... maybe discussing it in the bug will be better/more effective means as communication00:18
axwanastasiamac: reviewing00:19
wallyworldanastasiamac: agreed in principal. but we don't want to polluate the bug with lots of back and forth. the summarised outcomes can be added though00:19
axwwallyworld: this change is unintrusive, I don't think we need to have any more discussion before landing this particular change00:19
axwwallyworld: this is an alternative to what was being proposed, which was adding pre-populated relation settings00:20
wallyworldaxw: that is true. but i was concerned it is a solution to a problem they didn't need to have if things were deployed the recommended way. i'd have to re-read the email trail00:21
axwwallyworld: ehh except there's some weirdness in the PR, so maybe I'm still misunderstanding the issue.00:23
wallyworldright00:23
wallyworldi'm hesitant because i'm not sure w'ere all on the same page00:23
axwwallyworld: yeah I'll continue discussions.00:26
anastasiamacwallyworld: sure but now that the PR is up, email communication is not best, especially if it excludes ppl that r blocked byy the bug and r proposing solutions00:28
wallyworldanastasiamac: the bug is not the place to have detail design discussions. status updates etc sure00:31
wallyworldor steps to repro etc etc00:32
axwanastasiamac wallyworld: I'm taking the discussion to the PR.00:41
wallyworldyup, +100:41
axwand will take it back to email if that becomes unwieldy00:41
wallyworldaxw: FYI, as discussed, this is the CDO vsphere bug https://bugs.launchpad.net/juju/+bug/166948302:44
mupBug #1669483: [2.1] juju bootstrap fails when there is no VM in vsphere datacenter or all VMs are in folders <cdo-qa-blocker> <oil> <oil-2.0> <vsphere> <juju:Triaged> <https://launchpad.net/bugs/1669483>02:44
axwwallyworld: okey dokey02:45
axwwallyworld: might be hard to test, since larry is away02:46
axwI don't think I should be deleting existing VMs02:46
wallyworldyeah, best effort and all that02:46
=== mup_ is now known as mup
cmarshi, i have a fix for LP:#1675214. can i get a review? https://github.com/juju/juju/pull/714703:52
mupBug #1675214: destroy-model failed because could not determine model SLA level <ci> <destroy-model> <regression> <juju:In Progress by cmars> <https://launchpad.net/bugs/1675214>03:52
thumperjam: to be honest, I think we don't care for the use case you mentioned03:56
thumpernot really, not now03:56
thumperhowever, if you think we do, I could add a txn-revno assert back in03:57
thumperjam: we do do a txn-revno assert in 2.x03:57
wallyworldcmars: looking04:07
cmarswallyworld, thanks!04:07
wallyworldcmars: yeah, or account for the facade version for each model - won't be too hard to do that04:09
wallyworldlgtm for the temp fix - just code deletion really04:09
cmarswallyworld, ok thanks!04:10
wallyworldbabbageclunk: not sure if you are able to squeeze in a review before your EOD https://github.com/juju/juju/pull/714404:11
stokachufirst cut of conjure-up on macOS done \o/04:13
babbageclunkwallyworld: that's a tiny one! looking now04:13
wallyworldbabbageclunk: that's what all the girls say too :-)04:13
wallyworldstokachu: well done!04:14
stokachuwallyworld: hopefully that'll increase our userbase by a lot04:14
stokachui need to look into xhyve though for localhost deployments04:15
stokachulike docker does04:15
wallyworldstokachu: maybe? how many of our target audience  ueses macs? i personally hate them04:15
stokachuwallyworld: good question, im not sure04:15
stokachuword is though all the conferences people use macs04:15
stokachukubecon etc04:15
wallyworldinteresting04:15
wallyworldwe should collect stats on that04:16
stokachuwe do04:16
babbageclunkdefinitely true at Python conferences I've been to04:16
stokachunice, yea i think having a localhost deployment mechanism will be handy04:16
stokachubasically xhyve to boot ubuntu04:16
stokachuthen do some magic there to wire it up04:17
stokachuor vsphere would be nice here too i think04:18
babbageclunkwallyworld: reviewed04:37
jambabbageclunk: so I think we do need to have a better primary key than CIDR for subnets, but probably not worth you fixing right now. (you can't fix all the bugs in networking on your own :)04:38
babbageclunkjam: :) fair enough!04:41
wallyworldjam: that's exactly what i sid too :-)04:44
wallyworldbabbageclunk: thanks for review04:44
jambabbageclunk: and my other point was "we won't really know if we have the right data until we actually go to *use* the data", (we're only recording it with your patch)04:45
jambut rough glance looks like its the right thing, and we can iterate from here.04:45
* jam takes the dog out04:46
wallyworldbabbageclunk: i replied to one of you comments, see if if makes sense?04:50
axwjam: 1:1? wallyworld is here too05:02
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mwhudson_ is now known as mwhudson
mupBug #1468752 changed: "juju ssh" adds an additional strings to all commands when used on Windows, in interactive mode <ssh> <windows> <juju:Fix Released by07:36
mupgz> <juju 2.0:Fix Released by gz> <juju 2.1:Fix Released by gz> <juju-core:Won't Fix> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1468752>07:36
mupBug #1616149 changed: Incompatible protocol between older client and candidate server <ci> <regression> <test-failure> <juju-core:Won't Fix> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1616149>07:36
mupBug #1637267 changed: Juju fails to restore state-server on xenial <ci> <juju-core:Won't Fix> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1637267>07:36
mupBug #1616832 changed: stuck rsyslogd causes mongodb to block <eda> <needs-ci-test> <sts> <juju:Triaged> <juju-ci-tools:Triaged> <juju-core:Won't Fix> <juju-core 1.25:Won't Fix> <https://launchpad.net/bugs/1616832>07:48
=== frankban|afk is now known as frankban
wallyworldaxw: you happy to go with "not supported" initially for nova networks and subnets in heather's PR ?09:07
* axw looks09:11
axwwallyworld: hm. not sure, I'll need to check the behaviour of the code that calls Subnets09:13
wallyworldaxw: yeah, if the interface claims support and then the other methods error, might not be good09:13
axwwallyworld: have the changes to discover subnets already been made09:26
axw?09:26
wallyworldaxw: in the worker, yeah09:27
axwoh yeah09:27
axwwallyworld: we at least need to look for NotSupported in the discoverspaces worker, in discoverSubnetsOnly09:29
wallyworldaxw: yeah, i'd rather the provider not lie to the worker though09:29
axwwallyworld: welp, the only other option I guess is to return separate Environ implementations when nova and neutron are supported. I'm not sure if that's feasible though, because opening an an Environ is not supposed to make any API calls09:31
wallyworldyeah, also true. maybe handle not supported in the worker with a todo to fix the openstack provider to return subnets for nova09:32
axwwallyworld: yep09:32
axwwallyworld: FWIW, I'd prefer if we had an Environ.Networker method, which every Environ was required to implement. it would return an Environ or a NotSupported error09:33
wallyworldno argument from me there09:33
axwwallyworld: and then Networker would have methods for checking support for subnets, spaces, etc.09:33
wallyworldyep09:33
wallyworldi don't like the current implementation09:33
jamwpk: ping12:30
wpkjam: pong12:32
jamhi wpk, I wanted to go over some of the key bugs, though if you want it can wait until standup I suppose12:39
jamI'm going to be gone over the weekend, so I was hoping to chat with you about some next steps12:39
wpkI'm ready, should we talk here or maybe just join standup hangout now?12:43
jamsure, brt12:46
jamwpk: i'm there now12:47
jamwpk: https://github.com/juju/juju/pull/7119 reviewed13:21
jamsinzui: what triggers someone to get an "affiliated" icon in Launchpad?13:38
jamI'd like to get WPK a Juju sticker so that I don't accidentally pick some other Witold13:39
sinzuiwow you challenge me13:39
sinzuijam: I think it is show when the user is a member of the owner or driver teams.13:40
jamwell, he's in '~juju-core' afaict13:40
sinzuijam, we forgot to add him to ~juju13:41
jambut it looks like there is ~juju-hackers he wasn't part of13:41
jamI just did13:41
jam"Juju Hackers" aka ~juju13:41
jamsinzui: thanks for the pointer13:41
jamsinzui: btw wpk's current branch https://github.com/juju/juju/pull/7119 is likely to want a feature tests13:42
jamor an update to whatever we currently have that 'apt-proxy' works13:42
jamanyway I'm out for a bit13:42
sinzuijam, yep, that was the one I was curious about. I reported bug 1635633 and am eager to close it13:43
mupBug #1635633: assess_proxy does not test apt proxies <gap> <proxy> <juju-ci-tools:Triaged> <https://launchpad.net/bugs/1635633>13:43
=== frankban is now known as frankban|afk
wallyworldbabbageclunk: did you see bug 1675546?20:51
mupBug #1675546: container networking broken in GCE <ci> <gce-provider> <lxd> <network> <regression> <juju:Triaged by 2-xtian> <https://launchpad.net/bugs/1675546>20:51
rick_hwallyworld: anything to chat on today?22:02
wallyworldrick_h: not as such. very happy about the latest memory profile22:02
rick_hwallyworld: +122:16
babbageclunkwallyworld: yup, chasing it, but had to rush off to the doctor - back now.22:17
wallyworldty22:17
wallyworldwe will release beta1 regardless22:18
wpkI'm having problems with bootstraping on maas, I'm constantly getting22:25
wpk/var/lib/juju/nonce.txt does not exist22:25
wpk23:23:13 DEBUG juju.utils.ssh ssh.go:292 using OpenSSH ssh client22:25
wpkpacket_write_wait: Connection to 10.2.15.254 port 22: Broken pipe22:25
wpkany ideas on what might I be doing wrong?22:28
menn0wpk: can you give a bit more context? is this with real hardware or vmaas?22:41
babbageclunkwallyworld: the bug is because the juju-qa env is a legacy network, so network interfaces are returned with no subnet. It looks like I can get everything I need off the network in that case - doing that.22:41
sinzuibabbageclunk: interesting. We/me also has an ancient aws account22:44
wpkmenn0: real hardware, PC + 2 NUCs with AMT as nodes. I'm doing juju bootstrap maastiff, and as I understand it SSHs to the node, installs all the stuff, reboots it, and then SSHs to it again just to fail on the above, then decomissions it22:45
babbageclunksinzui: yeah, that's part of the problem - new accounts wouldn't have this kind of network as the default22:45
babbageclunkwpk: can you deploy a node in maas without juju?22:46
menn0wpk: seems something is up with SSH on the host causing it to drop the SSH connection attempt. is it possible to get the sshd logs on that host?22:46
wpkbabbageclunk: yes, no problem with that22:47
wpkmenn0: it gets decomissioned before I have a chance to get to it :/22:47
menn0wpk: try adding --keep-broken to the juju bootstrap command22:48
menn0wpk: that should keep the system around22:48
wpkmenn0: ok22:48
wpkhttps://pastebin.canonical.com/183603/ that's the whole log22:48
sinzuiwpk: your localhost cannot ssh to that address. As menn0 says try --keep-broken to keep it up22:52
sinzuiwpk: while juju is bootstrapping, you *should* be able to ssh in as ubuntu@<ip>22:53
wpkI am22:54
sinzuiwpk: you are sshed in?22:54
sinzuiif so, use -v to see what key works.22:54
sinzuiyou can force the juju key using -i $JUJU_DATA/ssh/juju_id_rsa22:55
wallyworldwpk: there's a bug or 2 where this issue is discussed; usually the cause is a set up issue, see last comment or 2 on https://bugs.launchpad.net/juju-core/+bug/131468223:26
mupBug #1314682: Bootstrap fails, missing /var/lib/juju/nonce.txt (containing 'user-admin:bootstrap') <bootstrap> <juju> <maas-provider> <juju:Expired> <juju-core:Won't Fix> <https://launchpad.net/bugs/1314682>23:26
wallyworldwpk: also https://ask.openstack.org/en/question/59760/juju-bootstrap-failed/23:27
wpksinzui: I was able to ssh in, using /home/wpk/.local/share/juju/ssh/juju_id_rsa key, and /var/lib/juju/nonce.txt exists on this node23:29
wpksinzui: the nide has Internet access and dns resolution working23:31
wpkwallyworld: nothing worrying in cloud-init.log23:43
wpkhm, except for this:23:44
wpk2017-03-23 23:28:12,171 - util.py[DEBUG]: Running module apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python3/dist-packages/cloudinit/config/23:44
wpkcc_apt_configure.py'>) failed23:44
wpk(...)23:44
wpkValueError: Old and New apt format defined with unequal values True vs False @ apt_preserve_sources_list23:44
wallyworldthat would do it23:45
wpkwallyworld: and what's the cause and how to fix it?23:48
wallyworldwpk: i have no idea off hand - it's an issue outside of juju and maas from whay i can see. you'd need to google the error and fix your apt config23:49
wallyworldbut if cloud init doesn't complete, you'll see the nonce error23:50
wallyworldso you need to fix whatever is stopping cloud init from running properly23:50
wpkwallyworld: but why there's the nonce error if the file is there?23:53
wpkhttps://bugs.launchpad.net/cloud-init/+bug/164657123:53
mupBug #1646571: apt failures non fatal, but cloud the log <landscape> <cloud-init:Incomplete> <MAAS:Confirmed> <https://launchpad.net/bugs/1646571>23:53
wpk(and as it says - it's not fatal, cloud-init continues after that)23:54
wallyworldwithout digging into the code and analysing logs etc, there's no way to tell. we'll need to devote time to looking into it23:55
wallyworldthe bug you link above indicates a maas issue23:55
wallyworldcan you add extra info from your sitution to the bug?23:56
wpkwallyworld: I will, tomorrow (1AM here)23:57
wallyworldthanks23:57

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