Monday, 2026-02-16

noonedeadpunkdamiandabrowski: can you check https://review.opendev.org/c/openstack/ansible-config_template/+/948915 (and the whole chain) to unblock 2.19 patches?09:20
damiandabrowskisure thing, will do that in a moment09:21
gokhanihello Folks, By default, the MariaDB backend configuration for HAProxy in OSA defines one node as the primary writer and the remaining nodes as backup. 09:25
gokhaniwhen the primary node goes down, the OpenStack services lose connectivity to the database because the backup nodes are not automatically promoted to active status in HAProxy. The only way we can restore the services is by manually removing the backup keyword from the config and reloading HAProxy.09:25
gokhaniIs there a move towards using a more intelligent SQL proxy (like ProxySQL) to handle this, or is there a way to make the current HAProxy-based default more resilient?09:26
gokhaniHow does the we handle this in production? Should we be using option allbackups or a different balance strategy (like first) to ensure that one of the backup nodes takes over automatically?09:27
gokhanithanks noonedeadpunk, I haven't tried yet using signed cookies. 09:28
noonedeadpunkwait, what?09:29
noonedeadpunkbackups are becomming immeditely in use when current active is marked as down or for maintenance09:29
gokhaniserver mgmt01 10.x.x.1:3306 check port 9200 inter 1200009:30
gokhaniserver mgmt02 10.x.x.2:3306 check port 9200 inter 12000 backup09:30
gokhanihaproxy config is like that: 09:30
gokhanimay be I need to retest this. 09:31
noonedeadpunkhttps://docs.haproxy.org/3.2/configuration.html#5.2-backup09:31
noonedeadpunkso failover must be pretty much atuomatical09:32
gokhaniIn my test it is failed I will test again. may be problem is specific to my environment. 09:34
noonedeadpunkwe never had to worry about this part tbh09:48
noonedeadpunkit works always quite nicely09:48
noonedeadpunkbut when you check the status of backends - do you see that they are all up?09:49
noonedeadpunkas it could be smth related to allowed subnets to accept conection from09:49
noonedeadpunkie - galera_monitoring_allowed_source09:51
noonedeadpunkas if haproxy is coming from unexpected address - it might be the issue, as then it maybe be not allowed to talk to mariadb09:51
noonedeadpunkhttps://opendev.org/openstack/openstack-ansible/src/branch/master/inventory/group_vars/galera_all.yml#L33-L3909:52
noonedeadpunkand it can be if keepalived has /24 VIP instead of /32 for isntance09:52
opendevreviewMerged openstack/openstack-ansible-openstack_hosts master: Add example of installation for user defined extra packages  https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/97286509:56
gokhaninoonedeadpunk: thanks for detailed explanation. before test I haven't checked backend status.  I have seen this issue only one of my environment. ı thought that this issue can happen in all environment but this is not true. I have tested this in different env it is working as you said. I am trying to find my env specific problem. 10:07
opendevreviewMerged openstack/openstack-ansible-lxc_container_create master: Use full service name in task name  https://review.opendev.org/c/openstack/openstack-ansible-lxc_container_create/+/97278710:37
noonedeadpunkhm, our gates look completely broken on horion setup right now11:22
noonedeadpunkok, so that's reproducible failure and related to setuptools somehow...12:17
noonedeadpunkhttps://paste.openstack.org/show/bIk1UwHEazI9bjgqsCSe/12:18
noonedeadpunkNot really getting why/how new setuptools getting in...12:44
noonedeadpunklooks like its pulled by some pyproject.toml or smth12:44
noonedeadpunkas in the venv and requireents it\s setuptools==80.10.212:45
noonedeadpunkok, found it...13:18
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build master: Cleanup environment on wheel build failure  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/97696713:26
noonedeadpunkso we have 2 ways to approach this13:30
noonedeadpunk1. --no-build-isolation and then ensure that pbr is installed together with pip, wheels, setuptools13:30
noonedeadpunk2. --build-constraint global-requirement-pins.txt13:31
noonedeadpunkfor the first case concern is about non-OSA deployments, as we don't have list of build requirements configurable so far13:32
noonedeadpunkfor the second case conern is that pbr is not in the global-requirement-pins.txt, and pbr is managed in upper-constraints13:33
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build master: Do not rely on build isolation  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/97697313:58
noonedeadpunkI'm kinda on the fence with this ^13:59
noonedeadpunklike it feels there's an opportunity to simplify things a lot13:59
noonedeadpunkby actually going a different way and using --build-constraint instead13:59
noonedeadpunkthough I'd assume using build isolation might take more time to execute14:00
noonedeadpunkand I can't come up with decent enough simplification to justify that14:02
opendevreviewAndrew Bonney proposed openstack/openstack-ansible master: Migrate k8s cluster from osa ops into main tree  https://review.opendev.org/c/openstack/openstack-ansible/+/97527714:43
opendevreviewDmitriy Rabotyagov proposed openstack/ansible-role-python_venv_build master: Cleanup environment on wheel build failure  https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/97696715:42
jrosseri think that this has blown up our horizon builds https://github.com/openstack/requirements/commit/c43ee322efb5bfb5cafc633c80d12d9c009b30da21:59
jrosserXStatic-Angular-Schema-Form in particular22:00

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