opendevreview | Merged openstack/kayobe master: switches: add flag to save configuration on Dell switches https://review.opendev.org/c/openstack/kayobe/+/862613 | 02:22 |
---|---|---|
opendevreview | Merged openstack/kayobe master: Install docker Python package in kolla venv https://review.opendev.org/c/openstack/kayobe/+/902282 | 04:08 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: fluentd: Fix getting podman labels https://review.opendev.org/c/openstack/kolla-ansible/+/902352 | 06:52 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible master: magnum: support kubeconfig configuration file https://review.opendev.org/c/openstack/kolla-ansible/+/896292 | 07:15 |
mnasiadka | ok then, last two patches for k-a ^^ | 07:16 |
SvenKieske | o/ | 08:07 |
SvenKieske | last two patches..so far! /homer_meme | 08:07 |
SvenKieske | mnasiadka: the kubeconfig check in magnum should be optional/allowed to fail, no? :) | 08:10 |
mnasiadka | SvenKieske: if the file isn't there, we don't template it in config.json | 08:31 |
mnasiadka | and don't copy it | 08:31 |
mnasiadka | so it should be fine | 08:31 |
SvenKieske | ok | 08:32 |
mnasiadka | just replied in gerrit | 08:32 |
mnasiadka | ok, kolla seems to be ready, let me update the release patch | 08:38 |
mnasiadka | and kolla-ansible in a few hours after those two will merge | 08:40 |
SvenKieske | nice :) | 08:43 |
priteau | Anyone able to approve this trivial backport? https://review.opendev.org/c/openstack/kolla-ansible/+/901715 | 08:59 |
opendevreview | Pierre Riteau proposed openstack/kolla-ansible master: Support CloudKitty deployment with internal TLS https://review.opendev.org/c/openstack/kolla-ansible/+/866598 | 09:01 |
mnasiadka | done | 09:05 |
priteau | thanks! | 09:14 |
opendevreview | Sven Kieske proposed openstack/kolla-ansible master: Add ovn-exporter https://review.opendev.org/c/openstack/kolla-ansible/+/855498 | 09:19 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/2023.1: CI: Fail on fluentd log parsing errors https://review.opendev.org/c/openstack/kolla-ansible/+/902239 | 09:21 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/zed: fluentd: Use labels for transition to v5 https://review.opendev.org/c/openstack/kolla-ansible/+/902240 | 09:22 |
mnasiadka | wrong patch :D | 09:23 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/zed: CI: Fail on fluentd log parsing errors https://review.opendev.org/c/openstack/kolla-ansible/+/902381 | 09:23 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/zed: CI: Fail on fluentd log parsing errors https://review.opendev.org/c/openstack/kolla-ansible/+/902381 | 09:25 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/yoga: CI: Fail on fluentd log parsing errors https://review.opendev.org/c/openstack/kolla-ansible/+/902382 | 09:25 |
* frickler is curious how many backports might be missing for that | 09:29 | |
mnasiadka | that's what I want to check :) | 09:29 |
frickler | mnasiadka: do you also want to propose rc2 for a-c-k or shall I? | 09:29 |
mnasiadka | frickler: you can do that, I hope it's going to be the only rc2 | 09:29 |
frickler | ack | 09:30 |
frickler | https://review.opendev.org/c/openstack/releases/+/902364 | 09:34 |
opendevreview | Merged openstack/kolla-ansible master: fluentd: Fix getting podman labels https://review.opendev.org/c/openstack/kolla-ansible/+/902352 | 10:09 |
mnasiadka | ok, one more and time to update release patch | 10:14 |
opendevreview | Merged openstack/kolla-ansible stable/2023.1: Move [oslo_policy] back inside Jinja if block https://review.opendev.org/c/openstack/kolla-ansible/+/901715 | 10:24 |
opendevreview | Merged openstack/kayobe stable/zed: CI: Test SELinux configuration https://review.opendev.org/c/openstack/kayobe/+/901239 | 11:18 |
opendevreview | Will Szumski proposed openstack/kayobe master: Stop kolla fighting with kayobe over selinux state https://review.opendev.org/c/openstack/kayobe/+/902369 | 11:18 |
opendevreview | Merged openstack/kolla-ansible master: magnum: support kubeconfig configuration file https://review.opendev.org/c/openstack/kolla-ansible/+/896292 | 11:22 |
mnasiadka | yay | 11:26 |
opendevreview | Will Szumski proposed openstack/kayobe master: Disable configuration of SELinux by Kolla Ansible https://review.opendev.org/c/openstack/kayobe/+/902385 | 11:33 |
opendevreview | OpenStack Release Bot proposed openstack/kolla stable/2023.2: Update .gitreview for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902375 | 11:55 |
opendevreview | OpenStack Release Bot proposed openstack/kolla stable/2023.2: Update TOX_CONSTRAINTS_FILE for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902376 | 11:55 |
opendevreview | OpenStack Release Bot proposed openstack/kolla master: Update master for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902377 | 11:55 |
opendevreview | Will Szumski proposed openstack/kayobe master: Remove unused kolla bootstrap variables https://review.opendev.org/c/openstack/kayobe/+/902379 | 12:00 |
opendevreview | Pierre Riteau proposed openstack/kayobe master: Remove kolla_enable_host_ntp variable https://review.opendev.org/c/openstack/kayobe/+/902380 | 12:02 |
opendevreview | Will Szumski proposed openstack/kayobe master: Remove unused kolla bootstrap variables https://review.opendev.org/c/openstack/kayobe/+/902379 | 12:07 |
opendevreview | Merged openstack/kayobe stable/2023.1: CI: Test SELinux configuration https://review.opendev.org/c/openstack/kayobe/+/901243 | 12:14 |
opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible stable/2023.2: Update .gitreview for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902402 | 12:14 |
opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible stable/2023.2: Update TOX_CONSTRAINTS_FILE for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902403 | 12:14 |
opendevreview | OpenStack Release Bot proposed openstack/kolla-ansible master: Update master for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902404 | 12:14 |
frickler | yay \o/ | 12:17 |
opendevreview | Merged openstack/kolla stable/2023.2: Update .gitreview for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902375 | 12:28 |
opendevreview | Merged openstack/kolla stable/2023.2: Update TOX_CONSTRAINTS_FILE for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902376 | 12:28 |
opendevreview | Merged openstack/kolla master: Update master for stable/2023.2 https://review.opendev.org/c/openstack/kolla/+/902377 | 12:28 |
opendevreview | Merged openstack/kolla-ansible master: Update master for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902404 | 12:37 |
opendevreview | Merged openstack/kolla-ansible stable/2023.2: Update .gitreview for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902402 | 12:39 |
opendevreview | Merged openstack/kolla-ansible stable/2023.2: Update TOX_CONSTRAINTS_FILE for stable/2023.2 https://review.opendev.org/c/openstack/kolla-ansible/+/902403 | 12:40 |
SvenKieske | 🥳 | 12:58 |
opendevreview | Merged openstack/kayobe master: Remove libgcrypt package update https://review.opendev.org/c/openstack/kayobe/+/901825 | 12:58 |
dcapone2004 | i do not know what it is, but this version of KA and I are not getting along... | 13:02 |
dcapone2004 | for some version my ceph.conf file is not being copied into the nova_compute container and that is preventing nova_compute from working properly | 13:03 |
dcapone2004 | did the config directory change for this? i have ceph.conf and the keyring file along with the nova-compute.conf in /etc/kolla/nova | 13:05 |
dcapone2004 | cinder and glance work fine and the ceoh.conf and keyrings copied as expected | 13:08 |
dcapone2004 | sorry i have the files in /etc/kolla/config/nova...typed too fast | 13:08 |
ironfoot | Could I get someone to give these a final look and +W please? https://review.opendev.org/q/Iddbdc4190b7953e9140d0740daf57f4062ba1b76 | 13:11 |
sylvr | Hello! I would like to test a git "cherry pick" to see if it fixed the issue I encountered, unfortunately I'm not sure how to proceed.. https://review.opendev.org/c/openstack/bifrost/+/864787 | 13:13 |
ironfoot | sylvr: do you want to cherry-pick that change locally in your env? | 13:19 |
sylvr | yes! | 13:19 |
ironfoot | it's so small, it might be easier to just change the file manually | 13:19 |
sylvr | I installed kayobe using source, so I have the git repo | 13:19 |
ironfoot | ah, thanks for the context, as I haven't used kayobe before | 13:20 |
ironfoot | in the top-right there's a 3-dots menu | 13:21 |
ironfoot | there's the option "download patch" | 13:21 |
ironfoot | you can try that | 13:21 |
ironfoot | there's a cherry-pick option | 13:21 |
sylvr | oh yeah thanks I don't know how I managed to miss that | 13:21 |
ironfoot | sylvr: TIL that menu exist, thanks for making me look | 13:22 |
sylvr | ironfoot : do you know where the source of bifrost is supposed to be when using kayobe ? ^^ | 13:24 |
ironfoot | I don't know, sorry | 13:24 |
sylvr | okay, thanks ! I'll look around | 13:25 |
ironfoot | np! :) | 13:25 |
mnasiadka | frickler: I’ll run some series of CI runs to check for obvious errors - if everything will be fine we’re good to aim for final before end of next week | 13:34 |
opendevreview | Simon Dodsley proposed openstack/kolla-ansible master: Add Pure Storage FlashBlade as Manila backend https://review.opendev.org/c/openstack/kolla-ansible/+/879846 | 14:26 |
opendevreview | Simon Dodsley proposed openstack/kolla-ansible master: Update Pure Storage NVMe Cinder driver https://review.opendev.org/c/openstack/kolla-ansible/+/879844 | 14:28 |
simondodsley | can i get some core reviews for https://review.opendev.org/c/openstack/kolla-ansible/+/879846 and https://review.opendev.org/c/openstack/kolla-ansible/+/879844. Just had to rebase as they have been hanging around so long. | 14:29 |
jovial | sylvr: You'll need to rebuild the bifrost container to apply that bifrost patch (or patch the file in the container) | 14:31 |
mnasiadka | simondodsley: we just released Bobcat, give us couple of weeks to stabilise that, and then we can review C cycle patches | 14:34 |
simondodsley | mnasiadka: Thanks. i did submit these in July for Bobcat as one in particular pertained to a new Cinder driver in Bobcat. I guess Caracal will be OK | 14:36 |
simondodsley | really i'd like to get at least the NVMe driver backported to Bobcat | 14:37 |
mnasiadka | We can discuss that once they are merged in master - but usually we don't backport features | 14:37 |
opendevreview | Pierre Riteau proposed openstack/kayobe master: [release] Sync with Kolla Ansible for 2023.2 https://review.opendev.org/c/openstack/kayobe/+/902421 | 14:54 |
SvenKieske | mnasiadka: this fix for rmq in yoga though would be nice, especially since we introduced quorum queues now: https://review.opendev.org/c/openstack/kolla-ansible/+/901919 | 14:57 |
mnasiadka | SvenKieske: done | 14:59 |
opendevreview | Pierre Riteau proposed openstack/kayobe master: Use OpenStack 2023.2 release https://review.opendev.org/c/openstack/kayobe/+/902422 | 14:59 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/2023.1: enable quorum queues https://review.opendev.org/c/openstack/kolla-ansible/+/902387 | 15:00 |
mnasiadka | actually, around quorum queues, let's try backporting that without changing the default | 15:00 |
opendevreview | Pierre Riteau proposed openstack/kayobe-config master: [release] Synchronise with kayobe for 2023.2 https://review.opendev.org/c/openstack/kayobe-config/+/902423 | 15:01 |
SvenKieske | okay; I'll do that | 15:01 |
SvenKieske | ah there is already a cherry pick for 2023.1 | 15:02 |
opendevreview | Michal Nasiadka proposed openstack/kolla-ansible stable/2023.1: enable quorum queues https://review.opendev.org/c/openstack/kolla-ansible/+/902387 | 15:02 |
mnasiadka | yeah, just did that | 15:02 |
mnasiadka | let's see if that passes | 15:02 |
opendevreview | Pierre Riteau proposed openstack/kayobe-config master: [release] Synchronise with kayobe for 2023.2 https://review.opendev.org/c/openstack/kayobe-config/+/902423 | 15:03 |
mnasiadka | SvenKieske: wondering if we need a job that tests that, but that would need to be multinode for best coverage | 15:03 |
SvenKieske | yeah, maybe | 15:04 |
SvenKieske | in theory we should also align the commit message to match what we do, because this does not enable quorum queues | 15:05 |
mnasiadka | we could just do a separate DNM patch that tests it does work | 15:07 |
mnasiadka | which probably makes sense to do, just to make sure oslo.messaging is working properly at that branch level | 15:11 |
opendevreview | Pierre Riteau proposed openstack/kayobe-config-dev master: [release] Synchronise with kayobe for 2023.2 https://review.opendev.org/c/openstack/kayobe-config-dev/+/902425 | 15:12 |
SvenKieske | sounds good | 15:13 |
mnasiadka | but it's Friday ;) | 15:14 |
SvenKieske | yes! | 15:16 |
opendevreview | Pierre Riteau proposed openstack/kayobe master: Remove unused kolla bootstrap-servers variables https://review.opendev.org/c/openstack/kayobe/+/902379 | 15:24 |
opendevreview | Merged openstack/kolla-ansible stable/yoga: Fix kolla_container_engine since not exist in Yoga https://review.opendev.org/c/openstack/kolla-ansible/+/901919 | 16:16 |
dcapone2004 | can someone guide me to the correct playbook/file where external tls configuration is handled? KA is seemingly completely ignoring the external tls certificate setting for some reason and generating a self signed | 16:18 |
mnasiadka | k-a is only generating self signed if you run kolla-ansible generate-certificates | 16:20 |
mnasiadka | or something like that | 16:21 |
dcapone2004 | that is how it is supposed to work, but for some reason it isn't | 16:21 |
dcapone2004 | did a destroy | 16:21 |
dcapone2004 | and a deploy, even changed the filename on the comment external cert line to haxy.pem to see what it did, and I still ended up with a self signed haproxy.pem file | 16:22 |
dcapone2004 | that is being used to secure external tls | 16:22 |
dcapone2004 | https://pastebin.com/zSJBLVve | 16:24 |
dcapone2004 | that is my globals.yml configuration ... the path for the cert exists... I put it in the config subdirectory intentionally as when moving our customizations cluster to cluster it is easier to just move the entire config directory and have the cert there | 16:25 |
SvenKieske | dcapone2004: I assume you have read https://docs.openstack.org/kolla-ansible/latest/admin/tls.html ? | 16:32 |
dcapone2004 | yes | 16:34 |
dcapone2004 | that is exactly how it is configured | 16:34 |
SvenKieske | you did not set "kolla_copy_ca_into_containers", why? | 16:35 |
dcapone2004 | I'm ONLY using external tls in this case....as u can see in the globals.yml | 16:35 |
dcapone2004 | internal an dexternal ip and fqdn are different | 16:35 |
dcapone2004 | the default is no, and the certificate is a signed cert from a trusted authority | 16:35 |
SvenKieske | is the CA present in your containers? | 16:36 |
SvenKieske | are the permissons for the cert in "kolla_external_fqdn_cert" path correct? | 16:37 |
dcapone2004 | the cert isn't, but I would assume the root cert is | 16:37 |
dcapone2004 | in the doc u linked, that setting was for copying "the CA certificate files in /etc/kolla/certificates/ca will be copied into service containers to enable trust for those CA certificates. This is required for any certificates that are either self-signed or signed by a private CA, and are not already present in the service image trust store. | 16:38 |
dcapone2004 | so I didn't think it needed to be set to yes to copy just my cert file... | 16:38 |
dcapone2004 | but yes permissions are correct....no errors from KA | 16:38 |
SvenKieske | well it's for the cert chain/the CA, if the CA is in the container image already it should not be necessary, just double checking | 16:39 |
SvenKieske | are you building your own containers or reusing the public registry? | 16:40 |
dcapone2004 | I'm running a reconfigure now with the cert moved into the /etc/kolla/certificates path (updated globals.yml to this path as well)... testing if support for a path outside of that directory was lost somewhere / somehow | 16:40 |
dcapone2004 | public registry | 16:40 |
SvenKieske | mhm, I'm confused, as I don't use the public images very infrequently, shouldn't there be more tags? https://quay.io/repository/openstack.kolla/ubuntu-source-haproxy?tab=tags | 16:49 |
dcapone2004 | I don't know if that was related to my issue ... but I am using rocky | 16:53 |
dcapone2004 | no change with cert moved | 16:56 |
SvenKieske | mhm, yeah very weird | 16:56 |
dcapone2004 | enable copy_ca generates error because ca folder doesn't exist | 16:56 |
SvenKieske | src or dst? | 16:57 |
dcapone2004 | pretty sure source | 16:57 |
dcapone2004 | /etc/kolla/certificates/ca doesn't exist | 16:57 |
dcapone2004 | "Could not find or access '/etc/kolla/certificates/ca/' on the Ansible Controller.\nIf you are using a module and expect the file to exist on the remote, see the remote_src option | 16:58 |
SvenKieske | well if you have no special CA or the CA isn't to new for the container cert store this should all not be necessary so that is probably fine and should be set to "off" as you originally had it. | 17:03 |
SvenKieske | it doesn't explain the self signed certs though | 17:03 |
SvenKieske | can you maybe look at the creation timestamps of the self signed certs, are they really new or maybe some old artifacts of your deployment? | 17:04 |
dcapone2004 | interesting, as the cert does have a creation date and time that is before I did a KA destroy | 17:05 |
dcapone2004 | but I don't understand why KA wouldn't see the new cert and update anyway... I have used KA and reconfigure to update certs at twice on previous KA versions without an issue | 17:06 |
dcapone2004 | at least* | 17:06 |
SvenKieske | good question :) | 17:07 |
dcapone2004 | lol | 17:07 |
dcapone2004 | does KA "cache" if the "certificates" command was run at any point somewhere? | 17:07 |
SvenKieske | is this a manual process or do you have maybe some CI stuff setup somewhere/some - new - automation which might interact with certificates? | 17:07 |
dcapone2004 | nope manual process, we are small :-) | 17:08 |
SvenKieske | well the "certificate" command generates the certs, I'm not 100% sure if the destroy command cleans that up? I never used that stuff manually afaik, or it is a long time ago, I can't remember. | 17:09 |
dcapone2004 | after i ran destroy | 17:09 |
dcapone2004 | I wiped out the entire /etc/kolla directory | 17:09 |
SvenKieske | maybe some path changed and the destroy command only cleans up some older path? | 17:09 |
SvenKieske | mhm | 17:09 |
SvenKieske | but the cert is there with an old date? how did you do the wipe? | 17:09 |
dcapone2004 | I did copy the globals.yml and passwords.yml file out of the directory before deleting and copied it back, as I didn't want to have to reedit the file again manually | 17:10 |
SvenKieske | sure | 17:10 |
dcapone2004 | rm -rf /etc/kolla | 17:10 |
dcapone2004 | I also tried cp our cert to /etc/kolla/haproxy.pem, so bbasically our is now in the haproxy.pem file, ran reconfigure, and it doens't look like KA noticed the change (understandable) as basically all tasks were skipped | 17:13 |
SvenKieske | which version are you using again? | 17:13 |
dcapone2004 | 2023.1 | 17:13 |
dcapone2004 | the latest stable KA branch | 17:14 |
dcapone2004 | kolla-ansible@stable/2023.1 | 17:14 |
dcapone2004 | with haproxy overwritten, I am attempting to disable tls, run reconfigure, enable it, and run reconfigure again and see what happens | 17:15 |
SvenKieske | I'm going through the changelog, seeing if I find something related there..maybe we introduced a bug somehow | 17:16 |
SvenKieske | dcapone2004: what changed since the last time you new this was working? did it work on stable/2023.1 for you before? | 17:28 |
dcapone2004 | this is the first time I am using 2023.1 | 17:32 |
dcapone2004 | we only use Openstack for dev, so we do not continuous update, basically deploy new when we upgrade hardware...although I was thinking of changing that as we have a lot of older hardware basically sitting idle now that I was going to play with | 17:33 |
SvenKieske | mhm, but it did work on the release before that? | 17:33 |
dcapone2004 | last release we used was pypi release | 17:34 |
dcapone2004 | I think it is in the 15.X chain | 17:34 |
dcapone2004 | whatever the Yoga release was | 17:36 |
dcapone2004 | but this i feel would be a pretty common deployment concept, the last thing I envisioned not working right... and since it just ins't working for me or I am assuming you would have received more feedback already, I'm guessing it is a specific combo of | 17:39 |
dcapone2004 | things causing the issue | 17:39 |
dcapone2004 | so tls is now off | 17:40 |
opendevreview | Merged openstack/kayobe master: Remove kolla_enable_host_ntp variable https://review.opendev.org/c/openstack/kayobe/+/902380 | 17:40 |
opendevreview | Merged openstack/kayobe-config-dev master: [release] Synchronise with kayobe for 2023.2 https://review.opendev.org/c/openstack/kayobe-config-dev/+/902425 | 17:40 |
opendevreview | Merged openstack/kayobe-config master: [release] Synchronise with kayobe for 2023.2 https://review.opendev.org/c/openstack/kayobe-config/+/902423 | 17:40 |
dcapone2004 | I am going to delete the /etc/kolla/haproxy/haproxy.pem file, enable tls, and run reconfigure | 17:41 |
SvenKieske | yes, I would have expected more reports when this was an issue on our side, as I'm fairly certain this is an often used configuration. | 17:41 |
dcapone2004 | haproxy.pem is deleted | 17:42 |
dcapone2004 | find /etc/kolla/* -name *.pem | 17:42 |
dcapone2004 | ONLY returns our signed cert | 17:42 |
dcapone2004 | I am going to run reconfigure now and see what happens and if it puts that haproxy.pem file back | 17:43 |
dcapone2004 | and of course /etc/kolla/haproxy/haproxy.pem is back as a self signed cert | 17:51 |
dcapone2004 | it is like the kolla_external_fqdn_cert variable is not being merged or picked up | 17:51 |
dcapone2004 | which was my first thought 30 hours ago, but I keep verifying that there is not a typo in the variable name | 17:53 |
SvenKieske | you could use `inotifywait` on the parent directory to detect what creates the cert there: https://stackoverflow.com/a/70133285 | 17:53 |
dcapone2004 | is that going to give me more info than openssl which is what I am guessing an ansible playbook is running? | 17:55 |
SvenKieske | no, well you could also just inspect the ansible.logs I think, that should tell you if a task ran that created the cert. | 17:57 |
dcapone2004 | I feel as those in prior KA release, it generated an error that haproxy.pem didn't exist (even if you tried to use the defaults and forgot to run the certificates command first) | 17:58 |
dcapone2004 | so I am wondering if there was a change implemented at some point that generates the cert if it is missing instead of erroring? | 17:59 |
SvenKieske | I looked at the stable/2023.1 changes only, I didn't find anything there. It might be good to write a detailed bugreport over at bugs.launchpad.net though | 18:01 |
SvenKieske | I'm off for the weekend now, bye! o/ | 18:02 |
dcapone2004 | have a good weekend | 18:02 |
dcapone2004 | so adding to this, so it is logged in the irc logs...I updated the kolla_external_fqdn_cert variable to be an invalid path and KA errors right away, so it is seeing the variable and verifying that the file exists at the path specified | 18:26 |
dcapone2004 | but it seemingly seems to ignore it anyway, so the only thing I can think of is a merge issue | 18:26 |
dcapone2004 | omg....no bug...no issues....just working too fast and then ignoring the obvious leading to a wasted day | 18:46 |
opendevreview | Pierre Riteau proposed openstack/kayobe master: Add python3-devel to Kayobe dependencies https://review.opendev.org/c/openstack/kayobe/+/902449 | 21:54 |
opendevreview | Pierre Riteau proposed openstack/kayobe stable/yoga: Use latest published CentOS Stream 8 image https://review.opendev.org/c/openstack/kayobe/+/902451 | 22:30 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!