16:00:20 <tiffanie> #startmeeting openstack_ansible_meeting 16:00:21 <openstack> Meeting started Tue Aug 13 16:00:20 2019 UTC and is due to finish in 60 minutes. The chair is tiffanie. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:22 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:24 <openstack> The meeting name has been set to 'openstack_ansible_meeting' 16:00:42 <tiffanie> #topic office hours 16:01:19 <mnaser> hi 16:01:20 <mnaser> everyone 16:01:21 <mnaser> :> 16:08:03 <openstackgerrit> Merged openstack/openstack-ansible stable/stein: Update docs & upgrade scripts for Stein https://review.opendev.org/672719 16:09:14 <jamesdenton> hi 16:09:29 <noonedeadpunk> o/ 16:09:33 * mnaser is getting tired of seeing warnings on CentOS 16:09:38 <mnaser> when sourcing openrc 16:09:48 <mnaser> noonedeadpunk: seems to have traced it back to https://github.com/openstack/openstack-ansible-openstack_openrc/commit/ef3fe9966fff2570ce2b40094921abe17fa3f2a1 16:10:06 <mnaser> i was thinking maybe we should set LC_ALL to some other value? or does centos not have a utf8 locale? 16:11:06 <noonedeadpunk> I'm not really sure that all systems will have some locale by default (except C, but not for centos) 16:11:32 <noonedeadpunk> So I saw ubuntu without en_us locale some time ago. 16:12:20 <noonedeadpunk> probably we should install one (or verify that it's there) 16:12:34 <noonedeadpunk> or kinda detect avaiable ones 16:13:04 <mnaser> it looks like ubuntu is ok with that locale 16:13:07 <mnaser> hmm let me find a centos machine 16:14:10 <noonedeadpunk> Yeah, I guess ubuntu has it by default 16:15:59 <mnaser> https://termbin.com/692k 16:16:02 <mnaser> this is all the centos locales 16:16:29 <mnaser> isnt there a way for us jsut to say "use utf8" 16:16:32 <mnaser> and not the specific lang 16:17:02 <noonedeadpunk> I guess no... That's why C was created I guess 16:17:23 <noonedeadpunk> (but I's just a guess) 16:19:07 <mnaser> i wonder what would happen if we dropped that line entirely 16:20:28 <noonedeadpunk> Probably I'd suggested adding some en_us.UTF8 generation for centos and defining it instead of C 16:20:46 <noonedeadpunk> at least for centos 7. And hope appearing C in centos 8 16:24:22 <noonedeadpunk> and add posibility to override it:) 16:24:44 <mnaser> yeah to not mess up users who have specific locales i guess 16:24:56 <mnaser> is C.UTF8 the same as en_us.UTF8 16:25:00 <mnaser> or mostly same 16:25:51 <noonedeadpunk> I'm not a big expert but out of what I've found for such pressed time it looks pretty common 16:26:23 <mnaser> yeah i dont think having C.UTF8 will keep your local 16:26:26 <noonedeadpunk> despite en_us may be missing things 16:26:36 <mnaser> so it will revert you to english anyways 16:26:47 <mnaser> so if we default to en_us its not like people will get confused 16:28:55 <noonedeadpunk> mnaser: So we need to ensure that this locale is present for sure 16:29:07 <guilhermesp> upps late 16:29:08 <guilhermesp> o/ 16:29:11 <noonedeadpunk> so the question is should be do this for both ubuntu and centos or centos only... 16:29:16 <mnaser> noonedeadpunk: oh i wonder if there is an ansible fact that can say what is the current locale? 16:30:07 <noonedeadpunk> ansible_env.LANG 16:30:25 <noonedeadpunk> https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variables-discovered-from-systems-facts 16:30:27 <mnaser> so maybe we can use that? 16:31:54 <noonedeadpunk> yeah, let me try to make a patch 16:37:10 <mnaser> other than that, the uwsgi repo thing seems to have been approved 16:37:13 <mnaser> so we can start on that clean up 16:38:07 <noonedeadpunk> wow, that was fast 16:38:34 <mnaser> noonedeadpunk: ptl +1 counted as +2 :P 16:38:47 <noonedeadpunk> I'd say yes:)) 16:38:55 <jrosser> hello 16:38:58 <mnaser> https://opendev.org/openstack/ansible-role-uwsgi 16:39:01 <mnaser> its up and ready 16:39:03 <mnaser> so we can start iterating 16:39:05 <mnaser> hi jrosser 16:39:16 <noonedeadpunk> The bad thing is that https://review.opendev.org/#/c/676193/ failed... 16:40:09 <mnaser> noonedeadpunk: thats normal because of how openstack/project-config works 16:40:11 <noonedeadpunk> ok, seems that depends on doesn't work 16:40:27 <mnaser> noonedeadpunk: its a 'trusted' repo so you cannot do depends-on it 16:41:04 <noonedeadpunk> Ok, great. I've already started work on uwsgi 16:41:45 <mnaser> "A list of projects to be treated as config projects in this tenant. The jobs in a config project are trusted, which means they run with extra privileges, do not have their configuration dynamically loaded for proposed changes, and Zuul config files are only searched for in the master branch." 16:41:48 <noonedeadpunk> so repo shouldn't be empty for a long time 16:41:52 <mnaser> they're called config projects now i guess :) 16:41:55 <mnaser> noonedeadpunk: awesome 16:46:19 <jrosser> the nova-lxd jobs on stein are failing 16:47:09 <jrosser> and i didnt really understand why, but problem is it seems to try to use the master version of the repo when it builds the nova venv 16:47:22 <openstackgerrit> Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-openstack_openrc master: Add option to redefine locale https://review.opendev.org/676244 16:47:41 <noonedeadpunk> jrosser: so nova-lxd has moved to x/nova-lxd - can't this be the problem? 16:48:15 <jrosser> ah yes thats the otehr thing it it using the wrong url 16:48:21 <jrosser> but i could not see how or where that came from 16:49:43 <noonedeadpunk> I guess that they've just move repo to the new url as a part of obsolate process 16:50:44 <noonedeadpunk> mnaser: what do you think about approach in https://review.opendev.org/676244 ? 16:51:55 <mnaser> noonedeadpunk: that seemes reasonable actaully 16:52:06 <mnaser> jrosser: i think i remember looking into that 16:54:31 <mnaser> jrosser: i think the step #1 issue is this 16:54:32 <mnaser> https://review.opendev.org/#/c/675155/ 16:54:35 <mnaser> its using the old functional jobs 16:55:36 <jrosser> oh right yes 16:55:44 <mnaser> mainly https://review.opendev.org/#/c/658521/ 16:55:53 <mnaser> logan-: is that safe/good to backport? 17:00:28 <tiffanie> #endmeeting