16:01:21 #startmeeting openstack_ansible_meeting 16:01:21 Meeting started Tue Sep 5 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:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:26 The meeting name has been set to 'openstack_ansible_meeting' 16:01:28 o/ 16:01:45 #topic this week's bugs 16:01:53 o/ 16:01:55 #link https://bugs.launchpad.net/openstack-ansible/+bug/1714597 16:01:56 Launchpad bug 1714597 in openstack-ansible "multi OS repo-build needs to be more intuitive " [Undecided,New] 16:02:24 odyssey4me: yes some tasks are played from that task file 16:03:16 never heard about this problem but I agree we don't have cross repo testing 16:03:27 hmm 16:03:38 cross distro* 16:04:03 we dont really have a way to test that though 16:04:11 manual testing only indeed 16:04:23 let's maybe leave that as is? 16:04:26 until someone confirms? 16:04:27 evrardjp_: I'm currently struggling uprading from ubuntu 14 to 16 and there are some possible improvements 16:04:49 it may make sense for that role to change up the tests to implement 3 qemu vm's via libvirt instead of using a container for the build 16:05:08 evrardjp_: mostly wheel package are not synced correctly 16:05:16 but that's obviously an improvement that someone would need to implement, which is not really the bug subject 16:05:31 neith this is the bug triage meeting - please wait until afterwards 16:05:50 (or register bugs!) 16:05:54 :D 16:05:59 don't! :p 16:06:04 (joking) 16:06:22 that problem should at least have been caught by a few users before 16:06:49 Morning 16:06:51 I think we should leave it as is, and if someone has the issue again we'll see 16:07:00 ok for everyone? 16:07:31 let's move on 16:07:32 #link https://bugs.launchpad.net/openstack-ansible/+bug/1714462 16:07:33 Launchpad bug 1714462 in openstack-ansible "Ansible security leads to FAIL_DELAY configuration error on ocata" [Undecided,New] 16:07:46 mhayden: ? 16:07:50 have you seen that? 16:08:06 * mhayden ganders 16:08:17 assign it to me and i'll dig into it 16:08:35 thanks 16:08:47 next 16:08:48 #link https://bugs.launchpad.net/openstack-ansible/+bug/1711376 16:08:49 Launchpad bug 1711376 in openstack-ansible "intermittent AIO error: Timeout (7s) waiting for privilege escalation prompt" [Undecided,New] 16:09:33 yeah i haven't seen that^^ ever since I increased the memory requirements on the Vagrantfile 16:09:36 hwoarang: is that done? 16:09:56 let's mark it as fixed for now, and maybe reopen then? 16:10:03 i guess we can close that since we don't see it on the gates 16:10:05 yeah ok 16:10:19 next 16:10:20 #link https://bugs.launchpad.net/openstack-ansible/+bug/1710874 16:10:23 Launchpad bug 1710874 in tripleo "tacker requires conductor service in pike" [High,Triaged] - Assigned to Tim Rozet (trozet) 16:14:04 do we even have ppl working on mistral? 16:14:23 who was working on tacker recently? 16:14:52 it was mbuil mostly i think - but he's out atm 16:15:28 well let's say confirmed, based on what we can see in other deploy projects 16:15:32 andymccr: I have a problem with ironic-api 16:15:39 sauloaislan: maybe later? 16:16:02 andymccr: how would you triage this? 16:16:09 low? 16:16:16 evrardjp_: yeah we dont officially spuport tacker in pike anyway 16:16:37 ok let's move on 16:16:37 sauloaislan: we're doing bug triage right now - happy to try help after 16:16:39 #link https://bugs.launchpad.net/openstack-ansible/+bug/1708360 16:16:41 Launchpad bug 1708360 in openstack-ansible "Openstack-Ansible Install Fails with OVS" [Undecided,New] 16:17:03 i mean - probably :P 16:17:07 same thing as last week? 16:17:12 My problem can be a bug, but ok 16:17:21 if somebody is keen on OVS we should get some testing etc going 16:17:32 hwoarang: ? 16:17:38 sauloaislan: if you put it up on launchpad then its probably on the list to go through today :) 16:18:08 list is already define, but I leave time at the end of each bug triage to talk about other bust 16:18:11 bugs* 16:18:32 ok let's move on 16:18:34 #link https://bugs.launchpad.net/openstack-ansible/+bug/1707151 16:18:35 Launchpad bug 1707151 in oslo.middleware "Remove method CORS.set_latent" [Undecided,New] 16:19:11 the glare paste file was removed, i don't know if there's anything else for OSA to do there 16:19:45 yeah I'd say I don't see anything in hound 16:19:52 I'll remove it 16:20:07 hmm 16:20:18 next 16:20:19 #link https://bugs.launchpad.net/openstack-ansible/+bug/1707142 16:20:20 Launchpad bug 1707142 in openstack-ansible "pip_install: "The following packages cannot be authenticated"" [Undecided,New] 16:20:43 gonna expire soon! 16:20:48 next 16:21:14 #link https://bugs.launchpad.net/openstack-ansible/+bug/1705374 16:21:15 Launchpad bug 1705374 in openstack-ansible "realpath() of /etc/uwsgi/nova-placement-uwsgi.ini failed" [Undecided,New] - Assigned to Andy McCrae (andrew-mccrae) 16:22:07 andymccr: I assigned that to you because you said you're gonna check on it because you had to revisit the code 16:22:18 now that it's revisited, should we close that? 16:22:33 evrardjp_: lemme double check ill close if its been backported i think it was 16:22:51 Major Hayden proposed openstack/openstack-ansible-rabbitmq_server stable/pike: Increase RabbitMQ's ulimit to 65536 https://review.openstack.org/500913 16:22:56 Major Hayden proposed openstack/openstack-ansible-rabbitmq_server stable/ocata: Increase RabbitMQ's ulimit to 65536 https://review.openstack.org/500914 16:23:00 yeh done 16:23:01 Major Hayden proposed openstack/openstack-ansible-rabbitmq_server stable/newton: Increase RabbitMQ's ulimit to 65536 https://review.openstack.org/500915 16:23:03 next! 16:23:25 #link https://bugs.launchpad.net/openstack-ansible/+bug/1703618 16:23:26 Launchpad bug 1703618 in openstack-ansible "repo_container on arm host contains packages for x86 hosts only" [Undecided,New] 16:24:36 should we decide to backport this to older branches? 16:24:45 we are not sure it would solve the issue 16:24:59 if nobody answers, it's gonna expire 16:25:11 we could mark it as incomplete too 16:25:20 incomplete ok for everyone? 16:25:54 3 16:25:55 2 16:25:56 1 16:26:16 #link https://bugs.launchpad.net/openstack-ansible/+bug/1703616 16:26:17 Launchpad bug 1703616 in openstack-ansible "Error " This is not a recognized Fernet token" when installing os-trove" [Undecided,New] 16:26:58 incomplete? 16:27:11 hmm 16:27:21 yeah 16:27:23 im not sure how to recreate 16:27:24 andymccr: it looks like we are expecting data 16:28:45 yeah 16:28:52 incomplete is good i think - if we cant recreate its hard to fix :) 16:28:59 sorry 16:29:04 next 16:29:06 #link https://bugs.launchpad.net/openstack-ansible/+bug/1698871 16:29:06 Launchpad bug 1698871 in openstack-ansible "[master] [os_gnocchi]Gnocchi role tests failing on installing pip packages" [Undecided,New] 16:29:25 anyone got the chance to look at that? 16:29:30 i mean its unsurprising 16:29:40 yes 16:29:43 the whole telemetry stack is pretty much in disrepair since nobody seems to use/maintain it 16:29:54 agreed 16:30:19 We have a talk at the PTG about phasing out roles 16:30:34 feedback gathering session at least 16:30:53 ok let's continue then 16:30:54 #link https://bugs.launchpad.net/openstack-ansible/+bug/1697782 16:30:56 Launchpad bug 1697782 in openstack-ansible "Mounting of ceph-backed cinder volumes is broken after Ocata upgrade" [Undecided,New] - Assigned to Jesse Pretorius (jesse-pretorius) 16:31:10 odyssey4me: I don't recall why I assigned that to you. I can check on the logs 16:31:31 I added a patch to check whether it was true, as far as I can see builds are still working with that patch merged. 16:31:42 Merged openstack/openstack-ansible-rabbitmq_server master: tests: test-vars: Install the RabbitMQ file directly https://review.openstack.org/500629 16:32:00 https://review.openstack.org/483541 16:32:07 logan- appears to be working on it though 16:32:31 i have not done any work on it since my last reply, have not had any luck reproducing it :( 16:32:58 should we care? 16:33:00 im about to dive into ocata upgrade stuff so i'm keeping an eye out for it cropping up in my deploys here 16:33:37 I've removed myself as assignee and added a comment about the testing implemented 16:34:43 thanks odyssey4me! 16:34:46 next 16:34:47 #link https://bugs.launchpad.net/openstack-ansible/+bug/1711347 16:34:48 Launchpad bug 1711347 in openstack-ansible "Config file override mechanism broken" [Wishlist,New] 16:35:08 andymccr: did we revert the python3 yet? 16:35:20 sorry I haven't followed that, I just see 1 commit. 16:35:29 evrardjp_: we did in pike yeah 16:35:46 we dont install it as part of the bootstrap and we dont select it so it should be fine 16:35:48 check experimental in plugins will expose a bunch of py3 plugins issues 16:36:59 logan- you had another patch to test the connection.strategy plugins which needs a revision too - it'd be nice to get that done 16:37:14 yup 16:37:28 was looking at that this weekend, trying to wrap up old patches I have open 16:37:42 but ill ping after the mtg about that :) 16:37:58 no I meant these kind of patches: https://review.openstack.org/#/c/471531/ 16:38:04 https://review.openstack.org/#/c/471529/ 16:38:21 if we are good then let's continue with our lives 16:38:21 yeah 16:38:35 there's a lot more of those needed in plugins before py3 works correctly there 16:38:39 What I mean there, is that there were other bugs to introduce python3 compatibility 16:38:51 sorry let me rephrase 16:39:20 if some of our code is python 2+3 ready, good. 16:39:44 if it's breaking under 3, meh IF we ensure python3 is not used. 16:39:54 but this isn't the case. So should we care now? 16:40:12 Because expectations to run python3 may be in the community already 16:40:37 so should way say somewhere: run python2? (in our shabangs ?) 16:41:28 in the meantime, I'd say let's leave the bug as is, and just remember it :) 16:41:45 bootstrap-ansible essentially enforces "run python 2" or "run python 3" because it manages the venv build 16:41:45 ok for everyone? 16:41:47 yeah 16:42:21 ++ 16:42:23 logan-: oh yeah that's true. So except if someone is running with it's own bootstrapped ansible we should be fine 16:42:43 ok 16:42:50 done for today 16:43:03 anyone else has a bug to raise? 16:43:47 5 16:43:49 4 16:43:51 3 16:43:52 2 16:43:54 1 16:43:55 thanks :) 16:44:00 ty ! 16:44:01 #endmeeting