16:00:21 #startmeeting openstack_ansible_meeting 16:00:24 #topic rollcall 16:00:25 Meeting started Tue Nov 27 16:00:21 2018 UTC and is due to finish in 60 minutes. The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:28 The meeting name has been set to 'openstack_ansible_meeting' 16:00:32 o/ 16:00:39 o/ 16:00:43 o/ 16:01:33 o/ 16:01:46 o/ although I'm sharing with another meeting :/ 16:01:49 i'm sorry, i haven't been updating things properly 16:02:10 last week highlights imho has been: odyssey4me getting us closer to running integrated for all roles 16:02:35 so please eyes on https://review.openstack.org/#/c/551791/ 16:02:45 need one more core review for https://review.openstack.org/551791 - then I'll be porting those back so that we can do upgrade tests along with deploy tests 16:02:48 i thought i reviewd that 16:03:01 ok ill review this shortly after the meeting to get us the second +2 16:03:05 ta 16:03:13 other things is os_placement still in progress 16:03:24 we're having a lot of gate failures i think 16:03:59 os_manila is also in progress 16:04:21 (while of lesser importance than placement, I agree) 16:04:21 i can look at the centos jobs to help make them stable but if we're going to have always-red nonvoting jobs, i would want to remove them 16:04:45 it takes 1.5h of wasted upstream CI time on every job and if no one is actively looking at them.. makes it hard 16:04:58 bear in mind we agreed that distro jobs on master stay non-voting, regardless of consistent failures 16:05:21 this allows people to work on fixing things as we go, rather than having to focus on fixing it at the end of the cycle 16:05:36 well the idea was to report back -- for example suse current breakages in horizon is on my todo list, even if I didn't get the chance to tackle it 16:05:37 odyssey4me: i agree, but it seems like there aren't a lot of eyes on them presently 16:06:10 we need more ppl to help there, anyone, feel free to help ! :) 16:06:24 sure, but it'll be easier to troubleshoot and solve them once we're using integrated build for all tests - because everyone is more familiar with it 16:06:37 odyssey4me: yep, i agree 16:06:47 so just something to keep in mind 16:07:02 Jonathan Rosser proposed openstack/openstack-ansible-os_tempest master: Add support for aarch64 images https://review.openstack.org/620032 16:07:06 we've identified a few responsible people per distro so just keep up with those and feel free to ping them when/if we need things 16:07:40 over the next few days i'm upgrading a few environments so https://review.openstack.org/#/q/topic:queens-to-rocky 16:07:57 mnaser: great news! 16:07:57 that's most of what i've identified, anyone else (surely i missed things!) 16:08:16 shouldn't that be a topic of the open discussion though? It's less a report, more a heads-up :p 16:08:59 Review please https://review.openstack.org/#/c/618046/ 16:09:31 sure 16:09:42 mostly just a "what i've been working on" thing, anyways 16:10:22 #topic bug triage 16:10:25 #link https://bugs.launchpad.net/openstack-ansible/+bug/1805239 16:10:26 Launchpad bug 1805239 in openstack-ansible "missing logrotate of the syslog, daemon.log " [Undecided,New] 16:11:28 hm 16:11:36 we dont use rsyslog_client anymore right 16:11:49 we do, for suse 16:12:23 maybe asking which branch does this apply? 16:12:33 and if that is for hosts or containers? 16:12:50 vakuznet: are you the owner of this bug? ^ 16:12:54 this says centos 16:12:55 yes 16:13:05 Queens, host 16:13:19 vakuznet: we supposed master :) 16:13:23 presumed* 16:13:33 so yeah that could apply. 16:13:33 so in rocky we no longer use rsyslog stuff and moved to journals for everything afaik 16:13:40 it is a queens bug 16:13:51 indeed. 16:14:05 vakuznet: are you able to push a patch regarding this? i can help with how to get it properly landed if you have questions 16:14:36 sure 16:14:47 I'm not feeling very well, so I'm going offline. I'll catch y'all tomorrow. 16:14:52 take care odyssey4me 16:15:08 vakuznet: cool, ill mark as confirmed/medium and assign to you is that ok? 16:15:40 https://github.com/openstack/openstack-ansible/blob/master/playbooks/common-tasks/rsyslog-client.yml#L18 16:15:45 see you later odyssey4me 16:16:04 vakuznet: we can talk about the potential fix after our meeting right now, is that okay? we're just triaging things right now 16:16:08 just to see bugs or not bugs :) 16:16:19 ok 16:16:25 and important or not :) 16:16:30 or less* 16:17:06 #link https://bugs.launchpad.net/openstack-ansible/+bug/1804837 16:17:07 Launchpad bug 1804837 in openstack-ansible "Failed to checkout version 0.5.1 of ansible-sshd for stable/pike" [Undecided,New] 16:17:10 wasnt this fixed? 16:17:17 * mnaser checks 16:18:03 evrardjp: do you know if the shabump includes it? 16:18:55 oh no shabump required 16:19:00 ok so this will be included in 16.0.23 16:20:04 #link https://bugs.launchpad.net/openstack-ansible/+bug/1804827 16:20:05 Launchpad bug 1804827 in openstack-ansible "Keystone ldap only configures domain on one node" [Undecided,New] 16:20:28 aw darn 16:20:35 sorry I was to something else 16:21:12 yep thats valid 16:21:19 regression by https://github.com/openstack/openstack-ansible-os_keystone/commit/096ed19665dad45fe9b1c1790ba599d90ccf233c 16:22:38 I am still reading... 16:22:57 confirmed/high assigned to jesse .. problem is that we made a change to run ldap setup on one container only to avoid race conditions 16:23:12 but that also meant the steps to config the local config files were only happening on one container 16:23:28 so that patch caused it, it should simply do then when: on the os_keystone_domain task only, not the entire script 16:23:37 yeah 16:23:51 I saw your message 16:23:56 great content in the bug 16:23:58 I agree 16:24:05 #link https://bugs.launchpad.net/openstack-ansible/+bug/1804770 16:24:07 Launchpad bug 1804770 in openstack-ansible "Pike -> Queens Upgrade: Documentation for OVS setup and neutron agent rebalancing missing" [Undecided,New] 16:24:47 thats an amazing bug 16:24:55 great docs included 16:25:51 posted asking for input 16:25:55 oh wow, thats a bummer ... 16:25:59 if they want/can contribute it 16:26:00 yeah 16:26:04 jamesdenton had something on that the other day ? 16:26:18 yes - i can take it and work on docs updates 16:26:20 cloudnull: i think he might have been helping the bug repoter here 16:26:25 ah . 16:26:32 jamesdenton: oh awesome, a lot of info was put there too, so ill assign to you, is that okay? 16:26:41 i think its something we can generally add to the upgrade scripts / playbooks 16:27:29 sure thing. 16:27:35 thank you 16:27:56 oh thats an easy one 16:27:59 #link https://bugs.launchpad.net/openstack-ansible/+bug/1804695 16:28:01 Launchpad bug 1804695 in openstack-ansible "Credentials needed to "Verifying OpenStack operation in openstack-ansible" step" [Undecided,New] 16:28:10 Merged openstack/ansible-role-systemd_service master: Allow user/group to be overriden in unit section https://review.openstack.org/620116 16:28:23 added as low-hanging-fruit, great if anyone wants to push up a small fix :) 16:29:04 #link https://bugs.launchpad.net/openstack-ansible/+bug/1804283 16:29:04 Launchpad bug 1804283 in openstack-ansible "Rabbitmq Error: unable to connect to node 'rabbit@ostack-controller-01': nodedown" [Undecided,New] 16:29:36 so i run into this all the time 16:29:37 i have to do 16:29:43 rabbitmqctl -n rabbit@`hostname` blah 16:30:02 it's a bug, not sure how's the best way to resolve it, but maybe eliminated with nspawn 16:30:32 confirmed/medium -- i'll add a comment about it.. maybe someone has insight if there's an easy fix? 16:30:32 mmm 16:30:36 that rings me a bell 16:31:05 mnaser: two questions for you 16:31:37 what's in /etc/hosts , and what do you have HOST or HOSTNAME in your bashrc/environment ? 16:31:50 oh third question, which branch? 16:32:26 evrardjp: those are probably good questions to add for the bug 16:32:28 :D 16:32:36 well we don't know if what you had is the same 16:32:44 but I can ask the questions. 16:32:49 let me comment on the bug 16:32:49 it is the same issue :) 16:33:16 ill move onto the next one while you comment on that 16:33:21 #link https://bugs.launchpad.net/openstack-ansible/+bug/1803444 16:33:22 Launchpad bug 1803444 in openstack-ansible "gnocchi playbook failing on 18.0.0" [Undecided,New] 16:34:28 I think that might be a duplicate of another one we talked in the past 16:34:48 evrardjp: the gnocchi one? 16:35:24 yeah, doesn't that ring you a bell? 16:35:34 yes, i didnt mark it as anything so it showed up next week :) 16:35:36 It seems we talked about that in the past. 16:35:49 hahah 16:35:51 that's why 16:35:58 so i think the solution is to add `import_playbook` .. but i dunno the implications of doing that 16:36:17 yeah we even discussed on what to do , but nobody got cycles, IIRC 16:36:49 okay well 16:36:55 confirmed medium and we can ask for that patch to be pushed up 16:37:30 #link https://bugs.launchpad.net/openstack-ansible/+bug/1802132 16:37:31 Launchpad bug 1802132 in openstack-ansible "OpenStack Ansible dashboard not able to log in with admin credentials" [Undecided,New] 16:37:37 mnaser: should we point to http://eavesdrop.openstack.org/meetings/openstack_ansible_meeting/2018/openstack_ansible_meeting.2018-11-20-16.00.log.html#l-73 ? 16:37:46 ok let me add that link into the bug 16:37:50 yes that would be useful 16:38:50 done 16:39:31 I haven't tried horizon for ages 16:40:17 i dunno 16:40:49 i've deployed countless times and havent seen aynthing 16:41:05 I recall horizon default endpoint policy to change to move to external by default, but I think we are explicit in endpoints usage. So it's probably not that, but I haven't touched horizon for a while, as I said earlier. 16:41:24 posted a comment requesting user_vars and etc 16:41:26 yeah it seem to deploy just fine for me, but I haven't tested it. 16:41:27 but it doesnt fel likea bug 16:41:30 yeah 16:41:43 I have the impression something wrong got inserted in the horizon config 16:41:52 making django scream 16:41:59 yup 16:42:04 #topic open discussion 16:42:05 next? 16:42:09 thats all :) 16:42:16 so upgrades? :) 16:42:25 going okay so far, i'll have a bunch of patches up 16:42:46 i will write an email to the mailing list about meeting engagement. i will maybe suggest we actually come up with another time, another method of communication or dropping it 16:42:47 I think there were a few ppl asking for feedback 16:42:54 we can say in the future you did just fine? 16:42:56 :) 16:43:04 once my patches land 16:43:04 :P 16:43:08 haha 16:43:11 well 16:43:18 tbh it's been always fluctuating 16:43:32 sometimes you find 9 ppl, sometimes I felt pretty much alone 16:43:54 I asked if the time was right, and at the end it was the best time. 16:44:11 But I agree we shouldn't be only two in meetings. 16:44:35 this is an opportunity for everyone to raise awareness of their work/issue, yet the media is not used... 16:44:41 yeah 16:44:43 * evrardjp shrugs 16:45:02 ill raise to ml 16:45:04 mnaser: it was worse when we had two meetings a week 16:45:30 i can imagine 16:45:34 I think having a meeting per week is the minimum, as one every two week will make our bug list and goal focus too thin 16:45:47 bug list too big* 16:45:51 i dunno 16:45:58 Merged openstack/openstack-ansible stable/queens: Add MariaDB infrastructure mirrors and disable nested virt https://review.openstack.org/619718 16:46:01 i feel like we do a good job communicating things together at the same time 16:46:07 its an ML discussion which ill send write away 16:46:27 yup, I think it's good to put it in the open at least. 16:46:52 perhaps we suffer today from not having the 1hr warning? 16:46:53 I'm alwys for LESS meetings :D 16:47:10 jrosser: i dunno, the 1 hour warning usualyl doesn't help much 16:47:21 i'm more about the engagement 16:47:25 oh yeah I am kinda not doing it anymore because I have other meetings 16:47:36 mnaser: it has been working for me in the past though : ) 16:47:51 (at least for the beginning of the meeting) 16:47:51 i try to do it closer to the meeting 16:47:57 so people kinda still remember it 16:48:02 haha 16:48:05 if you tell me about something that will happen in an hour surely ill forget :) 16:48:21 that's because you're all over the place, not everyone is like you :p 16:48:56 ha 16:48:56 :P 16:49:00 anyone has any other topics? 16:49:05 no other topic 16:50:16 cool, thanks everyone 16:50:17 #endmeeting