Thursday, 2022-09-22

opendevreviewJacob Anders proposed openstack/sushy master: [WIP] Retry BootSourceOverride request when SettingsURI is read-only  https://review.opendev.org/c/openstack/sushy/+/85659701:11
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: Set stage for Zed Release with 21.1  https://review.opendev.org/c/openstack/ironic/+/85884103:01
opendevreviewVanou Ishii proposed openstack/ironic-python-agent master: Fix failure of bind mount in _install_grub2  https://review.opendev.org/c/openstack/ironic-python-agent/+/85727106:11
rpittaugood morning ironic! o/07:02
ajyaGood morning Ironic08:12
ajyaif any 2nd reviewer available - https://review.opendev.org/c/openstack/ironic/+/855872 Thanks08:13
rpittauajya: done08:17
ajyathanks rpittau 08:18
*** akahat|ruck is now known as akahat|ruck|lunch08:39
opendevreviewOpenStack Release Bot proposed openstack/ironic-inspector stable/zed: Update .gitreview for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85886908:52
opendevreviewOpenStack Release Bot proposed openstack/ironic-inspector stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85887008:52
opendevreviewOpenStack Release Bot proposed openstack/ironic-inspector master: Update master for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85887108:52
opendevreviewOpenStack Release Bot proposed openstack/ironic-inspector master: Switch to 2023.1 Python3 unit tests and generic template name  https://review.opendev.org/c/openstack/ironic-inspector/+/85887208:52
*** akahat|ruck|lunch is now known as akahat|ruck09:31
opendevreviewMerged openstack/ironic master: Fix idrac-redfish RAID controller mode conversion  https://review.opendev.org/c/openstack/ironic/+/85587209:38
opendevreviewMerged openstack/ironic-inspector stable/zed: Update .gitreview for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85886909:38
opendevreviewMerged openstack/ironic-inspector stable/zed: Update TOX_CONSTRAINTS_FILE for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85887009:38
opendevreviewMerged openstack/ironic-inspector master: Update master for stable/zed  https://review.opendev.org/c/openstack/ironic-inspector/+/85887109:38
opendevreviewRiccardo Pittau proposed openstack/bifrost master: Convert keystone integration job to jammy  https://review.opendev.org/c/openstack/bifrost/+/85888010:05
opendevreviewVanou Ishii proposed openstack/ironic-python-agent master: Fix failure of bind mount in _install_grub2  https://review.opendev.org/c/openstack/ironic-python-agent/+/85727110:20
opendevreviewVanou Ishii proposed openstack/ironic-python-agent master: Fix failure of bind mount in _install_grub2  https://review.opendev.org/c/openstack/ironic-python-agent/+/85727110:37
opendevreviewMerged openstack/ironic-inspector master: Switch to 2023.1 Python3 unit tests and generic template name  https://review.opendev.org/c/openstack/ironic-inspector/+/85887211:02
kubajjdtantsur: I think I have an idea about what the inspector is doing and have some questions. Should I ask them here or in a private chat?11:03
dtantsurkubajj: all technical questions should rather go to the chat, this way we can engage more participants11:04
dtantsur(and arne_wiebalck knows that you're working lol)11:04
kubajjYou mentioned two subtasks for the first step of the story (access introspection data and provide introspection data from elsewhere). How does it work now? What happens when inspector gets the data from the ramdisk now?11:06
dtantsurkubajj: the data gets validated, then gets piped through a number of plugins called "introspection hooks". Then so called "introspection rules" are run against this data (these are admin-defined rules written in a JSON-based DSL that may already be familiar to you).11:08
dtantsurkubajj: finally, the data is stored in a local database or Swift (an unprocessed copy is stored too).11:09
dtantsurkubajj: task #1 is to replicate the last step in ironic. So, all the processing happens in inspector still, ironic only gets the result and stores it for its own usage.11:09
dtantsurtask #1.1. is to provide a similar process for other inspection implementations (even if no-op for now).11:09
dtantsurtask #1.2. is to provide an ironic API for users to fetch this stored data (the same way it's possible now for inspector API).11:10
dtantsurI think that's it for the start.11:11
dtantsurWe may ignore unprocessed data for now.11:11
dtantsurthe data itself consists of "inventory" key with the standard data from IPA. and other keys that are generated by plugins.11:12
dtantsurone of the things I'd change when doing this in Ironic is to hide or plugin-generated data under a new key ("plugin_data"?)11:12
dtantsurso that the top level only has two keys: "inventory" (standard) and "plugin_data"/"extra" (plugin dependent)11:12
kubajjIs the RootDiskSelectionHook (part I modified to match root device hints logic from IPA) one of the instrospection rules?11:12
dtantsurkubajj: correct11:12
dtantsurso, you're already familiar with hooks :)11:13
kubajjSo the API that I need to create is for the result of the inspector processing to be passed to ironic, right?11:14
dtantsurkubajj: yes - for now.11:15
kubajjdtantsur: Is there anything already passed from inspector to ironic, so that I could use a similar approach?11:17
dtantsurkubajj: introspection status (see drivers/modules/inspector.py), but it may not match 1-1 to what you need11:18
kubajjdtantsur: thanks11:18
dtantsurkubajj: since inspection may be asynchronous, you cannot just return the resulting data from InspectInterface.inspect_hardware11:19
opendevreviewJacob Anders proposed openstack/sushy master: [WIP] Retry BootSourceOverride request when SettingsURI is read-only  https://review.opendev.org/c/openstack/sushy/+/85659711:19
dtantsuron the other hand, out-of-band implementations (redfish etc) don't have a built-in storage. a dilemma.11:19
dtantsurso what we probably need is a new call somewhere e.g. in conductor.utils that will be called by InspectInterface implementations11:20
dtantsurpush model instead of pull model, if you wish11:20
dtantsurin terms of Inspector, it means that once the driver detects success, it asks Inspector for the data and stores it using the new conductor call11:21
* dtantsur hopes he expresses himself clearly despite being a bit sick11:21
kubajjOh, it is from ironic and not inspector. I see. So, the front-end calls the introspection and waits for the introspection status. Then my change should come in.11:23
dtantsurcorrect11:24
kubajjdtantsur: Do you mean push from inspector?11:24
dtantsurkubajj: no, from the ironic's inspector driver11:24
dtantsurso, you said correctly in the previous sentence11:24
iurygregorygood morning Ironic11:25
kubajjdtantsur: Do I need to modify inspector in any way?11:28
dtantsurkubajj: not at this point, I think11:29
kubajjand for testing purposes, should I deploy the devstack with the config from ironic-inspector docs?11:30
dtantsurkubajj: that, or bifrost (it has inspector by default)11:31
kubajjok, thanks dtantsur 11:38
dtantsuryou're always welcome11:38
shukunPlease review the next three backport patches: 11:42
shukun  - yoga: https://review.opendev.org/c/openstack/ironic/+/850553  11:42
shukun  - xena: https://review.opendev.org/c/openstack/ironic/+/850554  11:42
shukun  - wallaby: https://review.opendev.org/c/openstack/ironic/+/850707 11:42
shukun 11:42
shukunI understand the three patches are backporting a feature patch (https://review.opendev.org/c/openstack/ironic/+/845347), but that patch aims to support FIPS, and FIPS support will be necessary for some distributions which does not use master branch. So we want to backport that patch to every still maintained stable branch. FYI, for wallaby branch, the backport patch assumes that the next patch is merged: https://review.opendev.org/c/openstack/iro11:42
shukunnic/+/85280311:42
iurygregoryrpittau, except for the two patches in bifrost do we need something more?11:51
rpittauiurygregory: which bifrost patches?12:27
opendevreviewMerged openstack/ironic master: Implement a DHCP driver backed by dnsmasq  https://review.opendev.org/c/openstack/ironic/+/85168113:22
iurygregoryrpittau, the ones to supprot the new ubuntu13:34
iurygregoryjammy I think?13:34
rpittauiurygregory: there's more to that, I think we nee to exclude the change from zed and go to antelope directly13:37
iurygregoryok13:38
iurygregoryso I will request bifrost release now =)13:38
TheJuliagood morning13:54
kubajjGood morning TheJulia13:55
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/20.2: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889514:03
JayFThose iRMC backports (https://review.opendev.org/c/openstack/ironic/+/850553 being yoga) seem like a little extreme for backports -- including adding config options14:08
JayFin the past have we been more leniant about backporting for stuff like this? I'm just a little leery of sending new config options back to wallaby by default14:08
JayFAlso, even though it doesn't raise the requirement in driver-requirements.txt, the new functionality only comes into play if folks update that package14:09
opendevreviewJulia Kreger proposed openstack/ironic stable/ussuri: CI: fix ussuri branch  https://review.opendev.org/c/openstack/ironic/+/84351514:09
TheJuliaJayF: adding config options has been viewed as generally okay, and adding new driver capabilities as long as it as an operator benefit14:13
iurygregorygood morning TheJulia 14:13
TheJuliaJayF: it is new config options that break things that is not okay14:14
JayFTheJulia: a warmer, more cuddly backport policy <3 lol14:14
JayFI dig it, cool stuff14:14
TheJuliayes, that was a fun one to argue for :)14:14
*** vanou is now known as Guest114914:15
JayFHonestly with stuff like this; I just find myself wondering how many people who are running e.g. wallaby still care and feed their environment well enough to safely execute a driver lib update14:15
TheJuliaanyhow, I just uploaded https://review.opendev.org/c/openstack/ironic/+/843515  hoping it will fix ussuri's ci14:15
TheJulialooks like it sclose14:15
JayFlike, not "we shouldn't do this for [theoretical reasons]", but more curious about the practicality of if it's actually consumed14:16
JayFFor some reason, I find myself trying to understand operators in different situations than I've been in a little more in the last week :D 14:16
TheJuliaconsumed, it is. rhosp 17 == Wallaby14:16
JayFYou all will do the driver-requirements.txt upgrades in-cycle too?14:16
TheJuliawe accept updates to packages, we functionally ignore driver-reqs and track branches for the most part14:17
JayFIt feels weird, but I almost wish we had an official upstream place we documented people who consume and package openstack downstream, with details about versions/branches/etc14:18
JayFthere's probably no way to do that which wouldn't instantly bit-rot, but I have no problem with upstream priorities being aligned with folks who are getting software in front of people14:18
JayFI just like being explicit about why we're doing things :D14:18
TheJuliaJayF: that would be nice, but politics :(14:19
TheJuliapackaging politics are saddening14:19
JayFI've started to get a glimse into some of that in my on-my-own-time effort to become a Gentoo developer. And frankly, that involves a lot less money lol14:19
iurygregoryTheJulia, I was looking at the prelude "to support to enable greater separation " of duties, since I'm not native speaker the "to support to enable" sounds a bit strange to me .-.14:20
TheJuliaoh, just s/to support//14:21
iurygregoryok o/14:21
TheJuliasorry, it is a bit strange, I must have been interrupted while writing14:21
iurygregoryno worries14:22
iurygregoryin 38min PTG topics meeting14:22
* TheJulia looks at coffee and hopes it completes its task14:24
JayFTheJulia: re: ussuri CI patch; did we recently land those partition image tests in tempest?14:24
TheJuliaiurygregory: when did the combined tests land in tempest?14:24
TheJuliaI don't remember14:24
JayFI was pretty sure I'm had something merged to ussuri fairly recently14:24
dtantsurI think we need to add the bit about config options in backports to some docs14:24
* JayF asks git14:24
dtantsursomebody asks every time14:25
TheJuliadtantsur: ++14:25
dtantsurdriver-requirements is very hairy14:25
dtantsurlike VERY14:25
JayFlast commit in ussuri is 8/914:25
dtantsurwe've done that on a few occasions, but every time it's a chance of issues downstream14:25
JayFdtantsur: TheJulia: and never take me asking a question as like "I think X", I ask because I wanna know and usually it also means I have no strong opinion. Just trying to avoid being a human rubber stamp :D 14:25
TheJuliaJayF: sometimes some stuff worked, it has become a pile of failures due to the queue tag removal, so now everything together14:25
JayFTheJulia: yeah, I think I was remembering my patch to *nova* for the ironic driver which landed in ussuri more recently14:26
JayFTheJulia: this timeline makes more sense and I shoulda checked before typing in IRC :P14:26
TheJuliaheh14:26
TheJuliayeah14:26
TheJulianext ussuri patch is likely going to be to turn off a bunch of jobs that are really no longer needed or just won't be fixed that are non-voting14:27
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/20.2: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889514:27
TheJulialow risk ultimately because things around the jobs have broken/changed as time has moved on14:27
JayFgood stuff14:27
JayFI mean, if we're sending something back to ussuri there's a good chance it's: 1) minor, 2) security or 3) driver14:28
TheJuliaAnd, backports only... so we *really* only need base sanity checking stuffs working on the branch at this point14:28
JayFin which case coverage also matters less14:28
TheJuliaJayF: bingo14:28
JayFThe biggest CI thing weighing on me right now is that we have 3rd party CI systems that -- overall are good -- but still have broken jobs running and voting14:29
JayFand it makes it super easy to ignore results if it's constantly failing14:29
JayFI should put that on my list, to follow up on that14:29
TheJuliakubajj: so your looking into merging inspector into ironic right?14:29
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/19.0: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889614:30
kubajjTheJulia: yes, correct14:30
TheJuliaso I took a look at the db interface code in inspector yesterday14:31
TheJuliaI would highly advise you don't copy/paste db related code and you re-implement in the sqlalchemy2.0 style we've already started to work on in ironic14:31
TheJuliatl;dr, inspector is very not sqlalchemy 2.0 compatible14:31
iurygregoryTheJulia, I don't remember from top of my head .-. I can check later today14:32
TheJuliaiurygregory: doesn't really matter14:32
TheJuliaI'm thinking, overall, that for inspector, we can fix it, but it is going to take a lot of rewriting of the db layer which will take some time to just fix inspector14:33
TheJuliathat may end up helping, since it will be in a very similar style to ironic, but it is much more something to be mindful of14:35
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/19.0: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889614:35
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/19.0: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889614:36
kubajjTheJulia: should I do the rewriting?14:36
opendevreviewRiccardo Pittau proposed openstack/ironic bugfix/19.0: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889614:38
iurygregoryJayF, TheJulia thoughts on the name of the step in https://review.opendev.org/c/openstack/ironic-python-agent/+/566544 ? based on NobodyCam comment the step makes sense so I'm ok with it or maybe we should change 14:39
JayFbluntly, I think that whole mellanox->nvidia rename is just going to confuse the hell out of everyone14:39
JayFbut it's also unreasonable of us to ask them to not rebrand14:40
* JayF just tosses his hat in with `update_nvidia_nic_firmware` as the best of not-awesome options14:41
TheJuliaI think that is actually a better name, but yeah :\14:42
TheJuliastill needs a reno/docs and the actual code change14:43
TheJuliakubajj: if you focus on api/high level db object aspects, you should be able to avoid the pain points, but I think we should discuss further once we each have more clarity14:44
TheJuliaI guess the question is, what will the migration look like. Or at least, that might be something to ponder14:44
* TheJulia makes more coffeee14:45
kubajjTheJulia: should I focus now on what I would implement on the Ironic side and then discuss my plan with you to figure out what needs to change on the inspector side?14:48
TheJuliakubajj: I think that is perfect14:48
TheJuliasince I expect I'll be working on sqlalchemy 2.0 for inspector14:49
iurygregoryIf any core have some time https://review.opendev.org/c/openstack/ironic/+/858841 we need this to cut the Zed release o/14:53
iurygregoryI'm pushing the changes for releasenotes in Julia's patch to add the prelude after my lunch14:53
TheJulia+2'ed14:54
TheJuliaiurygregory: ack14:54
TheJuliaWell, so far so good with the ussuri patch14:57
TheJuliaabout 70% of the way there14:57
JayFlooking14:57
TheJuliaat least on check14:57
iurygregoryPTG call in 2min14:57
iurygregoryLink https://meet.google.com/ivs-qwyc-kpo14:59
TheJuliajanders: What time would work for you and Moshe for Active Steps ?15:33
TheJuliajanders: we're thinking splitting it so there is a 7am utc session to do requirements/initial thought gathering15:36
iurygregoryJayF, operator-hour-placeholder on Wed 13 UTC  essex room15:40
opendevreviewVerification of a change to openstack/ironic master failed: Set stage for Zed Release with 21.1  https://review.opendev.org/c/openstack/ironic/+/85884116:34
rpittaubye everyone o/16:37
* iurygregory goes for lunch16:49
opendevreviewVerification of a change to openstack/ironic master failed: Set stage for Zed Release with 21.1  https://review.opendev.org/c/openstack/ironic/+/85884116:58
opendevreviewMerged openstack/ironic stable/ussuri: CI: fix ussuri branch  https://review.opendev.org/c/openstack/ironic/+/84351517:03
JayFIt's time for my semi-daily stable review request funtime: https://review.opendev.org/c/openstack/ironic/+/857771 https://review.opendev.org/c/openstack/ironic/+/858468 (wow, I'm down to only two)17:29
opendevreviewJulia Kreger proposed openstack/ironic stable/ussuri: CI: Fix/Update a few more jobs  https://review.opendev.org/c/openstack/ironic/+/85896217:43
TheJuliaokay, that should clean it up the rest of the way17:43
TheJuliaussuri that is17:44
TheJuliaboom17:45
JayFI'll wait for zuul to respond on it then go vote on the change17:45
JayFwould prefer 2x+2 on that since it's changing test coverage17:46
JayFmeaning like, I won't +2A it like I did the direct fix :D17:46
opendevreviewJay Faulkner proposed openstack/ironic stable/yoga: Redfish: Consider password part of the session cache  https://review.opendev.org/c/openstack/ironic/+/85890317:50
TheJuliahttps://review.opendev.org/q/If69ce1cf2789d9d60fb8e544596cf7d29eab514d <-- could also use some stable reviews17:52
TheJuliayeah, all of that is non-voting that I changed for ussuri, so better to stop/see/then approve17:53
JayFTheJulia: ack, it's on my list17:53
TheJuliai did recheck the ussuri patch in that series17:53
TheJuliasince it's ci is now happier17:54
JayFYeah; I'm slightly disappointed that we landed the stuff in yoga before it went into bugfix/17:54
JayFI know policy doesn't require us to put every patch everywhere, but it's nice if we do17:54
* JayF is super guilty of approving patches w/o checking for this17:54
TheJuliarpittau: https://1db75cf0b12d832dc11e-0da77774ba1e870a646f19d85e727a87.ssl.cf5.rackcdn.com/858896/4/check/ironic-tox-unit-with-driver-libs/7523b5b/testr_results.html 8\17:55
opendevreviewMerged openstack/ironic bugfix/20.2: Redfish: Consider password part of the session cache  https://review.opendev.org/c/openstack/ironic/+/85777119:08
opendevreviewVerification of a change to openstack/ironic bugfix/18.1 failed: Do not reboot into nowhere after BIOS settings with fast-track  https://review.opendev.org/c/openstack/ironic/+/85846819:08
TheJuliaso now the standalone job fails on ussuri :\20:21
opendevreviewMerged openstack/ironic bugfix/20.2: Fix iRMC driver to use certification file in HTTPS  https://review.opendev.org/c/openstack/ironic/+/85889520:24
opendevreviewMerged openstack/ironic master: Set stage for Zed Release with 21.1  https://review.opendev.org/c/openstack/ironic/+/85884120:29
JayFI see all the reviews up for releases -- I'm going to assume we don't need more time, and just let those go in on 9/23 as scheduled (tomorrow). If anyone needs me to put a -1 on releasing an artifact, please let me know (today if possible)20:43
* JayF wonders if they honor anyone's -1, or just the PTL ... I hope it's everyone core on Ironic?20:44
JayFNobodyCam: You or Waleed likely going to get around to this? It's only missing prose (release note) and a name change to be mergable, but you've got less than a day :|  https://review.opendev.org/c/openstack/ironic-python-agent/+/56654420:47
erbarrwhat's using dbcounter? I got a notification from security that a 3rd-party group compromised it as a proof of concept and I got 90 days to fix it...20:51
JayFI did the math for a daily internal update I curate for GR-OSS team --> Zed will be the 18th release of OpenStack that contains Ironic (if you count incubation time)20:51
JayFerbarr: if there's a concern that one of our dependencies, or dependency-of-dependency is compromised in a way that could impact OpenStack, please open a private bug at storyboard.openstack.org about it20:52
JayFalthough consider me effectively nerd-sniped20:52
JayFTheJulia: are you working on a revision of https://review.opendev.org/c/openstack/ironic/+/858582/1/releasenotes/notes/zed-prelude-09fe95b11ad2459d.yaml ?21:16
JayFwe have to get this merged, and I know there was talk around it but I'm not certain what status it's in, and don't want to dupe work21:17
* JayF works on a revision just in case21:17
TheJuliaJayF: I believe iurygregory was going to21:19
JayFack; it says "please edit", and I think he's (hopefully?) asleep21:20
JayFso I'm going to put in a revision and let him edit further if he wants21:20
JayFand trust him to get it over the finish line tomorrow21:20
TheJuliaEh, late afternoon in brazil21:20
JayFoh, I forget he's in brazil21:20
TheJuliaiurygregory: o/21:20
TheJuliaerbarr: Oslo.db I believe…. I think it gets pulled in as a dependency of a dependency, so storyboard as a security story would be most appropriate against the particular component and then likely ping fungi21:22
JayFTheJulia: erbarr: FWIW; master branch of ironic with all deps installed (for unit tests), that package is not installed.21:23
JayFTheJulia: erbarr: So we may want/need to isolate which branches it's happening on as well, if Ironic is impacted.21:23
erbarryea, I'm seeing the plugin on pretty much every service from the devstack log, I tracked it down to this I believe: https://opendev.org/openstack/devstack/src/branch/master/tools/dbcounter21:23
erbarrsecurity saw it on pip3_freeze.txt and saw it wasn't a public pip package and made a malicious one to proof of concept it seems, I think I gotta yell at them or something21:24
JayFI mean, it's a reasonable concern if that's meant to be pip-installed that we should reserve the name even if we don't release it.21:25
ashinclouds[m]Ahhhhh name conflict too wheeeee21:25
JayFerbarr: I'd call that a very, very, very low impact security bug against devstack21:25
JayFerbarr: but they would likely be able to tell you for sure (and I wouldn't be surprised if someone argues it's not a bug)21:25
erbarryea, agree JayF21:25
JayFerbarr: I do feel for you, I know when the eye of security-sauron looks your way, it can be hard to get them to look away without a patch or something to point at :|21:26
erbarr*shrug* lol21:26
opendevreviewJay Faulkner proposed openstack/ironic master: Zed: Add a prelude for the release notes  https://review.opendev.org/c/openstack/ironic/+/85858221:27
JayFiurygregory: ^ I kept edits to a minimum, if you already have changes locally and need to dunk mine, it's not a problem21:27
fungierbarr: JayF: TheJulia: if it's a dependency of oslo.db that's the problem, then launchpad bug reported against that (i and the rest of the vmt will be automatically notified, but feel free to give me the bug number via privmsg if in doubt)21:55
TheJuliaSo, sounds like something devstack does with a same name as something else that caused a security team to freak21:56
TheJuliaAt least, that is my take21:56
* TheJulia will actually be able to look for realz in a little bit21:58
JayFTheJulia: I'21:58
JayFTheJulia: I'm looking at it for reals, and I sent fungi a concise (as concise as I get) summary in DM21:59
JayFTheJulia: going to try and keep it outta the main channels now until fungi says otherwise; even though I think it's probably OK it's not the project I work directly on so going to be extra careful :D21:59
TheJuliaK22:03
fungiyeah, https://review.opendev.org/839820 seems to be the origin of the code in question, so probably would be good to loop dansmith in as the author22:03
JayFfungi: is this public bug / ML safe? Or should I keep communications about this direct22:04
JayFfungi: I kinda feel like if we're going to make noise about this, someone should park that name first before someone gets any ideas :)22:04
dansmithso.. what?22:04
dansmithis there a real concern or is this a naming clash?22:04
fungiseems like it's low-risk and already public22:05
JayFdansmith: https://review.opendev.org/839820 added a python package, dbcounter. We had a report from an Ironic operator that their security team flagged it as a pip installed package that did not have a reserved name in pypi, and theorized that could be used as an attack vector.22:05
dansmithagainst devstack? :)22:05
fungidansmith: erbarr was notified by someone that the dbcounter package devstack embeds doesn't exist on pypi, so has been cautioned that it could become a problem if someone registered it and then uploaded malware22:05
dansmithetiher way, I don't think there's any assertion anywhere that every python package has to be registered in pip22:06
dansmither, pypy22:06
fungipypi, but i concur22:06
JayFI agree in broad strokes; but I've worked at large companies that had similar policies (you cannot install python packages that do not have pypi names reserved, or you had to block that name from being synced at the proxy)22:06
dansmithokay, I strongly disagree that we should need to register it on pypi because we use it internally to hook into sqlalchemy22:06
fungiwith my vmt hat squarely affixed, i'm inclined to not care about this22:06
dansmithfungi: same, although mine is a paper vmt hat I just made myself22:07
JayFfungi: dansmith: we might make erbarr's life a little easier if we documented this in a bug? My main concern in light of the facts is that I don't want erbarr's security team leaving with the impression we didn't take their report at all.22:07
JayFI'm happy to write the bug so one of you can WONTFIX it :D 22:07
fungicompanies with that sort of policy shouldn't be installing devstack. it's a much bigger security risk on its own than a non-registered pypi package22:07
dansmithfungi: agree22:08
dansmithJayF: sure if you want to file a bug I'll be glad to "I understand but disagree" it22:08
JayFI don't disagree with any of this, I just like writing it down in a more pemanent place.22:08
fungiyep, happy to add a vmt stamp on some bug if you file it, for posterity22:09
* TheJulia reads, and feels like there is a positive outcome22:10
JayFdansmith: fungi: https://bugs.launchpad.net/devstack/+bug/199058922:12
fungithanks!22:12
JayFI put most of what we need in the desc, but it's probably better just for posterity if someone else agrees and mashes the close buttons 22:12
JayFIDK if I even have power to do that in devstack anyway22:12
JayFerbarr: To summarize for you; we've filed https://bugs.launchpad.net/devstack/+bug/1990589 but it is not expected to recieve any real action as OpenStack (and generally, python) does not guarantee that every python package we ship in git (especially for dev purposes) will exist in pypi, or should be installed/upgraded from pypi.22:13
JayFerbarr: you can feel free to share that bug link with your security team if they'd like to make a different case there22:14
fungithat is an excellent and accurate summary22:16
JayFI wrote it like I was writing it to the Paranoids back when I worked at Yahoo! :) They taught me how to speak security-team a bit better 22:17
fungispace paranoids?22:18
* fungi loves tron22:18
JayFI'm not familar with that term; I only saw tron once and I was drunk and it was over a decade ago lol22:19
JayFfrom yahooinc.com > We're the information security team — widely known as The Paranoids — that defends the things you love the most about Yahoo from cybersecurity threats. 22:19
JayFbasically just a really good marketing name for an internal security team22:19
fungiin like (kevin) flynn22:19
* fungi fights for the users22:22
opendevreviewJulia Kreger proposed openstack/ironic stable/ussuri: CI: Fix/Update a few more jobs  https://review.opendev.org/c/openstack/ironic/+/85899422:45
TheJuliaso looks like there is an old inspector patch I can resurrect from the depths of abandoned state as a first pass to clean up db access23:14
TheJuliarebase is not... too narly so hopefully forward progress in the next few days23:14
opendevreviewIury Gregory Melo Ferreira proposed openstack/ironic master: Zed: Add a prelude for the release notes  https://review.opendev.org/c/openstack/ironic/+/85858223:26
iurygregoryTheJulia, if you are still around ^23:27
iurygregorynothing to change in releasenotes, so I just fixed a few things in the prelude 23:27
TheJuliaAck23:27
* TheJulia +2's and takes her migraine back to the bedroom where blahaj is waiting23:30
iurygregorytks!23:30

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