16:03:55 #startmeeting openstack_ansible_meeting 16:03:55 Meeting started Tue Apr 23 16:03:55 2019 UTC and is due to finish in 60 minutes. The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:56 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:03:57 #topic office hours 16:03:59 The meeting name has been set to 'openstack_ansible_meeting' 16:04:16 o/ 16:04:45 o/ 16:04:54 o/ 16:05:29 right so 16:05:43 usual announcement :) https://etherpad.openstack.org/p/osa-train-ptg 16:05:43 \o/ 16:05:57 0/ 16:05:57 o/ 16:06:44 also, I think stein is finally looking ok 16:06:50 besides all the infra troubles 16:06:52 I think our code seems ok 16:07:12 I always try to keep an eye on https://review.opendev.org/#/q/topic:openstack/openstack-ansible-tests/sync-tests+is:open 16:07:43 so we're just gonna wait out the infra issues, but as of now, we're doing pretty well 16:07:43 unfortunatelly, jobs are failing on zuul 16:07:47 stein is *actually* stein now 16:07:48 :) 16:08:00 I'm wondering if its safe to recheck now 16:08:02 that's great news! 16:08:21 mnaser: one job just failed several minutes ago 16:08:42 I think we will need to re-kick some jobs into the gate 16:08:51 I've sent https://review.opendev.org/#/c/654922/ to recheck and was keeping eye on it 16:09:13 noonedeadpunk: damn, the one that fails several minutes ago, is it recent? 16:10:22 yep, it's from the latest openstack-ansible-tests/sync-tests 16:11:32 ok, are we going to proceed with migration to opendev? Who have ideas regarding this? 16:12:50 And are we going to backport these changes to older branches, like queens? 16:13:08 o/ 16:14:00 I propose not backporting to ocats 16:14:02 ocata 16:15:08 is it still supported? 16:16:07 oh, it's under extended maintenance. So yes, the latest should be pike i think 16:18:24 noonedeadpunk: I think for opendev changes, I want to hold off until we actually release stein 16:18:26 So, I've created some sample for keystone https://review.opendev.org/#/c/653985/ and openstack-ansible itself https://review.opendev.org/#/c/653970/4 but really have doubts how backportable they are 16:18:37 that is a huge undertaking, and there might be a lot of ways we can break stuff :P 16:18:48 right, that was the idea, also, it pretty much breaks all backports 16:18:53 or a lot of potential backports 16:20:45 ok. And all new changes shouldn't contain links to our github - only opendev? 16:22:28 the authoritative place for all of our code is opendev.org 16:22:40 kinda like imagine git.kernel.org -- there are mirrors, but that is the *absolute* source of truth 16:23:37 yeah, it was just to confirm that I'm on the same page 16:24:01 absolutely yep 16:25:17 so I think if we can land everything in https://review.opendev.org/#/q/topic:openstack/openstack-ansible-tests/sync-tests+is:open 16:25:19 we may be ready for an rc2 17:03:16 #endmeeting 17:03:58 Antony Messerli proposed openstack/openstack-ansible master: Skip boostrap-ansible on upgrades if already run https://review.opendev.org/655199 17:04:55 Hi, there is a way to launch openstack-ansible setup-hosts.yml as non-root user on deployer and on target hosts ? 17:05:44 miloa: I'm not sure about that, as we haven't placed become everywhere, where it's required. 17:06:59 But probably you may try to add become flag to the openstack-ansible command 17:07:23 ok because I tried with --become and I've got this error during the lxc container creation "Gather container facts" I've got this error : "You lack access to /home/centos/.local/share/lxc\n" 17:09:19 mnaser: seems that you need to place #endmeeting :) 17:09:24 ah yes 17:09:27 #endmeeting