15:00:22 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:00:22 <opendevmeet> Meeting started Tue Jan 16 15:00:22 2024 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:22 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:22 <opendevmeet> The meeting name has been set to 'openstack_ansible_meeting'
15:00:27 <noonedeadpunk> #topic rollcall
15:00:29 <NeilHanlon> o/
15:00:29 <noonedeadpunk> o/
15:00:32 <NeilHanlon> morning
15:00:41 <NeilHanlon> afternoon, i guess ;)
15:00:42 <noonedeadpunk> heya :)
15:00:52 <noonedeadpunk> it's slightly closer to evening hehe
15:01:11 <noonedeadpunk> 4pm
15:01:24 <NeilHanlon> ah, yeah
15:01:43 <NeilHanlon> we've got lightly falling snow outside right now... not looking forward to cleaning it up later
15:02:40 <noonedeadpunk> when I asked locals when they saw snow last time, they answered that it was in 2016
15:03:11 <noonedeadpunk> so I kinda get nostalgic about snow
15:03:20 <noonedeadpunk> #topic office hours
15:03:38 <noonedeadpunk> We had relatively calm week I'd say
15:04:02 <noonedeadpunk> as a result - no new bugs. And this allowed to merge bumps and propose new point releases
15:04:31 <noonedeadpunk> except 2023.2, which I proposed as bugfix, rest are minor releases
15:06:10 <noonedeadpunk> Also I see that reviews started for openstack_resources role: https://review.opendev.org/q/topic:%22osa/openstack_resources%22
15:07:42 <noonedeadpunk> Also interestingly, update of ansible version results with quite weird/bad failures: https://review.opendev.org/c/openstack/openstack-ansible/+/905619
15:08:16 <noonedeadpunk> with "Could not find a module for {{hostvars['aio1_repo_container-b7922f21']['ansible_facts']['pkg_mgr']}}." during python_venv_build
15:09:29 <noonedeadpunk> and fails here o_O https://opendev.org/openstack/ansible-role-python_venv_build/src/branch/master/tasks/python_venv_wheel_build.yml#L19-L32
15:10:13 <noonedeadpunk> have close to no idea why it fails only for lxc
15:11:47 <noonedeadpunk> Another "interesting" topic changes to dynamic_inventory logic: https://review.opendev.org/c/openstack/openstack-ansible/+/905438/2
15:12:27 <noonedeadpunk> basically there're 2 goals: 1 - name LXC containers in a same way as their hostname as today we have mess with underscores/dashes in name
15:13:49 <NeilHanlon> weird...
15:14:28 <noonedeadpunk> and second to get rid of ANSIBLE_TRANSFORM_INVALID_GROUP_CHARS: https://opendev.org/openstack/openstack-ansible/src/branch/master/scripts/openstack-ansible.rc#L60
15:14:39 <noonedeadpunk> yeah, ansible failure is just crazy....
15:14:48 <noonedeadpunk> and what's more interesting, it's only for LXC
15:15:05 <noonedeadpunk> so potentially somehow related to connection plugin changes...
15:18:27 <NeilHanlon> yeah, could be...
15:20:25 <damiandabrowski> hey! sorry, I'm late again...
15:20:52 <noonedeadpunk> no worries
15:25:38 <jrosser> o/ hello
15:25:53 <NeilHanlon> heya damiandabrowski, jrosser
15:31:17 <noonedeadpunk> but eventually I have nothing to add for today.
15:31:34 <noonedeadpunk> shortly will try to have a look at pki role regarding vault integration
15:31:42 <noonedeadpunk> but likely not this week
15:41:13 <jrosser> nothing much from me, i work a lot on the capi patches at the moment to try to make a CI job
15:41:26 <noonedeadpunk> ++
15:41:37 <noonedeadpunk> yeah, that is really nice thing to have
15:41:55 <jrosser> need to get something to pass and merge it quick
15:41:55 <noonedeadpunk> I'm pretty much looking forward to it as well
15:42:17 <jrosser> as there are a lot of moving parts and we need CI to give some assurances about bumping versions of collections etc
15:43:29 <noonedeadpunk> Interesting part, if vexxhost collections do have some "fixed" requirements for dependencies
15:45:23 <noonedeadpunk> Hopefully, they will keep reasonable compatability for these https://github.com/jrosser/ansible-collection-kubernetes/blob/main/galaxy.yml#L11-L13
15:46:22 <noonedeadpunk> As recently we had some hassle with bein unable to resolve ansible requirements between osa and another collection
15:49:24 <jrosser> ah well git blame says i fixed those :)
15:49:48 <jrosser> becasue of exactly that reason
15:50:01 <noonedeadpunk> ugh, crap, ok, they did excatly what I was afraid of then
15:50:26 <jrosser> originally there was specific versions called for
15:50:27 * noonedeadpunk no idea why one would do that
15:50:36 <noonedeadpunk> or well.
15:50:36 <jrosser> and i changed it to be >=
15:50:58 <noonedeadpunk> I know the reason but no idea how this can be used in a real world
15:51:27 <noonedeadpunk> Like galaxy.yml should be treated as pyproject.toml (setup.txt)
15:51:55 <noonedeadpunk> where you define minimal requirements, but then you have some requirements.yml with specific ones
15:54:27 <noonedeadpunk> or dunno...
16:00:54 <noonedeadpunk> #endmeeting