15:01:00 <noonedeadpunk> #startmeeting openstack_ansible_meeting
15:01:02 <openstack> Meeting started Tue May 25 15:01:00 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:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:05 <openstack> The meeting name has been set to 'openstack_ansible_meeting'
15:03:10 <jrosser> o/ hello
15:03:24 <gshippey> o/
15:03:28 <noonedeadpunk> o/
15:03:53 <noonedeadpunk> #topic office hours
15:04:08 <noonedeadpunk> So we're kind of being pushed to do branching
15:04:35 <noonedeadpunk> I'm trying to hold this until linters be fixed. And also want pki stuff to land
15:05:48 * jrosser looks at etherpad
15:06:05 <noonedeadpunk> #link https://etherpad.opendev.org/p/osa-wallaby
15:06:50 <noonedeadpunk> I think send_service_user_token will go to X :(
15:07:01 <noonedeadpunk> other then that, we can backport
15:07:15 <openstackgerrit> Jonathan Rosser proposed openstack/ansible-hardening master: Remove references to unsupported operating systems  https://review.opendev.org/c/openstack/ansible-hardening/+/781061
15:09:31 <jrosser> hmm looks like heat don't merge the json policy stuff yet
15:09:38 <noonedeadpunk> it's not
15:10:03 <noonedeadpunk> an in X they jsut drop json support on oslo side
15:10:21 <noonedeadpunk> Which make heat is weird shape without any migration period...
15:10:42 <jrosser> so we're kind of left with https://review.opendev.org/q/topic:%2522osa/pki%2522+(status:open)
15:10:55 <jrosser> and whatever else is on the review dashbaord that needs to be in for W
15:11:31 <jrosser> i need to do some documentation for the PKI setup and move the vars to group_vars
15:11:37 <noonedeadpunk> Once linter will be settled down - we will be able to start reviewing and rechecking things
15:11:41 <jrosser> -ENOTIME right now though
15:13:13 <noonedeadpunk> I have some I think, at least until new CTO will take their place
15:13:48 <noonedeadpunk> The issue is with stable branches and linters
15:14:15 <noonedeadpunk> I pushed https://review.opendev.org/c/openstack/openstack-ansible-tests/+/792906 to workaround, but seems like bigger issue with tempest is there
15:14:31 <noonedeadpunk> (haven't checked yet)
15:15:26 <noonedeadpunk> oh, I can focus on bullseye during this week
15:18:00 <Gilou> noonedeadpunk, will do, but I need to rebuild a bit, I'm back on a kolla setup.. however, this seems to assume the backports were configured already, I'm pretty sure I had to add a debian backports entry myself, but I may be wrong…
15:18:27 <Gilou> also I was not on master, it was for victoria, so that might be the issue as well
15:18:55 <jrosser> noonedeadpunk: i made a bullseye AIO, and it kind of worked, but somehow it got slower and slower during the deployment then all the lxc stuff broke
15:19:04 <noonedeadpunk> I think we have the same for V tbh
15:19:21 <noonedeadpunk> jrosser: um.....
15:19:58 <jrosser> it created the containers and things, and then as it was progressing through setup-openstack everything went bad
15:20:01 <noonedeadpunk> I think we kind of stuck with lxc in CI
15:20:06 <jrosser> would be interesting to know if you can reproduce that
15:20:22 <jrosser> and there was nothing obvious i could find in the lxc logs
15:20:24 <noonedeadpunk> yeah, will have a look at it
15:20:38 <jrosser> i downloaded the bullseye daily build cloud image
15:23:52 <Gilou> yes, it's already there, but unless the pinning made me blind (and got overidden by my manual bpo entry), I think there was no entry for debian backports (only deb / osbpo…) but, let's not waste time, I'll check again :P
15:27:39 <jrosser> something strange happens on that V linters patch with tempest
15:28:48 <noonedeadpunk> yeah, like it get's master tempest?
15:29:10 <noonedeadpunk> I haven't chance to spawn VM though
15:29:57 <jrosser> though on OSA master we still have `tempest run -l`
15:30:19 <jrosser> and seems that way on the stable branches too
15:30:45 <jrosser> but on a stable branch we install tempest from pip package, so maybe there is a constraint error somewhere
15:32:12 <noonedeadpunk> yeah, and we have super weird logic in tempest role when it comes to constraints
15:32:29 <noonedeadpunk> btw, I think the only repo left with native linters - is integrated one
15:33:53 <jrosser> oh well it's master https://zuul.opendev.org/t/openstack/build/f783eeac959a41c7b394156fe45f0f3e/log/logs/openstack/keystone1/python_venv_build.log.txt#29486
15:36:30 <noonedeadpunk> I really can hardly recall logic we have... I know that on stable branches we remove tempest sha bump...
15:36:43 <noonedeadpunk> But I think we don't use master anyway? Or do we?
15:37:19 <jrosser> then on openstack-ansible-tests i have no idea, isnt that different again
15:37:32 <jrosser> as this is all functional tests breaking
15:38:26 <jrosser> but really we do remove nearly all use of this now
15:38:35 <jrosser> would be worth looking again where actually we use these jobs
15:40:09 <noonedeadpunk> yeah, agree
15:40:16 <noonedeadpunk> Was just thinking about that
15:40:32 <noonedeadpunk> I don't think we need it for doc/release notes
15:42:47 <openstackgerrit> Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump ansible-lint version  https://review.opendev.org/c/openstack/openstack-ansible/+/792154
15:43:06 <openstackgerrit> Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Bump ansible-lint version  https://review.opendev.org/c/openstack/openstack-ansible/+/792154
15:43:51 <jrosser> this was part of the motivation to take a look at molecule a bit
15:44:13 <jrosser> i.e don't introduce a bunch of tests for the pki role that mean openstack-ansible-tests has to stay around for longer
15:45:20 <noonedeadpunk> molecule feels like not quite easy to make I guess
15:45:56 <noonedeadpunk> but I think we can use integrated repo as well for it?
15:47:45 <noonedeadpunk> It's more about having molecule.yml inside role which we test?
15:48:33 <noonedeadpunk> but dunno
15:50:07 <jrosser> not sure, andrewbonney was taking a quick look at what was / was not possible
15:55:33 <noonedeadpunk> Am I stupid or blind? What's wrong with https://zuul.opendev.org/t/openstack/build/92c3b8d9dc184dd9b301cb69732457eb ?
15:56:19 <noonedeadpunk> We have `openstackdocstheme>=2.2.1` in requirements. And `openstackdocstheme===2.2.7` in constraints. How in the world is this conflicting?
15:59:33 <openstackgerrit> Merged openstack/openstack-ansible-os_ironic master: Replace linters test with integarted one  https://review.opendev.org/c/openstack/openstack-ansible-os_ironic/+/792608
15:59:56 <jamesdenton> is it the triple equal?
16:00:10 <jrosser> this https://opendev.org/openstack/openstack-ansible-tests/src/branch/master/doc/requirements.txt#L14
16:00:22 <jrosser> fights with https://opendev.org/openstack/requirements/src/branch/master/upper-constraints.txt#L394
16:01:19 <jamesdenton> ignore me. lol
16:01:25 <jamesdenton> hi jrosser :)
16:01:35 <jrosser> o/ hello
16:02:52 <jrosser> is it that one of those is in a constraint, and the other a requirement
16:02:52 <noonedeadpunk> yeah, but one is requirement and other is contstraint? I mean we can provide in requirements like minimal version required and some specific one in constraints? and until they do not interfer - that should be fine?
16:03:00 <noonedeadpunk> Or this is not the case with new resolver?
16:05:56 <noonedeadpunk> http://paste.openstack.org/show/805707/
16:06:02 <noonedeadpunk> #endmeeting