Monday, 2024-09-02

opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Use haproxy_install playbook from openstack-ansible-plugins repo  https://review.opendev.org/c/openstack/openstack-ansible/+/92416809:10
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_octavia stable/2024.1: Define ovn provider agent when OVN is used  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/92771809:12
noonedeadpunkgood morning09:12
jrossero/ morning09:12
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/2024.1: Remove the get_md5 parameter from ansible stat tasks  https://review.opendev.org/c/openstack/openstack-ansible/+/92771909:14
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/2023.2: Remove the get_md5 parameter from ansible stat tasks  https://review.opendev.org/c/openstack/openstack-ansible/+/92772009:14
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible stable/2023.1: Remove the get_md5 parameter from ansible stat tasks  https://review.opendev.org/c/openstack/openstack-ansible/+/92772109:15
opendevreviewAndrew Bonney proposed openstack/openstack-ansible-os_ceilometer master: Add support for Magnum notifications  https://review.opendev.org/c/openstack/openstack-ansible-os_ceilometer/+/92772409:43
noonedeadpunkandrewbonney: can you write a reno for ^ ?09:44
andrewbonneyAh yes, sure09:45
opendevreviewAndrew Bonney proposed openstack/openstack-ansible-os_ceilometer master: Add support for Magnum notifications  https://review.opendev.org/c/openstack/openstack-ansible-os_ceilometer/+/92772409:48
noonedeadpunkIt would be also kinda nice to have that backported to 2024.1 imo09:49
opendevreviewMerged openstack/openstack-ansible master: [doc] Add documentation on spawning HAProxy inside LXC  https://review.opendev.org/c/openstack/openstack-ansible/+/92435310:13
noonedeadpunkandrewbonney: sorry, I have forgot again about octavia keypair issue you've reported. But now I can't find the bug report either....10:22
noonedeadpunk(it's third time I'm about to look into that, I know)10:22
noonedeadpunkah, it's fixed with https://opendev.org/openstack/openstack-ansible-plugins/commit/be620d3b3546d3a7a27c7d8d29803ac49c864142 ?10:23
noonedeadpunkyeah, it must be10:24
andrewbonneyTo be honest I've forgotten about it too. It certainly looks like we're using that patch locally10:26
andrewbonneyIt looks like we may have changed octavia_ssh_key_dir locally. Not sure if perhaps the default wouldn't work in the case of an upgrade10:28
andrewbonneyPerhaps with that patch in place it's fine actually. It was perhaps just an issue before the deploy host fix10:30
noonedeadpunkyeah, probably. and we had just a different issue here with the same thing kinda10:44
noonedeadpunkbut you patch worked nicely :)10:44
opendevreviewMerged openstack/openstack-ansible-os_octavia stable/2023.2: Ensure Octavia communicates with Neutron through internal URL  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/92723310:56
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_octavia master: Provide better flexability for SSH keypair options  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/92772811:00
opendevreviewMerged openstack/openstack-ansible-ops master: mcapi_proxy: allow overriding of systemd service environment  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92688911:01
opendevreviewMerged openstack/openstack-ansible-ops master: Allow mcapi proxy git sources and python package versions to be overridden  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92640911:02
gokhanhello folks after the antelope upgrade we can not create images with glance, Error logs are: "glance_store.exceptions.StoreAddDisabled: Configuration for store failed. Adding images to this store is disabled." these are detailed logs https://paste.openstack.org/show/bjNCxjh6Km9Jkula3FKA/.  I am using nfs for glance images in this environment. Have you seen this issue ?11:04
opendevreviewMerged openstack/openstack-ansible-ops master: Add variables and hook for high-availability k8s control plane test  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92317311:12
grauzikasHello, im trying to make work magnum and have issues there. The issue is that heat doesnt provide to fedora-coreos certificate keys and inside fedora coreos i can see errors:11:13
grauzikashttps://paste.openstack.org/show/bBg7FijxjMK9EdjeZNNz/11:15
noonedeadpunkgokhan: and how does you glance.conf look like?11:15
noonedeadpunkgrauzikas: frankly - I have no idea if heat is capable of that even, given coreos design...11:16
noonedeadpunkbut if you're to use FQDN for public VIP and enable Let's Encrypt usage - I think you should not have issues with certificates there11:17
grauzikas*** is ip address of external vip. So i tryed to configure letsencrypt, but seems it configures only haproxy external side. Tryed to set some of tls opinions but also not worked. By searching on google i found that inside coreos openstack-ca.pem is  empty: https://paste.openstack.org/show/bxUxvRz2nQ62PhoKEosh/11:17
jrosseryou need to define openstack_ca_file in magnum.conf i think11:18
noonedeadpunkgrauzikas: oh, well, there're options to control that11:18
noonedeadpunkyeah, that11:18
noonedeadpunkor set `verify_ca: false` 11:19
jrosserletsecrypt is only for the external side, the internal side is not relevant for this11:19
grauzikashttps://storyboard.openstack.org/#!/story/201012411:19
jrosserit is the CA used by the magnum workload cluster when it calls back to the external API endpoint11:19
grauzikasbut this is for kolla ansible i mean this variable: openstack_ca_file11:20
jrosserthat is a config option for magnum11:20
gokhannoonedeadpunk, https://paste.openstack.org/show/bCerKFrXEFqCDEDkw05A/11:20
jrossergrauzikas: like the bug report there says, you need to configure openstack_ca_file - see https://docs.openstack.org/magnum/latest/configuration/sample-config.html11:21
noonedeadpunkgrauzikas: you can do like that I gueess https://paste.openstack.org/show/bbQHEpNCwOBo75YSbnys/11:22
noonedeadpunkin your user_variables.yml11:23
jrossermaybe we should add this as a default in the template11:23
jrosserbut with the heat driver there are just so many ways for this to go wrong (like using wrong endpoint blah blah)11:23
noonedeadpunkyeah. might make sense to add it indeed, though it's kinda just for dev setups rather then prods. As I hardly see any prod env with untrusted certificate anyway11:24
jrosserperhaps - an internal cloud with company CA would need it11:25
jrosserbut maybe thats a legitimate situation to use a manual override11:25
noonedeadpunkgokhan: hm, Im a bit confused why you're missing a [cinder] and [http] sections11:26
noonedeadpunkjrosser: and then you also don't want it to be ca-certificates I assume11:26
jrosserhttps://github.com/openstack/openstack-ansible-ops/blob/master/mcapi_vexxhost/playbooks/files/openstack_deploy/user_variables_z_magnum.yml#L2711:27
noonedeadpunkbut something way more specific11:27
noonedeadpunkwell. this proves the point that it makes sense to do this by default11:27
gokhannoonedeadpunk, there is no override for glance in user_variables. these are default settings. I only defined glance nfs client 11:32
noonedeadpunkok, yeah, on 2023.1 I have kinda same config, was comparing with 2024.1 accidnetally11:35
noonedeadpunkgokhan: I assume that you've already ensured that `glance` user can write to the NFS still? I guess I would try also to disable all extra backends (like cinder/file) if they're not used jsut to ensure it's file that's causing troubles11:39
noonedeadpunkie by setting `glance_additional_stores: []`11:40
noonedeadpunkas if you've re-setup OS during it's upgrade, it could be that now UID/GID of glance has changed, unless you've explicitly defined them11:40
gokhandrwxr-xr-x  2 nobody nogroup 65536 Jul 26 17:43 images 11:43
gokhannoonedeadpunk, all of the nodes uuid/gid are same 11:45
noonedeadpunkbut um. I'\m not sure glance user can write with 0755?11:46
gokhannoonedeadpunk, now I am trying wth glance user 11:48
noonedeadpunkas I don\t think that privilege escalation is gonna be used by glance11:48
gokhannoonedeadpunk, yes after changing its user to glance, it worked thanks. 11:49
gokhannoonedeadpunk, I have another question. how can we install multi region with osa? 11:49
noonedeadpunkyou'd need to have some overrides. I think that from OSA prespective these will be just 2 deployments (or better say, 2 openstack_deploy folders). But it kinda depends on the architecture more.11:51
noonedeadpunkas there's totally a possibility to have different regions as part of extra groups as well11:51
noonedeadpunkI kinda have some "example" here locally where I did multiregion with shared keystone11:52
gokhanthis is the first time I am trying to deploy multi region. 11:52
noonedeadpunkwhere each region was it's own openstack_deploy folder and keystone was a separate "region" from osa prespective11:52
gokhanI am also thinking with a shared keystone 11:52
noonedeadpunkas eventually, you'd need to have a different FQDNs (API endpoints) for each region11:53
noonedeadpunkthen both of these should talk to the same keystone 11:53
gokhanif it is possible can you share your overrides?11:53
noonedeadpunkbut it was quite complex (though interesting setup) I was going to document when have some time...11:54
noonedeadpunkwell, I did have tons of overrides but all due to different reasons, so I'd need some time to extract ones for multi-region setup11:56
noonedeadpunkas there were multiple AZs in each region as well11:56
noonedeadpunkand endpoints by path (ie cloud.com/identity)11:57
noonedeadpunkso this is atually how I wanted to do the keystone sharing: https://i.imgur.com/gngXklM.png11:57
noonedeadpunkwhere to maintain a separate mariadb cluster and keystone hosts from any of the existing regions11:59
gokhanthanks noonedeadpunk, keystone dbs will be seperate from other services dbs. instead of haproxy you prefer proxySQL12:01
noonedeadpunkActually, I'm looking at overrides now, and kinda main point there - is that neither of regions did have keystone defined in them12:01
noonedeadpunkso I had like /etc/openstack_deploy_region1, /etc/openstack_deploy_region2 and /etc/openstack_deploy_keystone12:01
* noonedeadpunk never finished proxysql part12:01
noonedeadpunkand then as part of /etc/openstack_deploy_keystone you include jsut keystone, memcahced and galera while other 2 conatian jsut everything except keystone12:02
noonedeadpunksince each had different public_vip (and thus endpoints) for regions I defined manually keystone_service_adminuri, keystone_service_internaluri and keystone_service_publicuri: https://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/all/keystone.yml12:04
noonedeadpunkthough I had to do a lot of hackery there in order to spawn keystone containers locally to these regions. and that part is kinda tricky12:05
noonedeadpunkso I wanted to re-use existing haproxy and controllers, so that each region was going to local to itself keystone only12:05
noonedeadpunkand only galera VMs were completely independent from regions12:05
noonedeadpunkso for `openstack_deploy_keystone` I defined just same controllers like that:12:06
grauzikassorry need to go away for a short time. so if i will set self provided cert it should work? and letsencrypt didnt helped because it is only for haproxy?12:09
opendevreviewMerged openstack/openstack-ansible-repo_server master: Remove references to lsync and rsync  https://review.opendev.org/c/openstack/openstack-ansible-repo_server/+/92725912:11
noonedeadpunkhttps://paste.openstack.org/show/brzpECoRijzjFryY3F7f/12:13
noonedeadpunkgrauzikas: let's encrypt should have helped. But it could be that the image just uses too old ca-certificates12:13
noonedeadpunkand let's encrypt changed it's root couple of times relatively recently12:14
noonedeadpunkbut also you could jsut disable CA verification in overrides as well12:14
noonedeadpunkgokhan: but in fact there're kinda more overrides to make... It's really tough to layout all nuances in IRC without showing drawings and without having any architecture in mind12:15
noonedeadpunkBut what I can totally tell is that osa is really flexible enough to support such crazy userstories12:15
grauzikasok will try again letsencrypt. and reinstall everything again. was trying various ways :) : https://paste.openstack.org/show/bAXJrgGZbmXGxzhKdWzA/12:17
gokhanthanks noonedeadpunk, thanks it seems ı got it. it is very benefical for me. I will try it.  If I have issues, I will share it with you :) 12:21
jrossergrauzikas: i think you created the overrides incorrectly for magnum openstack_ca_file there12:28
grauzikasyes yes i notices that, just spent a lot of time by figuring this out :)12:29
jrosseropenstack_ca_file is a setting in magnum.conf, not a variable for openstack-ansible12:29
noonedeadpunkI shared some sample paste above for this12:30
grauzikasbtw i have seen this somewhere, but cant find again. How i can append list of default packages for lxc containers? i want to add tools like net-tools, nano, wget, tcpdump - now all the time i need to install them after reinstall of system - and doing reinstall quite often while testing how OSA works12:30
grauzikasjrosser, nooonedeadpunk yes i already got this will try soon12:30
jrosserhere is how to add extra packages to the base container image https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaults/main.yml#L16512:31
jrosserthough you would need to update the base image, then delete/recreate and existing containers for that to take effect12:31
opendevreviewMerged openstack/openstack-ansible-os_neutron master: Ensure proper permissions for OVN Metadata service  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/92718312:32
jrosseryou can also set some packages here https://github.com/openstack/openstack-ansible-openstack_hosts/blob/master/defaults/main.yml#L14212:32
jrosserthose would be installed whenever the openstack_hosts role is run, which you could do for existing containers12:32
grauzikasand syntax “package1, packag2” or - package1 \n - package2 ? \n new line cant use in irc new lines :)12:44
noonedeadpunkit's a list, so new lines12:44
noonedeadpunksecond option :)12:44
grauzikasyes yes understud :) thanks12:44
opendevreviewMerged openstack/openstack-ansible-ops master: Add support for deploying mcapi control plane k8s on rocky linux  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92344713:01
opendevreviewMerged openstack/openstack-ansible master: Properly apply `always` tag to install_defaults  https://review.opendev.org/c/openstack/openstack-ansible/+/92493813:06
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-ops master: Revert "Ensure that python3-cryptography is present in k8s control plane hosts"  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92140013:47
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_octavia master: Provide better flexability for SSH keypair options  https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/92772813:51
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_magnum master: Define lock directory for oslo_concurrency  https://review.opendev.org/c/openstack/openstack-ansible-os_magnum/+/92169014:07
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Use infrastructure playbooks from openstack-ansible-plugins repo  https://review.opendev.org/c/openstack/openstack-ansible/+/92425314:09
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible master: Use hosts setup playbooks from openstack-ansible-plugins repo  https://review.opendev.org/c/openstack/openstack-ansible/+/92425914:11
opendevreviewMerged openstack/openstack-ansible-ops master: Add support for deploying mcapi control plane k8s on debian-12  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/92358615:00
jrossernoonedeadpunk: do we need to do anything about these? https://review.opendev.org/q/topic:%22remove-wsgi_scripts%2215:01
noonedeadpunkoh yes, we do15:02
noonedeadpunkcrap15:02
jrosserSHA bump time and see what breaks15:02
noonedeadpunkI totally missed that and thought it didn't make into the release15:03
noonedeadpunkAll breaks then....15:03
noonedeadpunkbasically this what nicely covers what we need to https://review.opendev.org/c/openstack/nova/+/902687/4/releasenotes/notes/add-nova-wsgi-module-3cc250a78fef7365.yaml#1915:04
noonedeadpunkand we should be able to do that before bump for some services15:04
opendevreviewMerged openstack/openstack-ansible master: Skip importing haproxy_service_config with no haproxy hosts  https://review.opendev.org/c/openstack/openstack-ansible/+/92430816:56
noonedeadpunkit seems these 2 things are completely borked now: https://opendev.org/openstack/openstack-ansible-os_neutron/src/branch/master/handlers/main.yml#L33-L7517:16
noonedeadpunkI don't really see any processes for `neutron-ns-meta` (as these are named differetly now)17:17
noonedeadpunk1. I'm really not sure what `pgrep neutron-ns-meta` should be catching - I don't see anything anywhere17:46
noonedeadpunk2. cat /sys/fs/cgroup/pids/neutron.slice/neutron-l3-agent.service/cgroup.procs does not exist anymore17:46
noonedeadpunkit should be /sys/fs/cgroup/neutron.slice/neutron-l3-agent.service/cgroup.procs I assume17:46
noonedeadpunkor at least depend on OS17:46
jrosserare those things breaking with a sha bump?19:09
noonedeadpunkno, not really. I just spotted plenty of atnelope processes on net nodes after upgrade to 2024.119:11
*** priteau_ is now known as priteau19:12
noonedeadpunkand issues with routers update...19:12
jrosserhrmm19:18
jrosseri wonder if that is something for the healthcheck playbook19:19
jrosserto test if there are any processes running from old version venvs19:19
noonedeadpunkwell it would mandate running such playbook then19:19
noonedeadpunkAnd I'd guess this would be quite specific to neutron with ovs/lxb due to our KillMode: process19:20
jrosseri was thinking that the upgrade jobs would catch it19:20
noonedeadpunkSo I guess I'd rather fixed handlers with commands that can result in success19:21
jrosserbut yes you're right, old type networking19:21
noonedeadpunk>  upgrade jobs would catch it - ah, that makes sense indeed19:21
noonedeadpunkI thought you was talking about moving handlers to a healthcheck playbook from neutron overall :D19:22
opendevreviewDmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron stable/2024.1: Ensure proper permissions for OVN Metadata service  https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/92776121:15

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