16:01:21 #startmeeting openstack_ansible_meeting 16:01:23 Meeting started Tue Mar 7 16:01:21 2017 UTC and is due to finish in 60 minutes. The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:24 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:26 Heyo 16:01:26 The meeting name has been set to 'openstack_ansible_meeting' 16:01:50 \o/ 16:02:11 Does someone want to prioritize work? 16:02:35 if not, we'll take the order planned 16:02:51 evrardjp: order planned is fine with me (just seeing your ping earlier) 16:03:13 order seems fine! 16:03:17 ok I'll wait for a few seconds more to let the chance to ppl to join 16:03:55 well I'm not patient enough I guess. 16:03:57 let's go 16:03:59 https://bugs.launchpad.net/openstack-ansible/+bug/1670632 16:03:59 Launchpad bug 1670632 in openstack-ansible "ceilometer error because gnocchiclient > 3.0 for stable/newton " [Undecided,New] 16:04:10 #link https://bugs.launchpad.net/openstack-ansible/+bug/1670632 16:04:21 alextricity25: stevelle ? 16:04:49 Jesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-lxc_hosts stable/newton: Allow the Trusty backport repo addition to be disabled https://review.openstack.org/442592 16:04:55 dont know much about that one yet evrardjp 16:04:55 it looks like an upstream bug that needs a bump, maybe we can't do that in that branch? 16:05:10 gnocchi is using a different branching, right? 16:05:33 close but not necessarily in sync w/ OS 16:05:47 this is likely due to the fact that telemetry doesn't abide by the g-r process 16:06:09 odyssey4me: I would agree 16:06:31 do we have news from the bug reporter if everything is working on latest newton? 16:06:43 that later gnocchi client must be coming from somewhere though 16:06:49 yes 16:07:21 i believe fabg filed the bug today 16:07:30 ok, let me try and build an environment to see if I can confirm it 16:07:51 I've self-assigned it 16:07:56 ok cool 16:07:56 ok 16:07:59 thanks odyssey4me! next 16:08:00 let's continue 16:08:12 #link https://bugs.launchpad.net/openstack-ansible/+bug/1670580 16:08:13 Launchpad bug 1670580 in openstack-ansible "No bridges on Xenial AIO reboot" [Undecided,New] 16:08:50 this one has been coming up a lot lately 16:08:51 I'd say incomplete 16:09:06 there was much discussion earlier for the same issue on multinode deployments 16:09:06 We have no /etc/network/interfaces(.d) 16:09:19 I had that issue yesterday 16:09:27 but it was because of my interfaces file 16:09:48 odyssey4me / mgariepy: https://review.openstack.org/442484 <-- keystone gate unblocker 16:09:50 seems to be a bug with our suggested network interface files then? 16:09:55 its not an OSA issue, its a "i dont use ubuntu usually" problem 16:09:58 xdfil_: could you put your diagnostic on the bug? 16:10:31 i think the bug relates specifically to the AIO though - so that's hardcoded in - and potentially relates to our docs too 16:10:49 oh it's an AIO 16:10:51 xdfil_: Well, the reporter uses it more or less daily, so I'm not sure that it's just an unfamiliarity problem 16:11:02 andymccr: yes 16:11:12 oh, they might be having a seperate issue 16:11:21 thats what it was in my case 16:11:28 id say thats kinda high - if people are configuring networking based on our docs/use cases and its wrong then we should fix that 16:11:48 xdfil_: if you could have a look at our docs to see if there is something wrong there, that would be nice 16:11:54 ^ yeah that 16:11:58 k 16:12:04 if its just the AIO its less critical - still a bug potentially 16:12:12 xgerman: finally got time to gander at your patches -- 422062 and 428979, right? 16:12:20 xdfil_: sections for configuring host networking and AIO :D 16:12:52 andymccr: let's classify this as confirmed and medium. It doesn't impact gates, let's fix it when convenient 16:13:08 evrardjp: yeah that seems fine for triage 16:13:12 mhayden correct 16:13:16 andymccr: Do we want it hard coded in and then docs explaining what to do after to fix? 16:13:19 xgerman: lookin' 16:13:31 thx 16:13:54 spotz: at the moment i think we just want to figure out what the issue is - perhaps our docs are fine and that would be less "high" priority then 16:14:00 mhayden: xgerman could you talk about that later, it's harder to triage when there is noise :p 16:14:02 spotz evrardjp andymccr not sure it's confirmed at this point, personally 16:14:09 odyssey4me: im testing now 16:14:10 has anyone else rebooted an AIO to confirm? 16:14:12 evrardjp: sorry! 16:14:14 alright 16:14:15 i think it is - i just rebooted an AIO and its taking a while :P 16:14:27 but i'll mark as confirmed if/when i get access to the AIO again 16:14:32 or incomplete as appropriate 16:14:35 whatever the issue we need to fix it - it may be a canary for multi-node deployments 16:14:37 I think I may have got that in the past 16:14:48 let's continue and we can get back to it 16:14:56 #link https://bugs.launchpad.net/openstack-ansible/+bug/1670556 16:14:56 Launchpad bug 1670556 in openstack-ansible "Glance needs ceph client when rdb in use" [Undecided,New] 16:14:59 odyssey4me: andymccr evrardjp - well write notes if its docs and assign to me, I'll ask my usual silly questions if needed:) 16:15:01 mhayden: np :p 16:15:12 spotz: thanks! 16:15:16 spotz: excellent, appreciate that 16:15:27 yeah that's great to hear :) 16:16:08 ah that bug is referring to https://review.openstack.org/#/c/438671/9/playbooks/os-glance-install.yml 16:16:18 ok, I'll patch that up real quick 16:16:38 marking medium, confirmed if that's ok with everyone 16:16:41 looking at the example network configs in 15rc1 they are all correct in the sense of inet manual vs inet static 16:17:02 ok odyssey4me 16:17:23 odyssey4me: if you are working on it I can even bump it to in progress. 16:17:35 evrardjp once the patch is submitted it'll get done 16:17:46 yup yup! 16:17:48 ok next 16:17:54 #link https://bugs.launchpad.net/openstack-ansible/+bug/1670357 16:17:54 Launchpad bug 1670357 in openstack-ansible ""Worker" not defined in ceilometer config template for ocata" [Undecided,New] 16:18:09 i think thats fixed already 16:18:17 yep, patch went in to fix that yesterday 16:18:35 i'll find and mark released 16:18:37 lets go to next! 16:19:08 ok 16:19:16 https://review.openstack.org/442047 16:19:20 #link https://bugs.launchpad.net/openstack-ansible/+bug/1670021 16:19:20 Launchpad bug 1670021 in openstack-ansible "user_external_repo_*_list undefined errors" [Undecided,New] 16:19:59 ive also seen those errors so confirmed 16:20:25 yeah, me too 16:20:37 Yes, it's my laziness. 16:20:47 it happens when bootstrap-host runs the pip_install role 16:20:48 oh wait. 16:21:01 so we can't have that var undefined, it needs to be defined, but empty 16:21:10 well I can define default to empty and it's gonna be fine 16:21:13 I'll do it 16:21:16 yeah seems fine 16:21:18 ok cool 16:21:18 COnfirmed low? 16:21:19 okie dokey :) 16:21:28 yeah, that's fine 16:21:40 #link https://bugs.launchpad.net/openstack-ansible/+bug/1669897 16:21:40 Launchpad bug 1669897 in openstack-ansible "galera_server apt related vars difficult to override" [Undecided,New] 16:21:49 is it normal that interfaces added later are ignored by cloud init? they don't get an IP 16:22:00 Merged openstack/openstack-ansible-haproxy_server master: Add http-check options to haproxy service template https://review.openstack.org/441690 16:22:22 nea1: If I remember cloud-init right, it's only one initial startup 16:22:45 is the related fix good enough? 16:23:09 before you go AFK remind me I have a question about enabling iscsi multipath 16:23:15 it looks good enough 16:24:12 I'll move to fix commited and we'll see 16:24:34 if the reporter tells us it's not enough it's gonna swap the bug status to new I think. 16:25:16 so for the record andymccr just confirmed https://bugs.launchpad.net/openstack-ansible/+bug/1670580 16:25:17 Launchpad bug 1670580 in openstack-ansible "No bridges on Xenial AIO reboot" [Medium,Confirmed] 16:25:36 i also see the fix - so i'll take and fix 16:25:48 let's keep up the good work 16:25:50 next bug 16:25:52 #link https://bugs.launchpad.net/openstack-ansible/+bug/1669691 16:25:52 Launchpad bug 1669691 in openstack-ansible "repo-install.yml failed in tasks of repo_pre_build.yml " [Undecided,New] 16:26:57 change in requirements/mysql_python recently? 16:27:41 not sure if it's newton or not, the tag was added and removed :p 16:28:15 sorry I'm late. I'm here now o/ 16:28:32 Jesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-pip_install stable/newton: Revert "Remove EPEL and use RDO instead" https://review.openstack.org/442607 16:28:33 cool fresh blood! 16:28:37 :) 16:28:42 so its 14.1.0 16:28:57 Jesse Pretorius (odyssey4me) proposed openstack/openstack-ansible-pip_install stable/newton: Revert "Remove EPEL and use RDO instead" https://review.openstack.org/442607 16:28:59 so the uca change 16:29:03 hmm maybe] 16:29:37 what was the other reason why we bumped to a higher sub version? 16:29:49 i believe the UCA was the reason 16:29:58 because we setup UCA everywhere 16:30:42 yes I think so too 16:30:49 ok so 16:31:12 odyssey4me: could you have a look? 16:31:21 yeah I can take a look 16:31:32 not sure if this is repeatable 16:31:33 it's a repo build requirements thing, I know you love it ;) 16:31:36 will see 16:31:40 ok 16:31:50 let's leave it as is if nobody reproduced it 16:31:56 let's see how it goes next week 16:32:09 next 16:32:11 #link https://bugs.launchpad.net/openstack-ansible/+bug/1669436 16:32:11 Launchpad bug 1669436 in openstack-ansible "nova_libvirtd_listen_tcp won't actually work" [Undecided,New] 16:32:37 andymccr: what's the status of this? 16:32:45 ahh yeah so that setting will cause libvirtd to not start on xenial - other than that i havnt had a chance to look into it in more detail 16:32:47 is listen tcp the default? 16:32:50 nope 16:33:01 its not - so i didn't look too deep into it 16:33:02 I knew ppl using this :( 16:33:03 i just know the service fails 16:33:16 know* 16:33:25 evrardjp: on OSA? 16:33:27 did some have a look at this? 16:33:31 evrardjp andymccr it may be worth having a chat with jamespage or looking at what the charms guys do... we both use the same platform and systems 16:33:32 yup with osa 16:33:38 well with other systems too 16:33:42 odyssey4me: yeah good point 16:33:43 messing with libvirt within nova.conf has never produced the same results as messing with libvirtd directly in my experience 16:33:59 so this might be outside the scope of OSA 16:34:00 xdfil_: its mostly the service defaults not so much the nova conf 16:34:10 if the default config works then ... idk 16:34:27 we set like "-l" in the libvirt startup opts when using tcp and the service then doesnt start 16:34:34 ok 16:34:37 that's a systemd thing 16:34:39 but yeah odyssey4me has the best idea there i think 16:34:40 we should remove that 16:34:51 or I think we should I'm not really sure anymore 16:35:11 oh wait 16:35:18 I'm confused with another option 16:35:33 forget what I just said 16:35:45 well I'll take it 16:36:03 In the meantime, I'd say confirmed and medium 16:36:17 agreed 16:36:18 I guess we can trust the bug reporter 16:36:40 next 16:36:44 #link https://bugs.launchpad.net/openstack-ansible/+bug/1669125 16:36:45 Launchpad bug 1669125 in openstack-ansible "rabbitmq-server fails so start with ubuntu16.04" [Undecided,New] 16:37:01 I'm having a hard time understanding the use case for tcp 16:37:05 ok confirmed, and we'll wait for an upstream patch 16:37:13 xdfil_: pure speed 16:37:17 I've used it with SASL 16:37:27 in non openstack 16:37:55 evrardjp: did you still want a note added to the doc or no? 16:38:05 but for openstack to me it seems like TLS is required as SASL wont work for service initiated stuff 16:38:31 oh so the user is accepting the less secure scenerio... i get it now 16:38:43 spotz: for the rabbitmq? 16:38:46 I think it's fine 16:38:56 well the patch to the doc is definitely welcomed 16:39:09 to say: "hey there is a bug there if you have hostname in your bashrc" 16:39:16 but I don't know where to put it. 16:39:42 anyway, I've marked the bug as won't fix 16:40:08 ev yeah 16:40:15 and expressed it was a deployer/ansible issue, not really an openstack-ansible one 16:40:44 Could you target the bug in your docs commit spotz? 16:40:48 That would be great. 16:41:02 evrardjp: I'll look to see if there's a good place and add if there is. Yeah do we have a link in there? 16:41:26 A link for the bug in ansible or the bug link? 16:41:40 evrardjp: I'm assuming the ansible bug not our bug:) 16:41:55 Well I don't think I filed a bug, I think I submitted a PR directly 16:41:59 let me have a look 16:42:20 #link https://github.com/ansible/ansible/pull/22246 16:42:30 thanks 16:42:39 so not fixed until 2.3 16:43:06 adding it to the comments so I'll remember:) 16:43:13 Perfect. 16:43:19 Next osa bug then! 16:43:23 #link https://bugs.launchpad.net/openstack-ansible/+bug/1668949 16:43:23 Launchpad bug 1668949 in openstack-ansible "dnsmasq-dhcp log spam from lxbr0" [Undecided,New] 16:43:47 andymccr: want to change to using proper dns instead? 16:43:49 :D 16:44:12 evrardjp: haha yeah ok go make it happen ;P 16:44:22 that was from the ML and is confirmed - but its low i'd say 16:44:26 im not sure if there is a simple fix - there probably is 16:44:28 Major Hayden proposed openstack/openstack-ansible-lxc_hosts master: Set higher priority for COPR repo https://review.openstack.org/442613 16:44:35 I think unbound can act as a basic authoritative server for some things on top of being recursive 16:45:07 maybe logan- is already doing it the proper way :p 16:45:18 ok I'll mark it as confirmed low 16:45:34 next 16:45:38 #link https://bugs.launchpad.net/openstack-ansible/+bug/1667130 16:45:38 Launchpad bug 1667130 in openstack-ansible "During N->O upgrade, nova-api-os-compute service won't start" [Undecided,Fix released] 16:45:40 forget it 16:45:41 :p 16:46:00 next 16:46:05 #link https://bugs.launchpad.net/openstack-ansible/+bug/1666235 16:46:05 Launchpad bug 1666235 in openstack-ansible "Update Zaqar to use tempest for func tests" [Undecided,New] 16:46:05 heheh 16:46:36 for me this means our role is broken if it's not properly tested :/ 16:46:51 evrardjp: depends on your definition of "properly tested" 16:46:55 but yes it'd be ideal to use the tempest tests 16:47:00 it's not like wishlist "that would be great if our role do the right thing" 16:47:03 :p 16:47:27 Well I guess what's in my head doesn't translate properly ... 16:47:34 confirmed and... ? 16:47:44 medium? 16:48:18 it's to match the community goals of having better tests that I say that :D 16:48:22 evrardjp: yeah agreed 16:48:24 lets set it to that 16:48:34 ok 16:48:52 next 16:48:55 #link https://bugs.launchpad.net/openstack-ansible/+bug/1665667 16:48:55 Launchpad bug 1665667 in openstack-ansible "Slow failover Recover on primary node restart" [Undecided,New] 16:49:22 Jesse Pretorius (odyssey4me) proposed openstack/openstack-ansible master: Check for rbd as a default & optional glance back-end https://review.openstack.org/442615 16:50:03 Hm wonder if that's just HAproxy or something else 16:50:20 Merged openstack/openstack-ansible-pip_install stable/ocata: Use yum priorities for RDO https://review.openstack.org/442562 16:50:54 palendae: it depends on the load balancing behavior 16:51:06 Yeah, that too 16:51:13 I think for some of the upgrades we force shutting down connections 16:51:14 well that interval is 12000 16:51:29 So I'd say we may need some tweaking 16:51:35 it's technically possible to improve this 16:51:44 andymccr: Seconds? 16:51:47 not sure how we can improve that with our current haproxy role 16:51:54 palendae: ms 16:52:08 haproxy are always ms except explicitly metioned 16:52:11 Ah 16:52:12 mentioned* 16:52:20 I think the interval is 5s though 16:52:32 yeah 5s 16:52:38 Still, much shorter than 5m 16:52:39 oh thats not so bad then. 16:52:54 wait 16:53:01 you mean the check interval 16:53:09 well I don't think it's relevant to that 16:53:13 "If that primary node goes down we see hard failures in applications for 2-5 minutes and connection failures in the haproxy logs going for up to 20 minutes or so." 16:53:16 but let me verify if the check interval is in ms 16:54:18 yes it's ms 16:54:45 I think it's connection termination that we should enforce for faster reconnect 16:54:56 IIRC 16:54:56 On which side? 16:55:05 This might be relevant to RPC's minor upgrade efforts 16:55:08 haproxy config 16:55:11 Ah 16:55:15 Well then it wouldn't be :) 16:55:35 well it's good to know it, this way we can adapt 16:55:42 Yeah 16:55:58 f5 would have the same kind of issue, maybe they know it already and did it smartly "by default" 16:55:59 :D 16:56:02 anyway 16:56:35 I'm not suprised of this, can someone technically confirm? 16:57:05 I will have a look 16:57:20 posted a few comments on the galera one 16:57:33 I think the haproxy one we could have a look together :) 16:57:45 ok last one for today 16:57:49 #link https://bugs.launchpad.net/openstack-ansible/+bug/1665568 16:57:49 Launchpad bug 1665568 in openstack-ansible "Check for .shosts or shosts.equiv files is very slow" [Undecided,New] 16:57:54 mhayden: ? 16:58:33 could we use a locatedb or something like that for security role? 16:58:48 is this confirmed? 17:00:04 ok no answer, it's gonna be for next week! 17:00:11 yeah 17:00:19 thanks everyone! 17:00:21 that may as well be confirmed, although I don't know if there's anything we can do about it 17:00:22 https://github.com/openstack/openstack-ansible-security/blob/1ff2d1b4aa2f866fafac10dd42907bfe0c720664/tasks/rhel7stig/auth.yml#L514 17:00:42 maybe some paths could be excluded? 17:00:54 maybe use another way to locate, or be more restrictive 17:00:55 yes 17:01:07 I'd not use locate because it may not be up to date 17:01:16 but being more restrictive in the find should be better 17:01:16 I think we'll have to wait for mhayden answer I guess... 17:02:12 for the locate an update could be used at the beginning of the role, async, and then use it at the end 17:02:27 then locate will take an age :p 17:02:31 well I guess we can mark it as confirmed and wishlist 17:02:42 the reporter could also just skip the task 17:02:52 fine for everyone and we wrap it up? 17:03:08 need another review for https://review.openstack.org/442607 to unblock newton patches please 17:03:51 ok thanks everyone 17:03:55 #endmeeting