opendevreview | Merged openstack/openstack-ansible-openstack_hosts master: Manage apt repositores and keys using deb822_repository module https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/907434 | 09:28 |
---|---|---|
noonedeadpunk | morinings | 09:53 |
noonedeadpunk | would be nice if someone could take a look at https://review.opendev.org/q/topic:%22osa/apache_mpm_alignment%22 - as I wanan backport them to 2024.1 as well (except repo_server) | 09:54 |
noonedeadpunk | and yeah - horizon will be switched to mpm event from worker... Will write reno right away | 09:55 |
opendevreview | Dmitriy 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/+/929695 | 09:59 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible master: Add global release note for Apache MPM alignment https://review.opendev.org/c/openstack/openstack-ansible/+/930185 | 10:11 |
opendevreview | Merged openstack/openstack-ansible-os_neutron stable/2023.1: Use cgroupsv2 for L3 cleanup https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929003 | 10:14 |
opendevreview | Merged openstack/openstack-ansible-os_neutron stable/2023.2: Use cgroupsv2 for L3 cleanup https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929002 | 10:14 |
opendevreview | Merged openstack/openstack-ansible-os_neutron stable/2024.1: Use cgroupsv2 for L3 cleanup https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929001 | 10:14 |
opendevreview | Merged openstack/openstack-ansible-os_neutron stable/2023.2: Disable uWSGI usage by default https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929550 | 10:14 |
opendevreview | Merged openstack/openstack-ansible-os_neutron stable/2023.1: Disable uWSGI usage by default https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/929551 | 10:14 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron stable/2023.2: Do not kill ipsec on L3 cleanup https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/930186 | 10:14 |
opendevreview | Dmitriy Rabotyagov proposed openstack/openstack-ansible-os_neutron stable/2023.1: Do not kill ipsec on L3 cleanup https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/930187 | 10:15 |
opendevreview | Dmitriy Rabotyagov proposed 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/+/930188 | 10:15 |
opendevreview | Merged openstack/openstack-ansible-os_octavia stable/2024.1: Return `amphora` provider back https://review.opendev.org/c/openstack/openstack-ansible-os_octavia/+/928999 | 10:17 |
opendevreview | Dmitriy 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/+/928771 | 10:19 |
noonedeadpunk | and this is also quite good bugfix for centos: https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/929540 | 10:21 |
jrosser | should we add that to the base image for rh-like containers? | 10:39 |
noonedeadpunk | oh, that's a good point | 10:40 |
noonedeadpunk | maybe we should add all of these there ?:) | 10:41 |
noonedeadpunk | but well, frankly I'm not sure if that's needed "for real" anywhere except utility. | 10:41 |
noonedeadpunk | as what I saw (as well as reporters) that it was enough to install on utility | 10:42 |
noonedeadpunk | and it was used basically only by mysql collection | 10:42 |
noonedeadpunk | so probably having it everywhere is excessive, given that selinux in fact looks like disabled.... | 10:42 |
noonedeadpunk | but then smth apparently goes off for centos, as rocky doesn't need it yet anywhere... | 10:43 |
noonedeadpunk | so smth makes ansible think it needs selinux bindings for some modules | 10:43 |
gokhan | hello noonedeadpunk , I solved issue about masakari. the failure is bacause of disable_ipmi_check=false. it gets Failed to get params of ipmi RA error. after changing disable_ipmi_check from false to true it worked. | 12:58 |
gokhan | but if we are using pacemaker-corosync we also need https://review.opendev.org/c/openstack/masakari/+/788382 commit. because if nova compute service is actually is not down, it can not disable nova compute service. may be using consul instead of pacemaker-corosync is best choice. | 13:00 |
noonedeadpunk | oh, yes, totally, evacuate doesn't work if nova does't mark service as down. Though I'm not sure this patch is *needed* per say | 13:01 |
noonedeadpunk | as masakari has timeouts/retries from scratch to handle that | 13:02 |
noonedeadpunk | as I can recall even Train was working that way. So you can set amount of retries and sleep beteween timouts while masakari-engine will wait for nova to mark service as down | 13:03 |
noonedeadpunk | also hashicorp is not having opensource license, so this is smth we will not deploy I assume | 13:03 |
noonedeadpunk | though I guess there should be possibility to mark pacemaker as optional and deploy whatever user wants for cluster monitoring | 13:04 |
noonedeadpunk | if you'd ask me - I even not sure why there is no "native" driver, which would jsut check on nova service list and action on compute service going down in nova... | 13:05 |
noonedeadpunk | would make total sense for me... | 13:05 |
noonedeadpunk | but -ENOTIME | 13:05 |
gokhan | indeed this patch also handles timeouts and waiting for nova compute to be down, | 13:09 |
noonedeadpunk | there were waits even before | 13:09 |
noonedeadpunk | what this patch is doing - it's disabling timeouts if it detects that nova is already down | 13:10 |
noonedeadpunk | so it's more quality of life improvement then smth too crucial, imo | 13:10 |
gokhan | I also added eventlet sleep before disabling nova compute | 13:10 |
gokhan | I added there https://github.com/openstack/masakari/blob/02bf0d3ed792c27b60b9a559366fba95547bf6da/masakari/compute/nova.py#L152 | 13:11 |
jrosser | surprising failure across the board for noble here https://review.opendev.org/c/openstack/openstack-ansible/+/928771?tab=change-view-tab-header-zuul-results-summary | 14:11 |
mgariepy | we do not sync sources.list.d from host the hosts ? | 14:23 |
mgariepy | or the directory is really missing ? | 14:23 |
opendevreview | Merged openstack/openstack-ansible stable/2024.1: Verify OS for containers installation https://review.opendev.org/c/openstack/openstack-ansible/+/928589 | 14:49 |
noonedeadpunk | there was some patch for sources.list.d creation? | 15:58 |
noonedeadpunk | I can recall this being reported a week ago or so | 15:58 |
jrosser | i thought that was something i had to deal with inside the containers for sure | 15:59 |
noonedeadpunk | but these are metal, yeah | 15:59 |
jrosser | https://review.opendev.org/c/openstack/openstack-ansible-lxc_hosts/+/924309 | 15:59 |
noonedeadpunk | could be new image... | 15:59 |
jrosser | so maybe the same thing is true for the host | 15:59 |
noonedeadpunk | more "minimal" or smth | 15:59 |
noonedeadpunk | https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/929695? also failed today on same thing - was passing last week | 16:01 |
noonedeadpunk | ah, yes, you wrote that it is across the board | 16:01 |
WireLost | hi guys, is it possible to deploy Skyline with OSA master? | 18:19 |
jrosser | WireLost: it should be ok, yes | 19:07 |
WireLost | jrosser, is it enabled by default, or should I explicitly enable it somehow? | 19:32 |
jrosser | you need to enable it explicitly | 19:50 |
jrosser | the inventory contains the env.d definition for skyline already | 19:51 |
jrosser | https://github.com/openstack/openstack-ansible/blob/master/inventory/env.d/skyline.yml | 19:51 |
jrosser | so you would enable it in your openstack_user_config.yml with something like this https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_deploy/conf.d/skyline.yml.aio | 19:52 |
jrosser | just like the other services | 19:52 |
jrosser | there is of course a decision to make if you want to have horizon and skyline at the same time, which can be done, with caveats | 19:53 |
jrosser | or just one of them | 19:53 |
WireLost | thanks! | 20:51 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!