Tuesday, 2024-09-24

noonedeadpunkgood morning07:19
noonedeadpunkyesterday we've got couple of new bug reports, so going to look through them07:19
jrossero/ morning07:47
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Define default value for `neutron_default_availability_zones`  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93026507:51
jrosseri wonder where we should ensure that /etc/apt/sources.list.d exists08:01
jrosseropenstack_hosts doesnt really have an existing function for making directories08:01
noonedeadpunkthat's a good question08:05
jrosserthere is `openstack_hosts/tasks/openstack_hosts_configure_apt.yml`08:06
jrossermaybe thats the best place - it gets run on the host before the containers are created, so we should only need to add it once there08:06
noonedeadpunkright efore where repo is being added seems like not bad place08:07
noonedeadpunkyeah08:07
noonedeadpunkbtw, talking about that - there's also a fresh bug report on replated topic: https://bugs.launchpad.net/openstack-ansible/+bug/208177508:07
jrosseri wonder why we dont see that fail08:09
noonedeadpunkdo we test lxc on debian even?08:10
noonedeadpunkoh, yes, we do08:10
noonedeadpunkand they've submitted another one for arm: https://bugs.launchpad.net/openstack-ansible/+bug/208176408:11
jrosserdoh ok08:12
jrosseri will need to make an experiment for that, its an ugly fixup already08:13
noonedeadpunkI'm thinking about just some mapping?08:13
jrosserwell, it's either a list or a string08:13
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Ensure apt sources.list.d directory exists.  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027208:13
jrosserand it can be many architectures, some of which need fixing08:14
noonedeadpunkum, any reason to add many architectures to the same host?08:14
noonedeadpunkI checked and UCA has same thing - arm64, not aarch08:15
jrosserwell - i just have made the code "pass through" then functionality of the ansible module08:15
noonedeadpunkI can recall having some arch mapping somewhere already...08:16
jrosserlxc i think?08:16
jrosserthough we did get rid of a lot of complexity there08:16
noonedeadpunkyeah - _architecture_fixup08:16
noonedeadpunk* https://opendev.org/openstack/openstack-ansible-lxc_hosts/src/branch/master/defaults/main.yml#L29-L3408:16
noonedeadpunkso pretty much - we can move such mapping to global level?08:17
jrosserthat makes the roles not self contained then08:18
noonedeadpunkoh, yes, there's galera and rabbit as well08:18
noonedeadpunkas for lxc and openstack_hosts - they're probably never were self contained?08:18
noonedeadpunkthen yeah - copy/paste I guess...08:20
jrosseraaah the osbpo key thing is bacuse we don't vendor the key into the repo08:20
jrosserwe give an external url to the key instead08:20
noonedeadpunkah08:20
jrosseri'll fix that08:20
jrosseras it's not helpful for offline things08:20
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027808:37
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Enable UCA repo for ubuntu noble  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92963108:37
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027808:38
jrossernoonedeadpunk: map('extract', openstack_architecture_mapping) would i think let you keep the original list / not list behaviour08:43
jrosseri think that will replace in turn each list member from the input without needing a loop08:44
noonedeadpunkI guess I don't get list/non-list issue?08:44
noonedeadpunkas module seems to accept both ?08:44
noonedeadpunkit's like package - where you can supply a list of packages or a single one, no?08:44
jrosserwell its just that to expose the complete functionality of the deb822_repository module, the `architectures` parameter can be either list or string08:46
jrosserso i had a allowed that to be the case in the vars/debian.yml vars/ubuntu.yml repo definitions too08:46
opendevreviewJonathan Rosser proposed openstack/openstack-ansible-openstack_hosts master: Vendor osbpo gpg key into the role  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93028008:51
noonedeadpunkyeah, but why to control that? Whatrever user will provide in `_package_repos` for specific repo will be jsut passed to the module08:57
noonedeadpunkand then module on it's own doesn't care if it's a single element or a list08:58
noonedeadpunkone repo can be string, another list... whatever?08:58
jrosserwell maybe you're right - i've put the complexity in the wrong place09:00
jrossertrying to fix up the data as it gets passed to the module, rather than have it be fixed up in the input data09:01
noonedeadpunkit wasn't bad, just if we need to have quite some arches supported - that become a bit tough...09:01
noonedeadpunkor well, dunno09:01
jrosserbtw i am not really understanding whats happening with https://bugs.launchpad.net/openstack-ansible/+bug/208177509:02
noonedeadpunkif you wanna keep the _architecture_fixup - we can do that as well I guess09:02
jrosserbecasue in our CI jobs the key is actually in /etc/apt/trusted.gpg09:02
jrosserwell - _architecture_fixup is messy and it's likley better to simplify it09:03
jrosserso i think your solution is better/simpler actually09:03
noonedeadpunkregarding `/etc/apt/keyrings` - no idea actually09:05
noonedeadpunkI was thinking to spawn a debian sandbox09:05
noonedeadpunkI wonder if that has smth to do with deploy host being on Ubuntu09:05
jrosseryeah there is something odd there09:07
jrosserwe are definatly missing copying the keyrings directory though09:07
jrosserbut when i look on a zuul job log both host and container /etc/apt/keyrings directory is empty09:08
jrosserbtw 930278 is not a direct fix for 2024.1 - only master09:10
noonedeadpunkyeah, as we don't use deb822 on 2024.1 yet09:15
jrosserand looking on stable/2024.1 i'm not sure i see architecture being used in the repo defnintion09:16
noonedeadpunkwell it feels that reporter does not actualy use 2024.109:17
noonedeadpunkas they supply master links and reffer to it as well.09:17
noonedeadpunkbut dunno09:17
jrosseryeah, perhaps we should ask about that09:17
jrosseri can try to make a debian/12 arm vm and try09:17
noonedeadpunkI wonder if we should just drop arch from repo definition instead :D09:19
jrosserfwiw we have an amd64 deploy host here and one aarch64 infra host in each deployment09:19
jrosserso this does work, at least for bobcat09:19
noonedeadpunkyeah, this could be really jsut master issue, as no changes in repos were made between bobcat and caracal09:20
noonedeadpunkthough, I assume you haven't re-created containers at least since antelope09:21
noonedeadpunkso that could slip on bobcat09:21
jrosserprobably not, and its a bit unusual as i think the aarch64 host only has utility and repo on it09:22
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-galera_server master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/93028209:22
noonedeadpunkoh, yeah. true as well09:23
jrosserwe just sit that sort of off to the side as a 4th very minimal infra host for buiding wheels09:24
noonedeadpunkI guess there could be arm-only deployments... But yeah....09:24
jrosserand the original 3 x86 ones are much more as you'd epect09:24
jrosserthe bug report about osbpo keyring is also consistent with using master imho09:25
noonedeadpunk++09:25
noonedeadpunkso probably good as we likely don't need to backport anything09:26
noonedeadpunkand well - good it was raised timely :)09:26
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-rabbitmq_server master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/93028309:27
noonedeadpunkfwiw that seems to be rax who reported issues :)09:33
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Enable UCA repo for ubuntu noble  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/92963109:35
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027809:35
jrosseroh well thats nice :)09:36
jrosserneed to encourage them to join us here09:37
noonedeadpunkI think they're kind of one leg into k8s deployment already though09:37
noonedeadpunkjust "old" deployments which left or so...09:37
noonedeadpunkbut not sure09:38
jrosseryeah i've seen what cloudnull was doing09:38
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-ceph_client master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/93028409:41
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Ensure that selected Apache MPM is enforced  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/92969509:48
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Convert Skyline HAProxy httpcheck  https://review.opendev.org/c/openstack/openstack-ansible/+/92989209:49
noonedeadpunkjrosser: do you have same compute names in hypervisor list vs compute service list? Or fqdn vs hostname ?10:52
jrossernoonedeadpunk: they are the same, and they are fqdn10:54
noonedeadpunkok, asking in context of https://opendev.org/openstack/openstack-ansible/blame/branch/master/scripts/upgrade-utilities/nova-restore-compute-id.yml#L3310:54
noonedeadpunkas for us in most deployments `ansible_facts['fqdn']` will be correct option10:54
jrosserso for me ansible_nodename is also the fqdn10:57
noonedeadpunk++10:58
jrosseransible_fqdn is "localhost"......10:58
* jrosser surprised10:58
noonedeadpunkwait, what?11:00
noonedeadpunksmth sounds off with /etc/hosts I'd guess11:01
jrosserhuh11:02
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Use node FQDN for nova-restore-compute-id  https://review.opendev.org/c/openstack/openstack-ansible/+/93029211:13
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_keystone master: Change example to contain domain name instead of UUID  https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/91956311:20
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_keystone master: Change example to contain domain name instead of UUID  https://review.opendev.org/c/openstack/openstack-ansible-os_keystone/+/91956311:21
gokhanhello noonedeadpunk, venv_wheels_rebuild is not wirking in skyline role. there is also a minor issue about masakari dashboard on skyline. In masakari role service type is ha https://github.com/openstack/openstack-ansible-os_masakari/blob/master/defaults/main.yml#L119 but in skyline role, it is defined as instance-ha https://opendev.org/openstack/openstack-ansible-os_skyline/src/branch/master/vars/main.yml#L46. 11:26
noonedeadpunkgokhan: so you tried to replace instance-ha with ha and it worked? (or vice versa)11:31
gokhannoonedeadpunk, yes it worked 11:43
gokhanwithout this change it can not add masakari proxy setting to skyline vhost config file 11:44
noonedeadpunkum... maybe you can propose a change then ?:)11:46
noonedeadpunkpreferably - to skyline role :)11:48
jrosseris it that we actually have it inconsistent in the masakari role (codesearch finds lots of instance-ha)11:50
gokhanjrosser, yes I think masakari role is inconsistent because in masakari installation guide service type is instance-ha 11:51
gokhanhttps://docs.openstack.org/masakari/latest/install/install_and_configure_ubuntu.html11:51
gokhannoonedeadpunk, we need to also update zun role 11:52
jrosserzun is likley very broken11:52
noonedeadpunkwell. We can actually patch masakari role. but then there's a question about if (and how long) we wanna backport it11:52
gokhanhttps://review.opendev.org/c/openstack/kolla-ansible/+/90416411:52
gokhanlike kolla ansible did, we make changes on zun role it worked. we don't need to pin docker version11:53
gokhanwe do not need to install etcd also 11:53
jrossergokhan: if you are using the zun role i would highly highly recommend taking on the maintaance of it11:53
jrosserif you've been able to make local patches that work, then you have done 99% of whats needed to contribute the necessary fixes11:54
gokhanjrosser, yes we are using it. we are very busy for internal works in these days, but next week we will plan to commit changes 11:56
noonedeadpunkyeah, as the thing is, that we don't have Zun usage here, so really hard to catch-up with it11:57
jrossersame here - we do not use it and I have no spare time to learn it11:57
opendevreviewMerged openstack/openstack-ansible-os_neutron stable/2024.1: Do not kill ipsec on L3 cleanup  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93018812:02
gokhanok  harun will send the patches next week for zun, there are no new features on zun. Harun can fix the gates  12:04
noonedeadpunkthat would be actually great12:05
noonedeadpunkwe will help where we can, but hard to justify time to fully dive into service that there're no plans to use :(12:07
noonedeadpunkI will check on masakari now12:07
jrosserwhen can we update this? https://opendev.org/openstack/openstack-ansible-openstack_hosts/src/branch/master/defaults/main.yml#L2212:16
opendevreviewMerged openstack/openstack-ansible-os_octavia stable/2024.1: Provide better flexability for SSH keypair options  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/92964912:24
noonedeadpunkjrosser: once rdo/ospb/uca release dalmatian packages13:00
jrosseri think that uca and debian are released13:00
jrosseroh maybe there is something for rdo too https://trunk.rdoproject.org/centos9-dalmatian/report.html13:02
* jrosser not sure about that13:03
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Define default value for `neutron_default_availability_zones`  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93026513:04
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Define default value for `neutron_default_availability_zones`  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93026513:05
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_masakari master: Rename Masakari service type  https://review.opendev.org/c/openstack/openstack-ansible-os_masakari/+/93032913:37
noonedeadpunkgokhan: ^ this should address masakari thing13:38
noonedeadpunkjrosser: sorry for stupid question, but does octavia dashboard work for you in Horizon as a user?14:21
andrewbonneynoonedeadpunk: I've just taken a look and it certainly displays load balancers at least14:29
jrosserandrewbonney: which release did you look at?14:29
andrewbonneyThat's OSA 29.0.014:31
noonedeadpunkhuh14:37
noonedeadpunksomehow for me it shows for admin, but not for any user on 29.0.014:38
noonedeadpunkso really o_O about why14:38
noonedeadpunkok, will try to re-spawn things then, thanks!14:38
* NeilHanlon waves g'morning15:00
noonedeadpunk#startmeeting openstack_ansible_meeting15:01
opendevmeetMeeting started Tue Sep 24 15:01:08 2024 UTC and is due to finish in 60 minutes.  The chair is noonedeadpunk. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'openstack_ansible_meeting'15:01
noonedeadpunk#topic rollcall15:01
NeilHanlono/15:01
noonedeadpunko/ hey Neil!15:01
damiandabrowskihi!15:01
NeilHanlonhi damiandabrowski, noonedeadpunk :) 15:02
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Link plugin settings extension separately  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/93034615:05
noonedeadpunk#topic office hours15:05
noonedeadpunkso, we do have bunch of things for review15:05
noonedeadpunkand our gates on master are blocked by this: https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027215:05
NeilHanlon+2 from me :) (and the W+1)15:06
noonedeadpunknice, thanks a lot!15:07
noonedeadpunkwe also got quite some bug reports this week already15:07
noonedeadpunkI was trying to go through them, but facing more and more nits along the way15:07
noonedeadpunkI think https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929549 was one of latest backports to 2024.1 I wanted to have before making a release15:09
noonedeadpunkah, and ofc https://review.opendev.org/q/topic:%22osa/apache_mpm_alignment%22 is quite a topic on itself15:09
noonedeadpunkbut it kinda is also needs to be backported..15:10
NeilHanlonfun...15:10
noonedeadpunkas on metal they do conflict, esp if skyline is in15:10
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Link plugin settings extension separately  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/93034615:11
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_horizon master: Link plugin settings extension separately  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/93034615:11
noonedeadpunkand with that new release is coming rapidly15:12
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Define default value for `neutron_default_availability_zones`  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93026515:14
NeilHanlonyep yep15:15
noonedeadpunkthere's also an update regarding mariadb 11.4 - the issue where we'd had to issue SSL cert for localhost was fixed upstream15:15
noonedeadpunkSo it should be in the next release15:16
noonedeadpunkthough, I don't know when it will be :(15:16
noonedeadpunkto be specific - in 11.4.415:17
NeilHanlonat least it's being fixed :) 15:18
NeilHanlonon rocky mirrors: I met again w/ infra group last week and presented some findings--result of which is I will put in a Change to setup the sync for Rocky mirrors and then work with infra to get an afs share/quota configured15:19
noonedeadpunkok, that is a nice update15:19
noonedeadpunkI haven't seen Rocky specific failures due to mirrors last week, fwiw15:20
noonedeadpunkso it seems they've improved a lot since ... winter?15:20
NeilHanlonif my theory is correct, there should be some failures in a day or so once we release a batch of updates RH put out last night15:20
noonedeadpunkI also had some fun with OVN and Neutron lately, found 1000x regression in performance, which also affected Nova listings15:23
noonedeadpunkfix for that landed yesterday for neutron and backports were proposed as well.15:23
NeilHanlonouch!15:24
noonedeadpunk#link https://review.opendev.org/c/openstack/neutron/+/92994115:24
noonedeadpunkAnd I do recall someone coming to IRC with question about performance regression after upgrade15:24
noonedeadpunkso here we are...15:24
jrossero/ hello15:26
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-rabbitmq_server master: Map all relevant architectures for deb822 repository setup  https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/93028315:26
noonedeadpunkjrosser: where we are with moving playbooks to collections?15:30
noonedeadpunkonly services are left?15:30
jrosserah yes, i have not yet managed to look at the remainder15:30
jrosseropenstack services would indeed be the next thing to do15:30
jrosserwhich will leave some leftovers i think15:31
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Fix upgrade job on master to upgrade from 2024.1 to master  https://review.opendev.org/c/openstack/openstack-ansible/+/92877115:32
noonedeadpunkok, I can look into that I guess15:32
noonedeadpunkonce CI is unblocked I wanna take another look at SHA bump failres on master15:34
noonedeadpunkand potentially switch things to stable branches to track them15:34
jrosserwhat is left to make a release on Caracal?15:36
jrosserdo you want to get the mpm stuff backported for that?15:36
noonedeadpunkI think so...15:36
noonedeadpunkas that is quite breaking change15:36
noonedeadpunkand very unpleasant issue to deal with15:37
noonedeadpunkand also https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/92954915:37
noonedeadpunkI think that's all15:37
noonedeadpunkI don't know anything else which should be considered as critical for upgrade15:37
noonedeadpunkespecially with recent neutron backports :)15:40
noonedeadpunkas our 29.1.0 is smth I'd consider minorly upgrading to, hehe15:41
noonedeadpunk(is going to be)15:41
noonedeadpunkdamiandabrowski: it would be also nice if you could spend some time on reviews this week15:42
damiandabrowskiokok, i will!15:42
noonedeadpunkah - actually this patch is potentially a point for discussion: https://review.opendev.org/c/openstack/openstack-ansible/+/92977515:44
noonedeadpunk#link https://review.opendev.org/c/openstack/openstack-ansible/+/92977515:45
noonedeadpunkwhile it kind of make sense - I think it's might be better to patch haproxy15:45
noonedeadpunkis there reason why we define SSL for `bind` if haproxy_balance_type is tcp? 15:46
noonedeadpunk#link https://opendev.org/openstack/openstack-ansible-haproxy_server/src/branch/master/templates/service.j2#L5615:46
jrosserthe commit message is not helping me much there15:47
jrosserwere is this user certificate?15:47
noonedeadpunkif I'm not mistaken - it's about like any certificate15:47
jrossercan't you put sometimes tls on the console service itself15:48
jrosserand then this patch talks about haproxy, which is another place there could be a certficate15:48
noonedeadpunkI think what they are into is this15:49
noonedeadpunk#link https://zuul.opendev.org/t/openstack/build/a4616d160b9249289a16b5980bf3e58a/log/logs/etc/host/haproxy/conf.d/nova_novnc_console.txt#615:49
noonedeadpunkor well15:50
noonedeadpunk#link https://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/nova_all/haproxy_service.yml#L19-L2015:51
jrosserthis is complicated15:51
noonedeadpunkso if they do define `nova_console_user_ssl_cert` - they don't want haproxy to be configured with TLS15:51
jrosseras there is compute hosts <> novnc proxy15:52
jrossernovnc proxy <> haproxy15:52
jrosserand haproxy <> user15:52
jrosserand afaik we have have tls in all of those places15:52
noonedeadpunkyes, true, but then we do have `haproxy_nova_console_http_mode | ternary('http', 'tcp')`15:52
noonedeadpunkso if there's a `tcp` - we should not be adding TLS to BIND15:53
noonedeadpunkI don't think it will matter or terminate TLS on haproxy at all15:53
noonedeadpunkbut having `ssl` statement on bind is confusion15:53
noonedeadpunkI'm not 100% sure if I got it correctly15:54
noonedeadpunkas you said - it's really complicated15:54
noonedeadpunkand I personally can hardly asses what is intented behaviour here in fact15:54
jrosserno i am not able to make a clear understanding of the actual issue without much more thought15:56
noonedeadpunkbut what I'm into - is that probably having ssl defined in haproxy when `mode tcp` doesn't make sense?15:57
noonedeadpunkas my guess was that it's the thing which is confusing15:58
jrosseri think that we might have really old code here for the user_cert stuff15:58
jrosserlike here https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/tasks/consoles/nova_console_novnc_ssl.yml15:59
noonedeadpunkoh, wow, yes15:59
noonedeadpunkit might work though16:00
noonedeadpunkbut doesn't make much sense indeed16:00
jrosseri don't know why this is not covered by the pki role16:01
jrosseras i do think that james worked specifically on tls for the consoles16:01
jrosserand those vars are not in defaults/main.yml for the nova role either16:02
noonedeadpunkyep, seems like leftover which needs to be covered as well16:02
noonedeadpunkso good patch from standpoint of raising attention at least16:03
noonedeadpunk#endmeeting16:04
opendevmeetMeeting ended Tue Sep 24 16:04:31 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:04
opendevmeetMinutes:        https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-09-24-15.01.html16:04
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-09-24-15.01.txt16:04
opendevmeetLog:            https://meetings.opendev.org/meetings/openstack_ansible_meeting/2024/openstack_ansible_meeting.2024-09-24-15.01.log.html16:04
jrosserwhat actually is this even doing https://opendev.org/openstack/openstack-ansible-os_nova/src/branch/master/templates/nova.conf.j2#L22-L2716:06
jrosserit's not in a specific config section at all16:06
noonedeadpunkwell, it's a valid config option...16:07
noonedeadpunkhttps://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.ssl_only16:07
noonedeadpunkI'm not sure it's related in any way though16:08
jrossercert for what though :)16:08
noonedeadpunkand cert even does have console in related options...16:08
noonedeadpunkhttps://docs.openstack.org/nova/latest/configuration/config.html#console.ssl_ciphers16:09
noonedeadpunkso I assume, that's for nova-novncproxy service16:09
noonedeadpunkwhich is stupid enough and takes just defaults16:09
noonedeadpunkand that part could end up after merging all config files together for nova years ago16:11
noonedeadpunkbut then I really don't know where this connection stands in global view16:11
jrosserhttps://review.opendev.org/c/openstack/openstack-ansible-os_nova/+/81722216:12
noonedeadpunkoh, well16:13
noonedeadpunkbut this is different16:13
noonedeadpunkI guess that's an encryption between compute and nova-novncproxy?16:13
noonedeadpunkbut then proxy <-> haproxy is still unencrypted?16:14
noonedeadpunkas 6080 port - where you connect to novnc - is actually nova-novncproxy. and then proxy connects to vnc on computes, and it's where vencrypt makes difference?16:15
jrosserright yes ok16:15
noonedeadpunkyeah, I'm just realizing that we have this connection hardly covered right now16:16
jrosserso we do seem to have some mess for what happens with novnc proxy <> haproxy16:16
noonedeadpunkor well - in a very weird way16:16
noonedeadpunkyeah, exactly16:16
jrosseri don't really understand why we have a user certificate option for this16:16
noonedeadpunkas then we somehow enforce TCP connection?16:16
jrosserthat sounds like something from the past (like we also had for horizon and keystone), but now the pki role makes that pretty redundant16:16
noonedeadpunkwell, whatever, we provide user certs for many things. but how it's done does not make sense16:17
jrosserperhaps this got missed with the internal tls work16:17
noonedeadpunkyeah, likely16:17
jrosseror backend tls work, i mean16:17
jrosseri think james had done a whole bunch of stuff around nova, for tls live migration etc, and also covered the compute<>novncproxy part16:18
noonedeadpunkoh yes, that is covered for sure16:18
noonedeadpunkand then Damian was looking into internal TLS, which is this specific thing16:18
jrosserso kind of question is if really there is a sensible fix for master16:18
jrosseror if it is just wrong and needs to come into alignment with the rest of things16:19
jrosseri.e is it ever valid to apply tls on the novnc proxy and pass that through TCP at haproxy16:19
noonedeadpunkI don't think it makes sense to pass TCP at all in this case16:20
jrosserno, i agree16:20
noonedeadpunkso it should act as all others16:20
noonedeadpunkbut then it feels that we might need to have a separate conf file for novnc proxy16:21
noonedeadpunkI kinda scared of [DEFAULT]/ssl_only16:21
noonedeadpunkbut there's no other place to define that for novnc16:22
noonedeadpunk*proxy16:22
jrosseroh is it all related to this https://opendev.org/openstack/nova/src/branch/master/doc/source/cli/opts/websockify.rst16:23
noonedeadpunkhow it's all related to ipv6 /o\16:24
jrosseroh wtf :)16:24
noonedeadpunkI want to unsee this one16:25
jrosseroh its jsut formatting though isnt it?16:25
noonedeadpunkah, lol, true16:26
jrosserhttps://opendev.org/openstack/nova/raw/branch/master/doc/source/cli/opts/websockify.rst16:26
jrosserbut anyway those are truly terrible config option names, without a specific section16:26
noonedeadpunkbut it's same as in config reference then16:26
jrosserhmm ok so we need to add this to the todo list :/16:29
noonedeadpunkI added to https://etherpad.opendev.org/p/osa-epoxy-ptg16:30
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron master: Define default value for `neutron_default_availability_zones`  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/93026516:51
opendevreviewMerged openstack/openstack-ansible-openstack_hosts master: Ensure apt sources.list.d directory exists.  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93027216:57
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Increase MPM thread limits for Apache  https://review.opendev.org/c/openstack/openstack-ansible/+/93036217:05
jrosser^ tiny typo in the commit message there "thereads"17:08
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Increase MPM thread limits for Apache  https://review.opendev.org/c/openstack/openstack-ansible/+/93036217:08
noonedeadpunkah, damn, likely https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/929540 is also a plus for 2024.1 release, as otherwise centos will fail right away....17:10
noonedeadpunk(or any alternative to it)17:10
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-ceph_client master: Ensure apparmor folder exists for ceph caching  https://review.opendev.org/c/openstack/openstack-ansible-ceph_client/+/92960617:19
opendevreviewJonathan Rosser proposed openstack/openstack-ansible master: Use ceph mirror in CI jobs  https://review.opendev.org/c/openstack/openstack-ansible/+/92377717:21
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-openstack_hosts master: Switch codename to Dalmatian for 2024.2  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/93036817:24
jrosseri think we really need those mpm fixes in18:02
noonedeadpunkyeah, mpm as well18:04
noonedeadpunkdamiandabrowski: can you check on https://review.opendev.org/q/topic:%22osa/apache_mpm_alignment%22 better sooner then later?18:04
noonedeadpunkgokhan: fwiw, Zun doesn't look too promising in service CI either: https://review.opendev.org/c/openstack/zun/+/92865518:31
mnasernoonedeadpunk: have you made any progress on https://bugs.launchpad.net/magnum/+bug/2067345/comments/35 ? it's quite annyoing :\19:32
jrossersuper annoying :(19:35
jrosserwe are also revert / pin oslo.db19:36
mnaserjrosser: i wonder if 14.1.0 makes sense -- https://github.com/openstack/oslo.db/compare/14.1.0...15.0.019:56
mnaserthere's not much change ther, i wonder what is the oldest worknig19:56
noonedeadpunkmnaser: frankly - I spet close to zero time on that so far, except finding the bug and reverting back u-c19:57
mnaseri wonder if its a newer release that broke things, im looking at the diffs19:57
noonedeadpunkthe oldest working would be the one having autocommit :D19:57
mnaserblargh i guess its easier to just do the workaround, i may make an ml post about this19:59
noonedeadpunkbut no, I think your approach makes most sense19:59
noonedeadpunkIt could be some single scenarion missed or covered with writes where only reads are needed or smth like that20:00
noonedeadpunkI was struggling to cover that for Vitrage for quite a while. And sqlite backend was a very-very good way for testing such things20:00
mnaseri mean it definitely could be, i know there's almost always the greenthread with listing all clusters where it is borked20:00
noonedeadpunkas connections there are locking, so tests would fail if connections remain open20:01
noonedeadpunkbut I was told to leave the magnum alone for now, so... I did that...20:01
mnasernoonedeadpunk: how were you able to replicate those issues if you dont mind me asking, i can dig in deeper but i'm just at all, cause unit tests dont really trigger that issue20:02
mnaserhttps://paste.openstack.org/show/825346/ - its stuck on `clusters = objects.Cluster.list(ctx, filters=filters)` in this case20:03
mnaserwhich goes into `clusters = objects.Cluster.list(ctx, filters=filters)`20:03
mnasersorry i mean `db_clusters = cls.dbapi.get_cluster_list(context, limit=limit,`20:03
mnaserwhen i compared to ironic, it's not too far out design wise - https://github.com/openstack/ironic/blob/master/ironic/objects/node.py#L362-L36520:05
noonedeadpunkmnaser: to be fair - I did not replicated for magnum per say. it was taking us 5mins tops on production to hit this. I was more reffering to my "practise" on vitrage https://opendev.org/openstack/vitrage/commit/d6b5247dbb1acedd43b3dc8e7b1cac06519467c420:06
noonedeadpunkbut only sqlite tests were catching this on unit20:07
mnasernoonedeadpunk: yeah exactly what i ran into as you ran into, without the context passing :(20:07
noonedeadpunkwell, seems magnum uses sqlite by default anyway: https://opendev.org/openstack/magnum/src/branch/master/magnum/tests/conf_fixture.py#L30-L3120:14
noonedeadpunkso yeah, then it's all irrelevant :(20:14
cringdahlhey, i'm the one that filed this business:20:20
cringdahlhttps://bugs.launchpad.net/openstack-ansible/+bug/208183120:20
cringdahljrosser: you talked about a patch in your reponse?20:21
cringdahlin all fairness, I discovered the apply_security_hardening var and set it to false, which got me moving again20:22
noonedeadpunkoh yes, that would be one way of doing that. 20:23
noonedeadpunkthe role needs some love and update as well though20:24
noonedeadpunkit's kind of a pity that amount of donors with arm has dropped dramatically20:27
noonedeadpunkas basically arm64 path in openstack is left almost without testing overall20:27
cringdahlI'm happy to be contributing to the open source community, then, if only with smoke tests20:28
jrossercringdahl: hi20:28
jrosserI will try to look at a patch for the security hardening role tomorrow to make it arm-aware, unless you want to submit something in the meantime?20:29
* noonedeadpunk singing off for today20:29
cringdahlthanks for that. I'm happy to wait until tomorrow, as I've bypassed with apply_security_hardening.20:30
cringdahland also i'm still struggling to get the whole thing running. :)20:30
cringdahlanyone know why /etc/glance/glance-api-paste.ini wouldn't get written by role os_glance?20:31
cringdahlI'm digging around, this one is eluding me20:31
jrosserwell - one thing you can do is to use the CI jobs as a reference20:40
jrosserin the irc topic you'll see a link to the code review dashboard at http://bit.ly/osa-review-board-v520:40
jrosserthen i picked a job for the openstack-ansible repo that was passing on master branch https://review.opendev.org/c/openstack/openstack-ansible/+/92963620:41
jrosserunder the zuul summary tab you can see all the job results, so looking in one for debian targets with lxc containers https://zuul.opendev.org/t/openstack/build/bb4980fac89647bc8c5165536276c0c720:42
jrosserwe can look in the job log and see where the glance-api-paste file is handled https://zuul.opendev.org/t/openstack/build/bb4980fac89647bc8c5165536276c0c7/log/job-output.txt#11001-1101520:43
jrosserthen we can also take a look at what it actually did for that file https://f4f8ba04bafc0163e558-e001c969608179e00bcb6eab56a8fbc9.ssl.cf5.rackcdn.com/929636/1/check/openstack-ansible-deploy-aio_lxc-debian-bookworm/bb4980f/logs/etc/openstack/aio1-glance-container-5f30c3f4/glance/20:44
cringdahljrosser: thanks for all that! 'Preserve original configuration file(s)' is where glance-api-paste.ini states failure to even exist, whereas rootwrap.conf comes back fine.20:49
cringdahlI could paste here, but I fear it'll be real spammy20:49
jrosserpaste.opendev.org :)20:50
cringdahlsweet20:52
cringdahlhttps://paste.opendev.org/show/825584/20:53
mnasernoonedeadpunk, jrosser: posted on the ML, maybe someone has a clue from oslo.db side20:53
noonedeadpunk++ thanks!20:54
jrossercringdahl: this is important https://zuul.opendev.org/t/openstack/build/bb4980fac89647bc8c5165536276c0c7/log/job-output.txt#1086921:03
jrosser /etc/glance is supposed to by symlinked into the built venv for glance21:06
cringdahljrosser: updated the paste with what I see instead of that output21:06
jrosseri think its made a new paste for you21:07
cringdahlhttps://paste.opendev.org/show/825586/21:09
cringdahlThere is no /usr/etc in this glance container21:09
noonedeadpunkcould it be that wheels/venv build has failed on previous run?21:10
noonedeadpunkas then you might wanna try to re-run the role with `-e venv_rebuild=true`21:11
cringdahlwhere would that -e flag go? I'm running all this through the openstack-ansible script21:13
opendevreviewMerged openstack/openstack-ansible-haproxy_server master: Respect defined interface for external VIP with LE  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/92433321:14
jrossercringdahl: just to check - this is a source based install?21:15
jrosserthe openstack-ansible script is a pretty thin wrapper around ansible-playbook21:16
jrosserso any of the options to ansible-playbook will be also ok as options for openstack-ansible21:17
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server stable/2024.1: Respect defined interface for external VIP with LE  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/93038421:19
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server stable/2023.2: Respect defined interface for external VIP with LE  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/93038521:20
cringdahljrosser: distro based21:20
jrossercringdahl: i was just going to say21:20
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-haproxy_server stable/2023.1: Respect defined interface for external VIP with LE  https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/93038621:20
jrosserbecause in your paste https://github.com/openstack/openstack-ansible-os_glance/blob/master/tasks/glance_install.yml#L95 this is false21:20
jrosserso basically don't do a distro install21:20
noonedeadpunkas a matter of fact - distro-based is not really supported for Debian21:20
cringdahlha21:20
cringdahldang21:21
jrossertime to start again from fresh with a source install, i'm afraid21:21
cringdahlI got really far!21:21
jrosseryou need a really good reason to choose a distro install21:21
noonedeadpunkI've started one day looking into it just to realize that packaging is completely different: https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/79422021:21
cringdahlmy really good reason was thinking it would be faster overall21:21
noonedeadpunkyeah, we could implement some protection indeed21:22
jrosserthat maybe true, but you will pay a large price in the long term21:22
noonedeadpunk++ ^21:22
jrosserand in the short term, our test coverage of distro installs is pretty minimal21:22
noonedeadpunkit's kinda positioned as more secuure, just because distro doe care about all package upgrades, but as consequnece, if you don't manage your own repo mirrors, you can't get reproducible environment21:23
cringdahlnoonedeadpunk: installing glance-common in the container satisfied ansible21:25
noonedeadpunkbut yeah, it's kinda slightly faster21:25
cringdahlthis is absolutely a lab environment, so I'll continue forward with distro for now, and if it gives me a working openstack, i'll let you all know :D21:26
noonedeadpunkit can, but on ubuntu or rocky21:26
noonedeadpunk(or might be centos by luck)21:27
noonedeadpunkalso, not all services are covered with distro method for now. So they might want to fallback21:27
noonedeadpunkon dabian I'd guess smth like that for glance would be needed for all services21:27
noonedeadpunk*debian21:28
noonedeadpunkbut you;ve already reported really good bugs for master - things we didn't tested but wanted to make right21:29
noonedeadpunkso kudos for that21:29
jrossercringdahl: the support for distro installs has been added by enthusiastic people close to those distros, we had this for suse in particular in the past21:29
jrosserbut unfortunately that has never really translated into long term support or maintainance21:30
jrosserand in the meantime the source installs are super solid and repeatable21:30
cringdahlunderstood21:31
jrosserand i guess for debian in particular, no-one has yet taken on sorting out distro installs21:31
cringdahlheh21:31
cringdahltypical. i try to do the easiest thing and it winds up being the hardest. story of my career.21:32
jrosserso we have no test coverage at all for debian/distro21:32
noonedeadpunkofftopic - we're getting plenty "Connection failure: The read operation timed out" on fetching a u-c in CI21:32
jrosser^ i looked at that a bit21:32
jrosserand got completely down the rabbit hole of why the upgrade jobs were on the wrong branch21:32
noonedeadpunkI can say - I have opendev activing weirdly locally as well21:32
jrosseri think it may be down to how we redefined the "base url" for the repos21:33
noonedeadpunkprobably I should have reported that to infra though21:33
noonedeadpunknah, I sometimes get timeouts in browser opening gitea21:33
jrosseroh yes i am getting that too21:33
noonedeadpunkand sometimes some issues with TLS negitiation21:33
noonedeadpunkso I think that what happens in ci as well21:34
jrosserand parts of the page rendering waaaaay behind others21:34
noonedeadpunk++21:34
jrosserbut anyway i think we broke the detection of repo url starting file:///21:35
jrosserand thats why we keep rraching out to u-c over https rather than off the disk21:35
noonedeadpunkbut it usually happens for upgrade jobs?21:46
noonedeadpunkon N-1 or N-2?21:46
noonedeadpunkas there we never use file://21:46
noonedeadpunkat least it's what I've spotted 21:47
jrosseryes - so thats why i was trying to understand how the reposwere configured for upgrades21:51
jrosserand i wanted to know if we made the correct override for the file:/// repo locations - but there were no logs21:51
jrosserso we had broken logging for upgrades21:52
jrosseralso upgrades on the wrong branches21:52
jrosserlogging was missing because of parallel, which we patched21:52
jrosseri thought we have been using file:/// for really many releases now21:53
noonedeadpunkI think we do. But we use file:// only when we "rely" on zuul repos, right?21:56
noonedeadpunkand on N-1 we just don't use cached repos right now21:56
jrosserlets look tomorrow :)21:57
noonedeadpunknot to accidentally checkout them by bootstrap-ansible or smth, which would vanish pulled by depends-on patches21:57
noonedeadpunk++21:57
noonedeadpunkyeah, midnight here :D21:57

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!