15:01:51 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:01:51 <opendevmeet> Meeting started Tue Aug 10 15:01:51 2021 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:51 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:51 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:01:56 <noonedeadpunk> #topic rollcall
15:02:04 <noonedeadpunk> \o/
15:02:24 <spatel> noonedeadpunk is back that is big update :)
15:02:38 <noonedeadpunk> well, unfortunatelly I'm not back for long :(
15:03:18 <noonedeadpunk> have tons of family business this week as well. I really hoped I would be online more this days, but this doesn't worked out :(
15:04:03 <noonedeadpunk> https://review.opendev.org/c/openstack/openstack-ansible/+/803097 looks really bad. I think it's because we haven't backported neutron patch...
15:04:16 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: Bump OpenStack-Ansible Wallaby  https://review.opendev.org/c/openstack/openstack-ansible/+/803097
15:04:46 <opendevreview> Dmitriy Rabotyagov proposed openstack/openstack-ansible stable/wallaby: Bump OpenStack-Ansible Wallaby  https://review.opendev.org/c/openstack/openstack-ansible/+/803097
15:05:54 <noonedeadpunk> #topic office hours
15:07:25 <noonedeadpunk> so, what's happening forum?
15:07:35 <noonedeadpunk> I'll be fully back only next week(
15:07:46 <jrosser> o/ hello
15:08:48 <jrosser> i think we need this and it's backport https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/798960
15:09:23 <noonedeadpunk> but for this I guess we need neutron patch spatel working on?
15:09:43 <jrosser> for master yes
15:09:53 <jrosser> whatever unblocks os_neutron needs to go first
15:10:20 <spatel> jrosser i have tried to stack my all neutron patches here, may need your input https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/804036/1
15:10:24 <noonedeadpunk> well, it's cherry-pick is not in a good shape either... https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/798881
15:10:42 <jrosser> no, there is so much to fix in os_neutron sadly
15:11:55 <noonedeadpunk> https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803987 looks like a light in the end
15:12:15 <opendevreview> Andrew Bonney proposed openstack/openstack-ansible-rabbitmq_server master: Fix erlang upgrades for rabbitmq external_repo installs  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/803711
15:12:29 <noonedeadpunk> So I'd say we can set jobs as NV in https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/804036/1 ?
15:12:36 <noonedeadpunk> and do bunch of rebases?
15:13:14 <spatel> noonedeadpunk yes that patch is part os multiple stack and i need to understand from you guys why other patches failed and solve their inter dependency when they are in chain
15:13:32 <jrosser> spatel: the first patch is tested on it's own
15:13:43 <jrosser> and is not enough to make the tests pas
15:13:51 <noonedeadpunk> yeah ^
15:13:53 <jrosser> the first and second then get tested together
15:14:02 <jrosser> then first / second / third, and so on
15:14:29 <jrosser> lets just do this now?
15:14:32 <noonedeadpunk> so let's set failing jobs as NV, merge all that and revert NV patch at the end of the day
15:14:48 <noonedeadpunk> But backporting that would be meh...
15:14:49 <jrosser> then work out what to do with W too
15:15:01 <jrosser> yeah, as there is centos and centos-stream there
15:15:09 <jrosser> and we kind of need to decide what we do/dont support
15:16:18 <noonedeadpunk> W is upgrade for Centos to Stream, right?
15:16:59 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Replace centos-8.x jobs with centos-8-stream  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/804036
15:17:05 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Set ovn hostname using nodename facts  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803988
15:17:10 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Fix OVN metadata protocol to point https  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803989
15:17:16 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Add support of OVN for CentOS-8-Stream  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803987
15:17:21 <spatel> centos-8.4 has broken OVS job, question is should we fix that or drop CI job and continue working with stream ?
15:17:22 <opendevreview> Jonathan Rosser proposed openstack/openstack-ansible-os_neutron master: Use list of cluster member for ovn ml2 agent to directly connect  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/803990
15:18:18 <noonedeadpunk> On W I'd say it would be great to fix that, but actually I kind of missed the reason at the first place. Smth related to some repos?
15:18:46 <jrosser> its several things, we need to fix ubuntu OVN on W regardless
15:19:08 <noonedeadpunk> yes, totally
15:19:09 <jrosser> we can decide if we add centos-8-stream OVN to W or not - or we say that is a feature from X onward
15:19:24 <spatel> Yes OVN repo is broken and this patch can fix it so i cut one patch to fix it but question is should we keep going with this kind of hack or drop it - https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/802402
15:19:27 <jrosser> and then there is the old centos-8 OVS jobs
15:20:43 <jrosser> it feels like this kind of delays 23.1.0
15:20:55 <noonedeadpunk> spatel: I'd say this patch would be relevant only for W and V?
15:21:08 <noonedeadpunk> No reason to merge that to master anyway
15:21:25 <jrosser> i think this was from before we dropped the old centos jobs from master
15:21:35 <spatel> i believe on W because i got issue with that, i didn't try on V yet
15:21:35 <noonedeadpunk> yeah
15:22:23 <spatel> CentOS community moved their repo to stream and that is why its failing to find latest OVS version for centos-8.4
15:23:21 <jrosser> lets deal with one thing at a time :/
15:23:25 <jrosser> too many moving parts
15:23:34 <spatel> +1
15:24:19 <noonedeadpunk> Ok, another thing. I was wondering if you have any thoughts regarding pain point, that could be selected as next community goals?
15:24:23 <noonedeadpunk> #link https://etherpad.opendev.org/p/pain-point-elimination
15:27:08 <spatel> Could you guy give review and bump to this patch, it will fix broken centos-8-stream distro deployment - https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/803475
15:29:00 <jrosser> spatel: did you see i left a comment on the depends-on?
15:29:28 <spatel> Just replied - var directory doesn't exist on chroot environment so when i tried /etc/yum/vars it failed to create var directory. may be we need to create first /etc/yum/vars directory first and then copy contents
15:30:16 <spatel> chroot doesn't have /etc/yum directory also
15:30:56 <spatel> for look like first we need to create empty /etc/yum and /etc/yum/var
15:31:12 <noonedeadpunk> I commented mentioned patch as well
15:31:51 <noonedeadpunk> Also I'd love to ask for some reviews of https://review.opendev.org/q/topic:%22bump_osa%22+(status:open)
15:32:03 <noonedeadpunk> As we didn't have a release for quite a while
15:34:01 <spatel> noonedeadpunk - nova has dependency requirement of some foo packages and that is part of this repo, without this repo it won't let you install nova components
15:34:25 <spatel> that is why distro installation failing
15:34:27 <jrosser> oh yes this is all nasty
15:34:38 <jrosser> its actually errors on the compute nodes that this fixe
15:34:40 <noonedeadpunk> doh
15:34:59 <noonedeadpunk> that is soooooo stupid....
15:34:59 <spatel> Yes..
15:35:21 <noonedeadpunk> good way to push ppl out of lxb...
15:35:26 <spatel> RPMs stuff someone may be be rebuildrequired: foo in spec file and that is why we endup here
15:35:45 <noonedeadpunk> ok, thanks for explanation
15:36:23 <spatel> i think its totally safe for add repo its not going to hurt so far
15:37:43 <noonedeadpunk> considering it's for distro setup only - I don't care _that_ much
15:39:12 <spatel> totally! that patch exclusively adding repo, no matter source or distro
15:39:36 <noonedeadpunk> uh, that's worse.
15:40:00 <noonedeadpunk> as eventually we're trying to control packages that are to be installed from repos that not present by default
15:40:22 <spatel> we can put condition if that is better way to handle it
15:40:34 <noonedeadpunk> that's why we drop epel-release there iirc
15:41:16 <noonedeadpunk> as well as centos-release-storage-common
15:41:34 <spatel> hmm, pervasively i created this patch to solve distro issue but then abandon it - https://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/803368
15:42:36 <jrosser> well nova role doesnt run on network nodes though? so we end up with wierd differences in OVS repo between hosts
15:44:22 <spatel> if we are concern then lets put condition == distro and push that patch out after review
15:45:05 <noonedeadpunk> yeah
15:45:33 <noonedeadpunk> we can really do like (service_install_method | default('source') == 'distro') | ternary('present', 'absent')
15:46:14 <spatel> ok
15:48:55 <opendevreview> Dmitriy Rabotyagov proposed openstack/ansible-role-vault master: Initial commit to Vault role  https://review.opendev.org/c/openstack/ansible-role-vault/+/800792
15:53:34 <noonedeadpunk> btw, have any folks were coming with questions regarding ^ ?
15:53:47 <noonedeadpunk> or they just PMing me regardless....
15:58:10 <noonedeadpunk> ok, whatever actually:)
15:58:15 <noonedeadpunk> #endmeeting