Wednesday, 2024-03-06

opendevreviewPierre Riteau proposed openstack/kayobe stable/2023.2: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107407:58
opendevreviewPierre Riteau proposed openstack/kayobe stable/2023.1: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107507:58
opendevreviewPierre Riteau proposed openstack/kayobe stable/zed: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107607:59
mnasiadkakevko: I have bad memories with backporting features that require new inventory groups, otherwise I guess it's ok ;-)08:48
kevkomnasiadka: I understand that it can be a problem ..but also inventory change can be problematic or not ... if it is totally new group which works only with some enable_something ..it should be also OK...09:14
mnasiadkaproblem is it just doesn't run/apply and user doesn't know why09:17
mnasiadkawe could add prechecks if inventory exists - but then it will fail on people that didn't update inventory09:17
mnasiadkanothing is ideal, so I prefer to not backport such changes09:17
mnasiadkabut all others are ok from my perspective09:17
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Refactor of kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91141709:57
opendevreviewMatt Crees proposed openstack/kolla-ansible stable/2023.1: Add precheck for RabbitMQ quorum queues  https://review.opendev.org/c/openstack/kolla-ansible/+/90996710:02
opendevreviewMatt Crees proposed openstack/kolla-ansible stable/2023.1: Rework quorum queues precheck  https://review.opendev.org/c/openstack/kolla-ansible/+/90996810:02
opendevreviewMatt Crees proposed openstack/kolla-ansible stable/2023.1: RabbitMQ: correct docs on Quorum Queue migrations  https://review.opendev.org/c/openstack/kolla-ansible/+/90996910:02
opendevreviewMatt Crees proposed openstack/kolla-ansible master: CI: Only migrate RMQ queues during SLURP  https://review.opendev.org/c/openstack/kolla-ansible/+/90997110:12
*** mrunge_ is now known as mrunge10:22
opendevreviewMerged openstack/kolla-ansible stable/2023.2: Configure missing nova services to expose vendordata over configdrive  https://review.opendev.org/c/openstack/kolla-ansible/+/91106710:42
opendevreviewWill Szumski proposed openstack/ansible-collection-kolla master: Add feature to use binary version of crun  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/91142210:54
opendevreviewWill Szumski proposed openstack/kayobe master: WIP: Add podman support  https://review.opendev.org/c/openstack/kayobe/+/90968611:11
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Refactor of kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91141711:13
opendevreviewWill Szumski proposed openstack/ansible-collection-kolla master: Add feature to use binary version of crun  https://review.opendev.org/c/openstack/ansible-collection-kolla/+/91142211:24
opendevreviewWill Szumski proposed openstack/kayobe master: Add podman support  https://review.opendev.org/c/openstack/kayobe/+/90968611:25
opendevreviewMerged openstack/kayobe stable/zed: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107611:35
WJeffs7508Morning, Anyone had any experience in tuning for 100GBE cards on kolla? We appear to be hitting a 15Gbit/s limit inside VMs/OVS, but host to host get ~98Gbit/s11:46
mnasiadkaare you using SRIOV, or just virtio?11:49
WJeffs7508just virtio, but I'm wondering if this is part of the issue.11:49
mnasiadkait is, vif multiqueue might help a bit, usually SRIOV is the way though11:55
WJeffs7508Yea I was starting to get down that line to think it was the option - but was hoping it wasn't the only way.11:55
kevkomnasiadka: btw, this is nice idea ..add some precheck for inventory change ...11:58
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Move actions to kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91150511:59
kevkomnasiadka: btw, yesterday i was walking around setuptools, pbr, wsgi-scripts stuff , pip resolver, poetry ...etc ... do you have  a plan how to deal with this in kolla images ?  If i am correct .. we are not updating setuptools (and maybe others) for now because of that ...am I right ? 12:02
mnasiadkawe have setuptools pinned because it broke horizon12:05
mnasiadkaI don't know if that's still the case12:05
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Refactor of kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91141712:05
opendevreviewMichal Nasiadka proposed openstack/kolla master: Remove setuptools pin  https://review.opendev.org/c/openstack/kolla/+/90182812:06
mnasiadkalet's see12:06
kevkomnasiadka: I meant email chain I've added you into  right now 12:14
mnasiadkaah, that drama12:15
kevkomnasiadka: yep12:18
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Refactor of kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91141712:19
opendevreviewIvan Halomi proposed openstack/kolla-ansible master: Move actions to kolla_container_facts  https://review.opendev.org/c/openstack/kolla-ansible/+/91150512:19
opendevreviewMerged openstack/kayobe stable/2023.2: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107412:21
opendevreviewMerged openstack/kayobe stable/2023.1: Remove default value from sample configuration  https://review.opendev.org/c/openstack/kayobe/+/91107512:21
opendevreviewMerged openstack/kolla-ansible master: prometheus: Add friendly instance labels for ironic and alertmanager  https://review.opendev.org/c/openstack/kolla-ansible/+/89961412:27
opendevreviewMerged openstack/kolla-ansible master: CI: Replace etcd with redis in GATE_IMAGES for cephadm scenario  https://review.opendev.org/c/openstack/kolla-ansible/+/91114312:28
kevkomnasiadka: hmm, it seems that change which is creating bridges in ovs not working if I am using two bridges :/13:20
kevkomnasiadka: weird https://paste.openstack.org/show/brVDt8fDDsrmFmuvzNNR/13:21
SvenKieskemhm, I wonder if I hit the same problem in ovs-exporter13:21
SvenKieskeah no, that is a different task (I guess)13:21
kevkohttps://ara.master.ultimum.cloud/results/4049.html13:24
kevkoit looks like loop didn't work13:25
kevkomnasiadka: do we have somewhere two bridges configured ? 13:30
kevkoi mean in CI13:30
SvenKieskemhm wait a second, you said loop, that reminds me of something..13:36
SvenKieskewondering if this is somehow related again to https://github.com/ansible/ansible/issues/8084813:39
kevkoSvenKieske: I am using containerized kolla-ansible container and I have this patch included for several releases and I am very glad I have patched ansible ... 13:42
kevkoSvenKieske: I've already check it ...no it's not it13:43
SvenKieskeyes, just rechecked the kolla_toolbox.py and it seems it can't be the culprit, mhm.13:44
SvenKieskewell, it's really curious that I have also a problem in a similar area, when creating ovs-bridges, exactly in this task: https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/common/defaults/main.yml#L11013:45
SvenKieskebut it fails because it can't connect to the ovs db socket because it isn't there, but it should be there (see https://review.opendev.org/c/openstack/kolla-ansible/+/855498/comments/1e150cc2_74f26b6f for some logs)13:46
SvenKieskeso there's a difference to your problem13:46
kevkoSvenKieske: I think it's somewhere in kolla-toolbox ... already debugging 13:47
SvenKieskethe /run (/var/run is just a symlink) directory is part of kolla-toolbox and I don't understand why kolla wouldn't be able to connect. that being said I wonder what are the permission bits on the socket..13:47
SvenKieskethe thing is; I'm pretty sure this whole stuff won't work in podman because we simply don't mount /run there shared, because that is not possible, by deliberate design in podman (I linked afaik a bugreport in the comments above somewhere)13:48
SvenKieskeso I'm also thinking on how to share this socket in a multi r/w fashion with different containers in the podman world13:48
kevkoSvenKieske: if I remember i was also reading documentation a lot and it was everything about r/w shared ...etc etc :D 13:50
SvenKieskeyes, but that's just not possible from podmans pov, what makes it worse, I can even understand the reasoning :D13:54
SvenKieskehttps://github.com/containers/podman/issues/16305#issuecomment-129981000413:55
SvenKieskemhm, I guess I need to look at it from another angle. So the /run can be mounted r/w/shared, but of course only once, because shared means it gets mounted on the host mount namespace, and once that is done it doesn't make sense to mount it again13:56
SvenKieskeso I guess we could "just" add templating logic to detect if this is already mounted and if yes don't try to mount, if no mount it?13:57
SvenKieskethe logic involved might get rather complex though :D13:57
kevkothe problem is with ovn exporter right ? https://review.opendev.org/c/openstack/kolla-ansible/+/85549813:59
SvenKieskeyes13:59
SvenKieskeI want to finally get it finished, but the containerized deployment still has some issues.14:00
kevkoSvenKieske: I will check also right after my issue will be solved 14:01
SvenKieskety, so your issues is that the loop doesn't really create the two bridges? I haven't really seen an helpful error message there though?14:02
fricklermnasiadka: no warning, no meeting?14:02
kevkoI am already here :D 14:03
SvenKieskeah right, it's already 2 past 314:03
spatelmnasiadka hey! 14:04
spatelquick question, How does kolla mount NFS share on compute nodes when using NFS backend for cinder-volume?14:05
mnasiadkameeting time14:06
mnasiadkasorry, train was delayed14:06
mnasiadka#startmeeting kolla14:06
opendevmeetMeeting started Wed Mar  6 14:06:40 2024 UTC and is due to finish in 60 minutes.  The chair is mnasiadka. Information about MeetBot at http://wiki.debian.org/MeetBot.14:06
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:06
opendevmeetThe meeting name has been set to 'kolla'14:06
fricklertrain is EOL *scnr*14:06
mnasiadkamgoddard mnasiadka bbezak frickler kevko SvenKieske mmalchuk gkoper jangutter jsuazo jovial osmanlicilegi mattcrees dougszu - meeting now14:07
mnasiadka#topic rollcall14:07
mnasiadkao/14:07
frickler\o14:07
mmalchuk\o14:07
mattcreeso/14:07
mhinero/14:07
r-krceko/14:07
SvenKieskeo/14:07
dougszu|o14:07
janguttero/14:07
jovial0/14:08
mnasiadka#topic agenda14:09
mnasiadka* CI status14:09
mnasiadka* Release tasks14:09
mnasiadka* Regular stable releases (first meeting in a month)14:09
mnasiadka* Current cycle planning14:09
mnasiadka* Additional agenda (from whiteboard)14:09
mnasiadka* Open discussion14:09
kevko\o/ 14:09
mnasiadka#topic CI status14:09
mnasiadkaI think it's green-ish, there was some breakage due to switch from etcd to redis in cephadm jobs (kolla side image build regex was not updated) - but should be good now14:10
jovialKayobe is green again this week14:10
mnasiadkaaarch jobs got broken with sha256 checking of sources.py, I'll have a look14:10
mnasiadkaotherwise looks good14:10
mnasiadka#topic Release tasks14:11
mnasiadkaThis week is R-4 - Cycle highlights14:11
mnasiadkaAny volunteer to propose cycle highlights?14:11
mnasiadkabbezak: ?14:11
mnasiadkaOk, I'll do that ;-)14:12
mnasiadkajovial: can you do that for Kayobe?14:12
jovialSure14:12
mnasiadka#topic Current cycle planning14:13
jovialIs there an example patch from last time?14:13
mnasiadkajovial: let me find it14:13
fricklerit is in the deliverables file in the release repo14:13
mnasiadka#link https://review.opendev.org/c/openstack/releases/+/90242014:13
kevkomnasiadka: well it's greenish ...but ovs is not creating second bridge if defines :) 14:14
WJeffs7508Anyone know why 2023.1 containers have been removed from Docker? Or if there is a archive somewhere?14:14
mnasiadkakevko: well, we can't test that in CI - I can have a look14:14
kevkomnasiadka: will be fixed in minutes i think14:14
mnasiadkaWJeffs7508: we mainly publish to quay.io/openstack.kolla14:15
jovialthanks14:15
mnasiadkakevko: sure, if you need me to have a look in that just let me know14:15
kevkookay, fixed .. I will added you to review14:15
fricklerkevko: thats sound more like a bug than a CI issue14:15
SvenKieskeI guess s/mainly/only/ with regards to quay.io?14:15
kevkofrickler: mmm...yes it's ...sorry bad interpretation14:15
mnasiadkaSvenKieske: not only, we still have docker publish jobs, but I really don't look at them ;-)14:15
mnasiadkadocker weekly I think14:16
mnasiadkaquay daily14:16
WJeffs7508mnasiadka: Just found them there :) Just wondered if there was a reason it wasn't on docker mostly. 14:16
WJeffs7508Wasn't sure if there was some major reason they got pulled I had missed.14:16
mnasiadkaWJeffs7508: the reason is Docker in the past tried to screw all open source projects and required to move to paid teams14:16
mnasiadkathey backed off that later - but the stench remains14:16
fricklerWJeffs7508: also note those images are only meant for testing, build your own for production use14:16
mnasiadkathat's another thing :)14:17
WJeffs7508Yea agreed. We are :)14:17
mnasiadkaok then, back to the topic - current cycle planning14:17
mnasiadka#link https://etherpad.opendev.org/p/KollaWhiteBoard#L22214:17
mnasiadkaI added RMQ 3.1314:17
mnasiadkaAlthough it's only 3.13.0 now - I prefer to bump it now, than next cycle14:18
mnasiadkawe still have some months to release14:18
SvenKieskeyes14:18
mnasiadkaand as promised on the PTG, we'll (SHPC) work on getting 3.13 to older stable releases14:18
SvenKieskedid anybody look at some of the TLS patches?14:18
mnasiadkawhich ones?14:19
fricklerbest link them in the etherpad, using a common topic14:19
mnasiadkamattcrees: how is the Quorum queues in Antelope?14:19
SvenKieske#link https://review.opendev.org/c/openstack/kolla-ansible/+/90918814:20
SvenKieskebut the "redis-cache" topic doesn't have all afaik14:20
mattcreesThere's some backports in a chain here: https://review.opendev.org/c/openstack/kolla-ansible/+/909967 and I've also changed Caracal to only migrate queues in SLURP: https://review.opendev.org/c/openstack/kolla-ansible/+/90997114:20
SvenKieskewhere exactly should I put caracal PTG links in the whiteboard?14:21
SvenKieskeah I see, line 222ff14:21
SvenKieskeput the link to the redis-cache topic there, but it's only a fraction of all the internal TLS stuff14:22
SvenKieskefrickler, you promised to review last week afaik ;)14:23
mnasiadkapromises, promises ;)14:23
frickleryes, sorry, I'll leave that page open now until I review14:23
mnasiadkafrickler: are you going to work on split-glance this cycle?14:23
SvenKieskemy promised doc patch also took 2 weeks until I got around to it..14:24
fricklermnasiadka: I still intend to do so, yes14:24
mnasiadkagood, if you change your mind - I might want to find somebody else to pick it up, it would be good security-wise to do that this cycle14:25
fricklerwell if someone else wants to work on that, I certainly wouldn't object14:25
mnasiadkalet's go to next topic14:25
mnasiadkafrickler: I didn't say that :)14:25
mnasiadka#topic Additional agenda (from whiteboard)14:26
mnasiadkaSvenKieske: your TLS topic I assume was already mentioned14:26
mnasiadka(mhiner) Please review:14:26
mnasiadkaPointers on where and how to create documentation for ce migration?14:26
mnasiadkaaction option introduction to kolla_container_facts: https://review.opendev.org/c/openstack/kolla-ansible/+/91141714:26
mnasiadkadocker-py version bump: https://review.opendev.org/c/openstack/ansible-collection-kolla/+/91075114:26
mnasiadkatransition to high-level docker api: https://review.opendev.org/c/openstack/kolla-ansible/+/90829514:26
mhinerSpecifically, I would like to know how I can create that documentation page14:27
SvenKieskeah "ce migration" referse to container engine migration, that took me a while to parse.14:28
mnasiadkaall the docs are under doc/source/14:28
mhinerI see, I thought it was supposed to be a page on the docs.openstack.org site14:28
kevkosorry ..i need to go ..i will be around ..but i need to go to another VDI ..we have some incident ...14:28
fricklermhiner: a new page is just a new file. it will get pushed to the docs site automatically14:29
mnasiadkamhiner: it's in sphinx format, it gets generated in the docs job in CI - and then when merged published to docs.openstack.org14:29
mnasiadkamhiner: commented on the docker-py version bump, will have a look in the rest later14:30
jovialAlso, you can use `tox -e docs` to generate locally14:30
mnasiadkaok, let's go forward14:30
mnasiadka#topic Open discussion14:30
mnasiadkaAnybody anything?14:30
fricklermhiner: did that answer your question?14:31
mhineryes, thank you14:31
mnasiadkamhiner: of course in any doubt - ask questions here :)14:31
SvenKieskejust my small doc patch regarding --limit: https://review.opendev.org/c/openstack/kolla-ansible/+/91108214:31
r-krcekHi I would like to ask about my patch. It has been inactive for a while. Is there anything else I need to do? https://review.opendev.org/c/openstack/kolla-ansible/+/90583114:31
SvenKieskeand if anyone has any insight in ovs socket sharing across containers and how to make this sane I would appreciate any feedback, details are in the comments here: https://review.opendev.org/c/openstack/kolla-ansible/+/85549814:32
SvenKieskeI'm still working on it myself of course, but maybe need a different perspective to look at it. the CI fails at creating ovs-bridge. need also to rework how we mount /run/ so it works in podman (currently we just ignore this in podman)14:33
r-krcek(followup to my previous comment) SvenKieske mentioned backporting. Would that also be my responsibility to facilitate as part of the patch?14:34
fricklerSvenKieske: iirc you can only mount explicit subdirs of /run with podman?14:34
mhinerI think that's how it's currently done for podman14:34
SvenKieskeyeah, the problem, as I understood, is that the "share" option means sharing the "/run" dir with the complete host, which only makes sense if you do it once, not twice.. so we need basically a singleton mechanism that ensures this is only run once and then not again. or mount countless subdirs, but I doubt that is a solution because multiple containers need to mount the ovs.socket run dir, namely: kolla_14:37
SvenKiesketoolbox, prometheus-ovn-exporter, ovn(?) itself, probably more14:37
SvenKieskebut r-krcek asked before I did and is possibly easier to answer as well :)14:37
fricklerI don't think a patch introducing a new role would be backportable14:37
mnasiadkaYeah, if you want to backport that, then fix it without introducing a role14:38
SvenKieskecurrently it's not a role, so imho should be fine :) we can maybe move it later to a dedicated role.14:38
mnasiadkayeah, refactor to a separate role afterwards14:39
r-krcekOkay, so in this patch I should fix it without introducing a new role, which will be backported to stable releases and open a new patch that would break it out to separate role.14:41
SvenKieskecorrect. I think the patch is also in a decent shape, at least I don't see anything preventing a merge, but the core reviewers have the ultimate decision :)14:41
r-krcekokay, thank you :) 14:42
mnasiadkaok then14:43
mnasiadkaseems we're done14:43
mnasiadkathanks for coming!14:43
mnasiadka#endmeeting14:43
opendevmeetMeeting ended Wed Mar  6 14:43:55 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:43
opendevmeetMinutes:        https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-03-06-14.06.html14:43
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-03-06-14.06.txt14:43
opendevmeetLog:            https://meetings.opendev.org/meetings/kolla/2024/kolla.2024-03-06-14.06.log.html14:43
mmalchukthanks mnasiadka 14:44
SvenKieskethanks!14:44
SvenKieskekevko: when you're back from your emergency: do you have a link to a patch regarding your ovs issue or is this just an issue you hit in a dev/live env? maybe a bugreport would be nice so we can properly debug it (if it exists in vanilla openstack)14:45
kevkoSvenKieske: it's regular patch ..i will send a patch 14:52
kevkoSvenKieske: it's vanilla openstack bug 14:52
opendevreviewMichal Arbet proposed openstack/kolla-ansible master: Fix creation of ovs bridges  https://review.opendev.org/c/openstack/kolla-ansible/+/91159115:23
kevkoSvenKieske: ^^ https://bugs.launchpad.net/kolla-ansible/+bug/205633215:23
SvenKieskety15:23
kevkoSvenKieske: funny no ? :D 15:24
SvenKieskeyeah, was wondering if we should have dedicated tests for this stuff.. (could in theory checked with a "virtual" precheck I guess)15:26
kevkoWell, this can be tested with Octavia for example ..as I have ... Not octavia_auto_configure 15:45
kevkoIt's also more production setup ... 15:46
kevko*production like 15:46
mnasiadkauhh, keystone is broken by passlib16:00
mnasiadka2024-03-06 13:39:50.483974 2024-03-06 13:39:50.482 38 ERROR passlib.handlers.bcrypt AttributeError: module 'bcrypt' has no attribute '__about__'16:00
mnasiadkafrickler: https://review.opendev.org/c/openstack/requirements/+/910534 - that seems to be related ;-)16:00
fricklermnasiadka: nice, I have heard about that issue but not actually seen it happen yet16:01
fricklerdo you have a link to a failed build? I think we may need to patch reqs within kolla for that for now16:02
mnasiadkaall jobs in https://review.opendev.org/c/openstack/kolla/+/911093 failed because of keystone16:02
fricklerso there goes our greenish CI \o/16:03
SvenKieskebut was passlib updated, or keystone? looking at passlib, is this the still official website, https://passlib.readthedocs.io/en/stable/history/ ? it hasn't really got any updates?16:06
mnasiadkabcrypt was updated16:07
mnasiadkapasslib is not maintained, or at least lousely maintained16:07
mnasiadkabasically keystone needs to stop using passlib16:07
SvenKieskeno update since 3 years, a little concerning for a security lib: https://foss.heptapod.net/python-libs/passlib16:07
SvenKieskepynacl would be better I guess, I don't know about the integration in keystone though.16:11
SvenKieskehttps://review.opendev.org/c/openstack/requirements/+/91053416:12
opendevreviewVerification of a change to openstack/kolla-ansible stable/2023.1 failed: Add precheck for RabbitMQ quorum queues  https://review.opendev.org/c/openstack/kolla-ansible/+/90996716:13
opendevreviewVerification of a change to openstack/kolla-ansible stable/2023.1 failed: Rework quorum queues precheck  https://review.opendev.org/c/openstack/kolla-ansible/+/90996816:13
opendevreviewVerification of a change to openstack/kolla-ansible stable/2023.1 failed: RabbitMQ: correct docs on Quorum Queue migrations  https://review.opendev.org/c/openstack/kolla-ansible/+/90996916:13
SvenKieskeansible apparently also relies on this unmaintained mess: https://github.com/ansible/ansible/issues/8194916:15
SvenKieskenvm, it's afaik deprecated.16:18
SvenKieskeno it's not..ansible source code is a mess16:18
kevkohave anyone seen issue when some router just switching between nodes without the reason ? 16:32
kevkobtw ..router keepalived logging to syslog but we as kolla dropping this log :( 16:33
mnasiadkakevko: it’s usually network problem or your host is too busy to respond to vrrp keepalives16:48
opendevreviewMark Goddard proposed openstack/kolla-ansible master: prometheus: Support overriding address of scrape targets  https://review.opendev.org/c/openstack/kolla-ansible/+/89961516:51
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Revert "Allow setting any_errors_fatal true for gather-facts"  https://review.opendev.org/c/openstack/kolla-ansible/+/91060117:00
opendevreviewMark Goddard proposed openstack/kolla-ansible master: Support reducing scope of delegated fact gathering  https://review.opendev.org/c/openstack/kolla-ansible/+/91050317:00
opendevreviewMark Goddard proposed openstack/kayobe master: Allow to continue when some hosts are unreachable  https://review.opendev.org/c/openstack/kayobe/+/91050917:04
opendevreviewMark Goddard proposed openstack/kayobe master: DNM: Test --continue-on-unreachable  https://review.opendev.org/c/openstack/kayobe/+/91051117:04
mnasiadkaHmm, maybe keystone is not always broken, weird17:24
kevkomnasiadka: well, OK, but how can I be sure what it is ? 17:38
fricklermnasiadka: it seems the bcrypt error also appears in passing jobs like https://75f846b58e02305c95b0-4c4be73445f57ce8e9e80fbec5b1bb43.ssl.cf5.rackcdn.com/911093/2/check/kolla-ansible-ubuntu/f6cc93d/primary/logs/kolla/keystone/keystone-apache-public-error.txt17:40
fricklerso the actual reason for the failure might be something completely different17:41
SvenKieskefrom that log it seems there's a workaround for bcrypt:17:57
SvenKieske2024-03-05 16:06:22.664213 2024-03-05 16:06:22.663 1012 DEBUG passlib.handlers.bcrypt [None req-65773efd-6242-43ac-9a44-8144861c0726 - - - - - -] 'bcrypt' backend lacks $2$ support, enabling workaround _finalize_backend_mixin /var/lib/kolla/venv/lib/python3.10/site-packages/passlib/handlers/bcrypt.py:406\x1b[00m17:57
opendevreviewMerged openstack/kolla-ansible stable/2023.1: Configure missing nova services to expose vendordata over configdrive  https://review.opendev.org/c/openstack/kolla-ansible/+/91106818:34
opendevreviewMerged openstack/kolla-ansible stable/zed: Configure missing nova services to expose vendordata over configdrive  https://review.opendev.org/c/openstack/kolla-ansible/+/91106918:34
mnasiadkafrickler: interesting18:48
samcat116I'm working on a bobcat deployment and my keystone is constantly logging warnings about "Truncating password to algorithm specific maximum length 72 characters.". Has anyone else seen this? I don't have any users with passwords due to sso so I have to imagine its some internal service users that k-a is creating21:35
samcat116I do see that in my passwords.yaml none of them are over 72 characters, so slightly confused21:35

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