16:00:13 #startmeeting openstack_ansible_meeting 16:00:14 Meeting started Tue Sep 17 16:00:13 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:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:17 The meeting name has been set to 'openstack_ansible_meeting' 16:00:32 #topic office hours 16:00:33 o/ 16:00:51 o/ 16:01:12 o/ 16:04:09 \o/ 16:04:38 o/ 16:05:23 so, upgrade jobs passing https://review.opendev.org/#/c/671105/ !!! 16:06:07 nice! 16:06:29 and, milestone https://review.opendev.org/#/c/681002/ was updated today 16:06:56 But due to keystone bug we can't merge it now 16:07:10 nice noonedeadpunk 16:07:39 we are going to need to work on tempest to land the keystone bug 16:08:03 becasue it needs this https://review.opendev.org/678379 16:08:04 jrosser: so, they're waiting our CI to pass before merging the patch? 16:08:19 no, i think it just needs review on the keystone side tbh 16:08:23 we have other issues :) 16:08:36 like swift 16:08:37 awesome work on ugprades, noonedeadpunk 16:08:39 lol 16:08:42 this is _very_ good 16:09:38 probably it's worth to include upgrade to milestone as well? 16:10:05 o/ 16:10:05 i personally think its very valuable to have that locked in 16:10:23 what are thoughts from others? 16:11:59 the centos upgrade is a long job - i hope we don't hit timeouts 16:12:58 yeah... 16:13:04 but I know how to reduce time 16:13:40 we need https://review.opendev.org/#/c/682103/ 16:14:02 to be able to skip tempest tests after stein deployment 16:15:44 https://review.opendev.org/#/c/671105/33/scripts/gate-check-commit.sh 16:17:25 Hello ! I've just added a compute node on my cluster (Rocky/Ubuntu16.04). This node is Ubuntu 18.04, and I don't see how to make the repo build venvs and co for Ubuntu 18.04, it does not running all the playbooks 16:19:24 noonedeadpunk: so i guess the upgrade is surviving a py2 -> py3 transition of some sort? 16:19:45 i figured that the ansible-runtime venv won't be recreated as py3 though 16:20:27 I guess I haven't rebased on top of py3 yet 16:20:42 :( 16:24:13 actually you may be ok https://zuul.opendev.org/t/openstack/build/8922b05644d6462ca472b071ba824187/log/job-output.txt#12667 16:25:19 gillesMo: You should hold on for sometime, look like weekly meeting going on. 16:25:31 oh, indeed 16:25:51 but it's for ansible. Dunno about projects 16:26:07 But seems that uwsgi has python3 suffix as well 16:26:47 cool 16:27:35 since aio don't contain swift or ironic - I'm ok :p 16:27:48 ... 16:27:50 lol 16:29:06 speaking of swift 16:29:22 jrosser: btw, regarding swift - should we edit our template as for now and keep track on the reported bug? 16:29:34 +1 noonedeadpunk 16:29:35 To rollback if they'll decide to use raw 16:29:56 you could propose a patch a revert at the same time so we remember 16:30:01 *and a 16:30:51 there are generally a few broken things we need to address 16:30:55 i'm all for that jrosser 16:31:05 sure:) 16:31:09 swift like we just mentioned which we can deal with 16:31:22 it'd help unblock the ironic efforts as well 16:31:32 neutron/calico is a python3 problem too 16:31:45 keystone bug + related tempest update 16:32:00 and i would like to land bind-to-mgmt too which needs some more work 16:32:14 plus i think we are about to learn what breaks with centos7.7 16:32:40 :) 16:32:50 and haproxy on metal looks very close too 16:33:02 Yeah I put a hold on the galera issue but will come back to it 16:33:03 I guess it's ok 16:33:13 regarding haproxy) 16:34:33 and one all that is sorted out there is a bunch of stuff folk have contributed which has got a bit backed up 16:38:14 jrosser: btw, I guess we need to walk through distro variables and ensure that ubuntu at least uses py3 everywhere 16:42:21 or leave it afterwards 16:46:09 so for bind-to-mgmt i want to tidy this up https://review.opendev.org/#/c/670051/ 16:46:42 far far too many variables, that needs cutting back and a global one introducing a bit like the py2/3 switch variable 16:50:40 jrosser: you mean by like adding a global var in each role correspondent to the mgmt-adddr? 16:50:59 yes, it's a bunch of one line patches to os_* i think 16:51:10 i was going to leave all the infrastructure things as they are 16:52:17 Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/openstack-ansible-os_swift master: Update fallocate_reserve to work with py3 https://review.opendev.org/682697 16:53:01 guilhermesp: nova_service_bind_address: "{{ openstack_service_bind_address | default('0.0.0.0') }}" 16:53:05 something like that 16:53:08 jrosser: for swift I've updated your's dnm if you don't mind:) 16:53:18 sounds clearer jrosser 16:53:46 for galera, we have abandoned the patch to replace the bind addrs but i need to figure out why it is still breaking on the integrated repo 16:54:08 practically on a production env it works as it is proposed in the patch 16:54:43 noonedeadpunk: thats fine 16:55:19 mnaser: anything from you on all this stuff? :) 16:55:29 guilhermesp: https://review.opendev.org/#/c/677830/ seems to be passing CI. Going to check what';s wrong with CLI 16:56:03 yeah noonedeadpunk it was passing all the time 16:56:07 jrosser: about galera.. everything we've used to deploy is all that i've handed to guilhermesp .. so im not sure ~how~ 16:56:14 now I guess murano-api is up, but cli returns bad request 16:56:15 not the last one:) 16:56:43 yeah I kinda of reproduced the vars we needed to set in 2 metal deployments 16:57:01 but was a mutlinode deployment 16:57:09 things could bahave differenctly in aio 16:57:19 in terms of galera 16:58:25 yeah, im not sure how/why it would behave different, but it does. 17:00:11 #endmeeting