| opendevreview | Michal Nasiadka proposed openstack/kayobe master: Stop replacing dashes with underscores for Kolla interfaces https://review.opendev.org/c/openstack/kayobe/+/922480 | 07:00 |
|---|---|---|
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: Stop replacing dashes with underscores for Kolla interfaces https://review.opendev.org/c/openstack/kayobe/+/922480 | 07:16 |
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: Stop replacing dashes with underscores for Kolla interfaces https://review.opendev.org/c/openstack/kayobe/+/922480 | 07:17 |
| mnasiadka | good morning | 07:29 |
| mnasiadka | frickler: https://review.opendev.org/c/openstack/kolla-ansible/+/922478 - if you could have a look - I stumbled upon that in my $downstream deployment :) | 07:29 |
| SvenKieske | morning | 07:34 |
| SvenKieske | mhm, doesn't ansible replace dashes anymore with underscores or is it just different in the facts module? https://bugs.launchpad.net/kolla-ansible/+bug/1927357 | 07:36 |
| SvenKieske | ah, a bug is linked, should read that first I guess | 07:36 |
| SvenKieske | mhm, this sounds like a good workaround, but also like a bug in upstream ansible, no? | 07:37 |
| mnasiadka | no | 07:38 |
| mnasiadka | they claim it's how python works, and they don't give a shit | 07:38 |
| mnasiadka | :) | 07:38 |
| SvenKieske | lol, have a link for my entertainment? :) | 07:38 |
| mnasiadka | can't find it right now | 07:41 |
| mnasiadka | but it's been like this for years | 07:41 |
| SvenKieske | I know about the general issue with dashes, but it seems new to me that this differs across ansible. I thought it was the same everywhere. | 07:48 |
| mnasiadka | I just filled out the PTG form, it's going to take place on October 21-25, 2024 | 08:08 |
| opendevreview | Mark Goddard proposed openstack/ansible-collection-kolla master: Add stats callback plugin https://review.opendev.org/c/openstack/ansible-collection-kolla/+/910347 | 08:24 |
| SvenKieske | I think frickler spoilered the date already some weeks ago (the meeting before the last meeting afaik) :D | 08:25 |
| opendevreview | Merged openstack/kolla-ansible stable/2023.1: Skyline: Fix incorrect keystone port https://review.opendev.org/c/openstack/kolla-ansible/+/922305 | 08:28 |
| opendevreview | Merged openstack/kolla-ansible stable/2024.1: Skyline: Fix incorrect keystone port https://review.opendev.org/c/openstack/kolla-ansible/+/922303 | 08:35 |
| opendevreview | Merged openstack/kolla-ansible stable/2023.2: Skyline: Fix incorrect keystone port https://review.opendev.org/c/openstack/kolla-ansible/+/922304 | 08:52 |
| opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: Fix prechecks for interfaces with dashes https://review.opendev.org/c/openstack/kolla-ansible/+/922478 | 09:01 |
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: Stop replacing dashes with underscores for Kolla interfaces https://review.opendev.org/c/openstack/kayobe/+/922480 | 09:05 |
| opendevreview | Gaël THEROND proposed openstack/kolla-ansible master: Add new hardware prometheus exporter: https://review.opendev.org/c/openstack/kolla-ansible/+/922211 | 09:22 |
| opendevreview | Gaël THEROND proposed openstack/kolla-ansible master: Add new hardware prometheus exporter: https://review.opendev.org/c/openstack/kolla-ansible/+/922211 | 09:23 |
| opendevreview | Doug Szumski proposed openstack/kolla-ansible master: CI: test interface names with dashes https://review.opendev.org/c/openstack/kolla-ansible/+/794545 | 09:45 |
| opendevreview | Bartosz Bezak proposed openstack/kolla master: add kayobe to release management doc's Launchpad admin section https://review.opendev.org/c/openstack/kolla/+/922593 | 09:49 |
| opendevreview | Matt Crees proposed openstack/kolla stable/2023.2: Move apt_prefs pins to respective images https://review.opendev.org/c/openstack/kolla/+/922605 | 10:22 |
| opendevreview | Matt Crees proposed openstack/kolla stable/2023.2: Move apt_prefs pins to respective images https://review.opendev.org/c/openstack/kolla/+/922605 | 10:23 |
| srdemircan | Hi everyone, | 10:25 |
| srdemircan | I’m trying to deploy baremetal nodes with ironic. I have configured ironic by following kolla-ansible's ironic guide. Somehow I could not deploy a node with default configurations. | 10:25 |
| srdemircan | I can successfully register and inspect(with both redfish and inspector interfaces) my baremetal node. But when I try to deploy, ironic_python_agent try to send collected node information to inspector service(to /v1/continue endpoint) and it fails because inspector’s node_cache is empty. | 10:25 |
| srdemircan | I can not find what I am missing. Do you have any idea? | 10:25 |
| opendevreview | Matt Crees proposed openstack/kolla-ansible stable/2023.2: RMQ: enable all stable feature flags at once https://review.opendev.org/c/openstack/kolla-ansible/+/922606 | 10:26 |
| opendevreview | Matt Crees proposed openstack/kolla-ansible stable/2023.2: RMQ: enable all stable feature flags at once https://review.opendev.org/c/openstack/kolla-ansible/+/922606 | 10:27 |
| opendevreview | Matt Crees proposed openstack/kolla-ansible stable/2024.1: RMQ: enable all stable feature flags at once https://review.opendev.org/c/openstack/kolla-ansible/+/922607 | 10:27 |
| jheikkin | Hi, I am upgrading all-in-one kolla-ansible installation in a VM. I am getting strange dependency failure on TASK [prechecks : Checking dbus-python package] I have updated Ansible version and run kolla-ansible install-deps. So I do not understand why dbus-python is missing. | 10:57 |
| frickler | jheikkin: can you show the full error on paste.opendev.org? what versions of kolla-ansible are you upgrading from and to? on which OS+version? | 10:59 |
| opendevreview | Victor Chembaev proposed openstack/kolla-ansible master: Fix kolla systemd unit template to prevent restart all kolla services with docker.service restart https://review.opendev.org/c/openstack/kolla-ansible/+/918639 | 11:03 |
| jheikkin | Here is a paste https://paste.opendev.org/show/bkmr34sJNDUCpBUKvRou/ I do not recall which version I have, is there way to check it? the base OS is debian-bookworm and I run on podman containers | 11:04 |
| jheikkin | I am upgrading to latest release using the instructions on kolla-ansible official documentation | 11:05 |
| kevko | jheikkin: it should fail if your don't have dbus on remote managing node ... | 11:13 |
| kevko | jheikkin: i would say that python3-dbus and dbus is installed in OS by default ...can u verify with dpkg -l | grep -i dbus .... ? | 11:14 |
| jheikkin | Yes, dbus is installed in os | 11:18 |
| jheikkin | but this is a failing python module. Anyway I can also manually install the module in virtualenv and see if this allows me to move on | 11:19 |
| PrzemekK | jheikkin: did You run precheck ? openstack versions show You cant skip more than 2 version in SLURP | 11:20 |
| SvenKieske | jheikkin: did you verify python3-dbus, or just dbus? these are not the same thing! | 11:22 |
| SvenKieske | https://packages.debian.org/bookworm/dbus vs https://packages.debian.org/bookworm/python3-dbus | 11:22 |
| jheikkin | I do not have python3-dbus installed | 11:22 |
| jheikkin | it was not in the requirements on the all-in-one installation either | 11:22 |
| SvenKieske | you need python3-dbus, apparently, I wonder though why it's not in our requirements.txt if we need it? | 11:22 |
| SvenKieske | ok, it's "only" needed for baremetal deployment, it seems. | 11:23 |
| SvenKieske | https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/prechecks/tasks/package_checks.yml#L12 | 11:24 |
| jheikkin | So I edit the inventory and remove everything from baremetal group? | 11:24 |
| SvenKieske | no, if you want to deploy baremetal you need that group I guess. you just need to install python3-dbus on your hosts. | 11:24 |
| SvenKieske | I'm just wondering if we can't fix this on the kolla side, this seems rather unfortunate. | 11:25 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: [CI] Force config drive for ipv6 jobs https://review.opendev.org/c/openstack/kolla-ansible/+/914185 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: [CI] Trust kolla generated CA cert https://review.opendev.org/c/openstack/kolla-ansible/+/922559 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: [CI] Fix swift disk preparation https://review.opendev.org/c/openstack/kolla-ansible/+/913942 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Bash replacement https://review.opendev.org/c/openstack/kolla-ansible/+/920368 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Add testing project - rally https://review.opendev.org/c/openstack/kolla-ansible/+/922462 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: [CI] Rally tests and tasks https://review.opendev.org/c/openstack/kolla-ansible/+/913728 | 11:26 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: [DNM] Try to turn on swift tempest smoke tests https://review.opendev.org/c/openstack/kolla-ansible/+/914411 | 11:26 |
| jheikkin | I am just deploying a PoC in a VM. But when I do this following the instructions on documentation, it should mention that baremetal group needs to be left empty. Now it is not mentioned | 11:26 |
| kevko | jheikkin: python3-dbus should be requirements of dbus | 11:26 |
| SvenKieske | kevko: it's not, at least not in bookworm: https://packages.debian.org/bookworm/dbus | 11:27 |
| SvenKieske | I also don't see why it should, it's just python3 language bindings for dbus, to make interaction with dbus easier from python3, not needed for dbus itself at all? | 11:28 |
| PrzemekK | kolla-ansible-stable-2023.2\ansible\roles\prechecks\tasks\package_checks.yml (4 hits) Line 12: - name: Checking dbus-python package Line 13: command: "{{ ansible_facts.python.executable }} -c \"import dbus\"" Line 14: register: dbus_present Line 17: failed_when: dbus_present is failed | 11:29 |
| SvenKieske | PrzemekK: yeah I already linked to that line above, the github link :) | 11:29 |
| kevko | SvenKieske: well, but this is bug of kolla-ansible or ansible-collections-kolla which should install this package ... as it's installing python3-docker | 11:31 |
| kevko | for example | 11:31 |
| jheikkin | hmm | 11:31 |
| jheikkin | I think this could be I need to pass right python interpreter | 11:31 |
| jheikkin | In the error it says "cmd": ["/usr/bin/python3", "-c", "import dbus" | 11:32 |
| SvenKieske | kevko: but this is a package only needed for certain roles, so I can see why it was not added, then again I would also say it would be nice to include it | 11:32 |
| jheikkin | so this package is actually present in my kolla-ansible venv | 11:32 |
| PrzemekK | there is bug for that https://bugs.launchpad.net/kolla-ansible/+bug/2021585 | 11:32 |
| SvenKieske | ah | 11:32 |
| kevko | SvenKieske: joking ? :D | 11:33 |
| kevko | SvenKieske: ./ansible/module_utils/kolla_systemd_worker.py:import dbus <<<< | 11:33 |
| kevko | SvenKieske: it's kolla_systemd_worker ...so it's the main brick of kolla-ansible ..crucial dependency needed :D | 11:33 |
| SvenKieske | kevko: I was just going by the precheck, which only runs if you have hosts in "baremetal" group | 11:33 |
| SvenKieske | ok, then we need to fix that, agreed | 11:33 |
| SvenKieske | don't we even have simple import test that catches this? something feels off about this.. | 11:34 |
| SvenKieske | it's at least not in requirements.txt, is it maybe in global requirements? or just in our CI runners already installed? | 11:35 |
| PrzemekK | Bug #2021585 reported by Stefan on 2023-05-30 :D | 11:36 |
| kevko | SvenKieske: w8 a minute | 11:42 |
| kevko | SvenKieske: BUT - it's actually egg or chicken question :) | 11:43 |
| frickler | jheikkin: just being curious: how did you install your bookworm vm, from the official debian cloud image or some other way? | 11:43 |
| kevko | SvenKieske: does precheck report that i am missing python3-dbus or should bootstrap via ansible-collections-kolla install it | 11:44 |
| kevko | I think it should be installed in bootstrap - so add to ansible-collections-kolla to docker role | 11:46 |
| jheikkin | frickler: I think I used an ISO image from debian web site. I did not use a cloud image for the VM. | 11:50 |
| opendevreview | Michal Arbet proposed openstack/ansible-collection-kolla master: Add installation of dbus package https://review.opendev.org/c/openstack/ansible-collection-kolla/+/922614 | 11:52 |
| kevko | jheikkin: go to your home and apply patch for ansible-collection-kolla ^^ ...run bootstrap ...run prechecks again | 11:58 |
| SvenKieske | kevko: but why to docker role? now you need to install it in both podman and docker role. well better then nothing I guess | 11:58 |
| kevko | SvenKieske: i agree that it's maybe not ideal placement for installation as it has connection with systemd not docker/podman .... yeah you are right ... but i know/rememeber that there is mechanism for package installation ...i mean that dance with venv or not venv ...bookworm or others ... etc ... and on the end ..it's dependency for kolla | 12:03 |
| kevko | systemd worker ..which has connection to kolla docker/podman worker .. so i feel that it is not ideal ...but actually not bad placement on the end ..... | 12:03 |
| tis_at_teuto | Hi there, i have a question regarding a change-request. I made a git review https://review.opendev.org/c/openstack/kolla-ansible/+/922391 and the change was verified last week. But now i was wondering what comes next. Is there anything i should do to get progress in there? Thanks and regards. | 12:03 |
| jheikkin | I will likely reinstall the VM from scratch. I wanted to test the upgrade process but I think I was too many versions behind. I originally created the VM and did all-in-one in March this year. But I did not have this issue then - otherwise I'd have the dbus-python installed I guess. | 12:03 |
| kevko | tis_at_teuto: please, user uppercase for commit message ...and then i am ok with that review | 12:06 |
| kevko | jheikkin: yes, but we added systemd wrapper ... so it's new dependency | 12:07 |
| kevko | jheikkin: or ...two years :D | 12:07 |
| jheikkin | kevko: I installed the vm and pulled latest kolla code somewhere in March 2024. Anyhow I will do fresh install to another VM and see if I hit the same issue. | 12:09 |
| opendevreview | Tino Schmeier proposed openstack/kolla-ansible master: Use template instead of copy for prometheus-alert-rules https://review.opendev.org/c/openstack/kolla-ansible/+/922391 | 12:12 |
| tis_at_teuto | kevko: Thanks, i've updated the commit-message. | 12:16 |
| kevko | jheikkin: you will hit the same issue :) | 12:19 |
| kevko | tis_at_teuto: +2 from me as it's trivial | 12:21 |
| kevko | hmm, we should clean kolla reviews :) | 12:23 |
| kevko | i mean, abandon what should be abandoned ...review what should be reviewed ..etc | 12:24 |
| SvenKieske | kevko: I made a scan with a tool called deptry (https://github.com/fpgmaas/deptry); I also made a shot at integrating it with tox tests, but there are some challenges, regardless, found some more missing imports: https://paste.opendev.org/show/byH6Il1bC1dfT61Bh4D1/ | 12:45 |
| opendevreview | Sven Kieske proposed openstack/kolla-ansible master: refactor requirements.txt https://review.opendev.org/c/openstack/kolla-ansible/+/922617 | 12:52 |
| opendevreview | Sven Kieske proposed openstack/kolla-ansible master: add missing license for hvac library https://review.opendev.org/c/openstack/kolla-ansible/+/922618 | 12:55 |
| kevko | SvenKieske: libvirt dependency is only for vagrant ... (honestly i really don't know if anyone is using vagrant :D ) | 12:56 |
| SvenKieske | sure, but distutils is there | 12:57 |
| opendevreview | Sven Kieske proposed openstack/kolla-ansible master: add missing distutils requirements https://review.opendev.org/c/openstack/kolla-ansible/+/922619 | 12:59 |
| kevko | SvenKieske: yes, but distutils is installed in every linux distro as part of standard preinstalled system-wide python installation | 13:00 |
| kevko | SvenKieske: so you can be sure that distutils is installed and you want to have distro packaged version ..not the pip one | 13:01 |
| SvenKieske | mhm, are you sure? | 13:03 |
| kevko | SvenKieske: 100 % | 13:10 |
| kevko | SvenKieske: but, distutils is deprecated and will be removed | 13:10 |
| sylvr | Hello! I'm trying to provision my overcloud, but I got an error saying the user defined deployment image is missing, I didn't remembering putting that in my config, do I need to create my own qcow2 files to provision my overcloud or kayobe can create those files ? | 13:16 |
| sylvr | My understanding is that `kayobe overcloud deployment image build` should do the trick ? | 13:19 |
| opendevreview | Michal Arbet proposed openstack/kolla-ansible master: Remove usage of distutils https://review.opendev.org/c/openstack/kolla-ansible/+/922621 | 13:19 |
| kevko | SvenKieske: ^^ | 13:19 |
| sylvr | sylvr: uuh it was `kayobe overcloud host image build` | 13:23 |
| SvenKieske | kevko: just wanted to ask how we handle the deprecation of distutils :D | 13:35 |
| kevko | SvenKieske: ^^ :) ...there is also need to rewrite easy_install stuff in pbr ...but it's not kolla | 13:38 |
| kevko | not our responsibility | 13:40 |
| sylvr | Hello ! How can I stop the following error from occuring while running `kayobe overcloud provision` : Deploy step deploy.prepare_instance_boot failed: Failed to install a bootloader when deploying node ffcc09d8-ede5-4c2a-8e2b-c0056d22e70f: No EFI | 14:09 |
| sylvr | partition could be detected on device /dev/sda and EFI partition UUID has not been recorded during deployment (which is often the case for whole disk images). Are you usi | 14:09 |
| sylvr | ng a UEFI-compatible image? (logs taken from the node using Ironic) | 14:09 |
| jovial | sylvr - If building with DIB, you need an element like block-device-efi to have an EFI compatible image | 14:10 |
| jovial | its either that or boot in legacy mode ;-) | 14:10 |
| sylvr | jovial: in bifrost.yml the parameter "kolla_bifrost_dib_elements_default" ? | 14:12 |
| jovial | slyvr: I think you want it in here: https://github.com/openstack/kayobe-config/blob/master/etc/kayobe/overcloud-dib.yml#L37 | 14:17 |
| jovial | See: https://docs.openstack.org/kayobe/latest/configuration/reference/overcloud-dib.html | 14:18 |
| sylvr | oh yes that makes much more sense ! thanks | 14:18 |
| jovial | Worth knowing that there is also an LVM variant: https://docs.openstack.org/diskimage-builder/latest/elements/block-device-efi-lvm/README.html | 14:22 |
| opendevreview | Victor Chembaev proposed openstack/kolla-ansible master: Fix octavia-interface timeout https://review.opendev.org/c/openstack/kolla-ansible/+/920377 | 14:23 |
| opendevreview | Victor Chembaev proposed openstack/kolla-ansible master: Fix kolla-ansible systemd restart behaviour https://review.opendev.org/c/openstack/kolla-ansible/+/918639 | 14:25 |
| kevko | SvenKieske: my first custom defined rally task ...just create volume ... check it ... save as html >> https://paste.openstack.org/show/bdkDEdDQEqch9Y829udQ/ | 14:30 |
| kevko | SvenKieske: this will simple replace all openstack calls and tests in bashes....very elegant and simple :) | 14:30 |
| SvenKieske | kevko: looks nice :) | 14:33 |
| kevko | SvenKieske: cool right ? | 14:40 |
| kevko | SvenKieske: cool is that you can for example start vm ..then restart libvirt ..restart mariadb ..restart rabbit ...whatever ..and then run another VM ..as a test ... described in simple yaml ...and you will get result :) | 14:40 |
| SvenKieske | and you can use all those preexisting tempest scenario tests, no? :) | 14:41 |
| kevko | SvenKieske: you can use rally as wrapper to tempest ..you can exec smoke tests only ..or regexp .. so there is a question if we want to run all thousands of tests which tempest has ... Or use rally to define our own yamls to test our specific scenarios | 14:46 |
| kevko | This report is report for my own task I defined to yaml | 14:47 |
| kevko | Or combination | 14:48 |
| SvenKieske | I don't think it's reasonable to run all those thousands of tempest tests, but there will be a good subset that extends our test coverage for important things. | 14:49 |
| kevko | Yep | 14:50 |
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: arista-switch: Fix eos_config call https://review.opendev.org/c/openstack/kayobe/+/922631 | 15:00 |
| opendevreview | Michal Nasiadka proposed openstack/kayobe master: arista-switch: Fix eos_config call https://review.opendev.org/c/openstack/kayobe/+/922631 | 15:02 |
| sylvr | jovial: do you know if having the management network and the introspection network on the same network might cause an issue ? my nodes are active, but it doesn't seems like they're available through ssh.. | 15:08 |
| jovial | sylvr: Should be OK. Could be that cloud init failed to run for some reason? You really need something like a devuser to debug this kind of issue: https://docs.openstack.org/diskimage-builder/latest/elements/devuser/README.html | 15:11 |
| sylvr | okay ! will do | 15:13 |
| jovial | slyvr: You might need to explitly enable ConfigDrive as a datasource. Like this: https://github.com/stackhpc/stackhpc-kayobe-config/blob/stackhpc/2023.1/etc/kayobe/stackhpc-overcloud-dib.yml#L41 | 15:19 |
| jovial | With the cloud-init-datasources element | 15:20 |
| jovial | If you find that is true, could you open a bug against kayobe? Really the default config should create a working image out of the box. | 15:24 |
| sylvr | jovial: got access to the nodes trhough IPMI and logged in as devuser, no IP are configured by default on the node | 15:45 |
| sylvr | jovial: I think it is by default but I'll add it to the extras just to be sure, going to rebuild and re-provision to check if it changes something | 15:46 |
| jovial | slyvr: Oh yeah, I see it in the defaults. I'd recommend checking the cloud init logs in /var/log/cloud-init.log | 15:49 |
| sylvr | jovial: I checked for this file on kayobe-control-host/seed-bifrost and on one of the node and I couldn't find it | 16:06 |
| jovial | sylvr: You need to check on the host you are provisioning via the devuser | 16:10 |
| sylvr | jovial: I checked, nothing | 16:11 |
| sylvr | well, not nothing, but no cloud-init.log in /var/log | 16:12 |
| jovial | slyvr: Anything in the journal? journalctl -u cloud-init or similar? | 16:16 |
| jovial | And what is the status of cloud-init.service? | 16:16 |
| sylvr | jovial: no entries for journalctl -u cloud-init and no cloud-init.service | 16:18 |
| jovial | Is the cloud-init package installed? | 16:18 |
| sylvr | on the node I try to provide ? no | 16:20 |
| jovial | Oh... Try adding the cloud-init element | 16:20 |
| sylvr | rebuilding the images, did I miss to add it or is it supposed to be by default ? | 16:23 |
| sylvr | I may leave soon, I'll probably send an update tomorrow | 16:23 |
| jovial | sylvr: Well it seems like cloud-init-datasources doesn't create a dependency on cloud-init. I guess we should add cloud-init to the default elements in kayobe. | 16:24 |
| sylvr | jovial: okok, thanks for you help and I'll keep you in touch | 16:25 |
| jovial | slyvr: No worries, this is all useful feedback :) | 16:27 |
| sylvr | jovial: yep that fixed the issue ! now running kayobe overcloud host configure | 16:39 |
| jovial | sylvr: Glad to hear it. Fancy submitting a patch to upstream kayobe to add it to the defaults: https://github.com/openstack/kayobe/blob/master/ansible/inventory/group_vars/all/overcloud-dib#L38? | 16:41 |
| sylvr | jovial: yep, I'd like that ! is it okay if I do that tomorrow ? | 16:43 |
| jovial | slyvr: Yeah, no problem - thanks :) | 16:44 |
| sylvr | jovial: awesome, I took notes, I'll keep you in touch tomorrow ! thanks again ! | 16:45 |
| opendevreview | Victor Chembaev proposed openstack/kolla-ansible master: Fix octavia-interface timeout https://review.opendev.org/c/openstack/kolla-ansible/+/920377 | 18:05 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!