Wednesday, 2025-09-10

opendevreviewLuan Utimura proposed openstack/ironic master: Fix nexthop error when adding route to PUBLIC_SUBNET_IP  https://review.opendev.org/c/openstack/ironic/+/96029900:40
kubajjdtantsur: are you around? We are working on the refactor of https://review.opendev.org/c/openstack/ironic-python-agent/+/937342 - the extraction of the functions to RAID utils brings some problems - i.e. we would need to move other functions outside of hardware.py to avoid cyclic imports - would this be ok, or should we keep it in the hardware.py in that case?08:58
kubajjI do not know how much other operators change their downstream hardware managers, so do not want to break stuff (the change is a bug fix, so was thinking about backporting it)08:59
kubajjdtantsur: please ignore, I think there would be too much to move, so we are going to keep them in hardware09:06
dtantsurkubajj: *nod* there is a known problem: hardware.py has both the abstract hw manager interface and the specific hw manager, so circular imports are a pain11:47
dtantsurat some point, I'm tempted to move GenericHardwareManager out of it11:47
kubajjdtantsur: valid11:47
koperg[m]o/ Hello Ironic... (full message at <https://matrix.org/oftc/media/v1/media/download/AYkoxSAsYj9BZr2yWs4eu3jrugozMLhn9uqJefMiXTWEvmSFZsIr3ukpwk3C4fmwfWKAUfCR45bhOSNXt25r95VCeZe47NSwAG1hdHJpeC5vcmcvRHRnQmVGS2VqTkViTEVOV21NeVJxa2di>)11:49
dtantsurkoperg[m]: please write shorter messages, otherwise the matrix bridge only posts a link11:50
koperg[m]dtantsur: sorry about that. Just saying i would appreciate a review on 2 relatively small NGS patches.11:51
lutimuraJayF: hey! just to let you know, i did some adjustments on https://review.opendev.org/c/openstack/ironic/+/960299 and zuul seems to be happy with it :)11:59
opendevreviewPierre Riteau proposed openstack/bifrost master: Fix support for CentOS Stream 10  https://review.opendev.org/c/openstack/bifrost/+/95885312:52
opendevreviewPierre Riteau proposed openstack/bifrost master: CI: Add testing for CentOS Stream 10  https://review.opendev.org/c/openstack/bifrost/+/95968412:53
opendevreviewMerged openstack/bifrost stable/2024.1: [2024.1 only] Drop upgrade jobs since 2023.2 brach doesn't exists  https://review.opendev.org/c/openstack/bifrost/+/95931712:54
opendevreviewVerification of a change to openstack/networking-generic-switch master failed: Cast boolean Netmiko kwargs to native types  https://review.opendev.org/c/openstack/networking-generic-switch/+/95807913:10
opendevreviewMerged openstack/ironic master: api: Fix off-by-one error  https://review.opendev.org/c/openstack/ironic/+/96028813:18
JayFdtantsur: kubajj: I would be+100000 to moving generic hardware manager to it's own module 13:19
kubajjJayF: dtantsur: I think I have the workforce to do it (my intern is very keen to move stuff :D )13:19
kubajj(mostepha: 😉)13:20
JayFhttps://review.opendev.org/c/openstack/ironic/+/960299 is needed to fix CI in some devstack configs, has my +214:01
JayFplease review it soon or I will land as a single core to unblock openstacksdk ci14:01
fricklersdk made the job non-voting, so not a blocker currently, but don't let that stop you anyway, would still be good to revert to voting asap14:02
dtantsurkubajj, mostepha: please do then :)14:05
kubajjdtantsur: could we do it after we fix the safeguards though? 😉14:06
dtantsuroh yeah, definitely. I was only worried about infinitely growing functions.14:07
stephenfinJayF: fwiw I'm making it voting again, but it was never an issue in the gate, only locally15:03
JayFah15:03
stephenfinlast time it was left unvoting for a while, quite a bit of broken stuff crept it15:03
stephenfin*in15:03
opendevreviewJakub Jelinek proposed openstack/ironic-python-agent master: Fix skip block devices for RAID arrays  https://review.opendev.org/c/openstack/ironic-python-agent/+/93734215:04
JayFI suspect there may be value in cross-gating it15:07
JayFsince you clearly are more sensitive to microversion issues15:07
JayFespecially since the schema changes are in line15:07
kubajjdtantsur: tried to refactor, let us know if this is more readable15:08
kubajjJayF: we went through the security issues you listed and just made it stricter 😈15:08
opendevreviewStephen Finucane proposed openstack/ironic master: Add cross-gating job with openstacksdk  https://review.opendev.org/c/openstack/ironic/+/96039315:13
stephenfinJayF: good idea ^15:14
JayFkubajj: I asked claude just to trace the code path for the one I found and it's like "which one of these 5 were you thinking about" lol15:20
kubajjJayF: 🫠15:20
JayFhint: some of those predated your code :D 15:21
JayFI meant it more as I'm impressed by claude's review than anything else fwiw15:21
kubajjnice15:21
kubajjJayF: btw, the assumed behaviour is for a node to be cleaned to deploy these - that's why we are strict with enforcing volume names15:23
JayFkubajj: https://review.opendev.org/c/openstack/ironic-python-agent/+/937342/6..7/ironic_python_agent/hardware.py#3148 I am ... sketched out a little by that logic?15:26
JayFkubajj: I guess I'm not convinced that "fail cleaning" is the right behavior on a failure *that can be trivially induced by the previous tenant*15:26
kubajjJayF: but if they are using create configuration, it will fail to validate configuration15:32
JayFI don't understand how that relates15:32
kubajjif the previous tenant did something, the node needs to clean15:32
JayF_create_raid_ignore_list() is in the cleaning codepath, isn't it?15:32
JayFif it's only in the create path I can see maybe what you mean15:33
kubajjJayF: nope, it is for creating15:33
JayFaha, that's the bit I was misunderstanding15:33
kubajjJayF: delete configuration is only using _handle_raid_skip_list15:33
JayFwhich I assume/hope doesn't kaboom there15:33
kubajjJayF: create also calls that, but only to check that the existing raid devices are actually supposed to be there15:34
JayFyep 100% fewer kaboom15:34
JayF+215:34
JayFthanks for walking me thru it15:34
kubajjJayF: are you sure about the +2? I was actually going to ask about our tests. We did not figure out how to call _create_raid_ignore_list from test_hardware, so it does not have any test case for itself. We do include a couple of tests for the whole create_configuration15:36
JayFyeah it's awkward that the methods are nested, likely is what is making the testing harder15:36
JayFI'll put this plainly: You are the primary customer for this feature in my mind, and I trust to some extent you have a good bit of certainty it works for your use case :). If that's not true, please W-1 and add some tests or do more testing :)15:37
JayFIf it is true, then maybe add more unit test coverage when you do that module move15:37
kubajjJayF: we did test it on real nodes and it worked as expected as before the small refactor15:41
kubajjso probs can do after the move15:41
kubajjthanks15:42
JayFI'll tell you what, I'll drop down to a +1 for now until you confirm you tested this version on real hardware or add unit tests to increase your confidence :)15:42
kubajjJayF: we already tested it 😉15:44
kubajj(it worked the same as before the refactor, might have confused you with the wording)15:45
JayFoh, your statement was more "worked as expected [same] as before the small refactor" not "worked as expected before the small refactor"15:45
kubajjJayF: by small refactor I meant what Dmitry suggested - splitting functions as they were too huge. I would not call this -206 +1440 a small refactor :D15:46
JayFahh15:46
JayFyou know how much IPA code these days is raid code?15:46
JayFapproximately all of it :P 15:46
kubajjJayF: sorry, the person responsible is sitting a couple of offices away from me and is currently the boss of the boss of my supervisor 😉15:47
kubajj(he also got me into OpenStack, so am not complaining)15:47
JayFhehehe it's not a bad thing, it's just a thing that was mildly surprising that I found when doing image security stuff15:48
dtantsurEverything that is not partition images handling is RAID code15:51
JayFa lot of that image handling code was unified during the security stuff15:59
JayFa lot of it could be unified further tbh15:59
cardoeWho let it be Wednesday already?16:52
JayFhttps://review.opendev.org/q/topic:%22ironic-releases-2025.2%22 one of our release managers must +1 these cc iurygregory rpittau 17:10
JayFI just updated it to get the recent api and wsgi bugfixes17:10
opendevreviewMerged openstack/ironic master: Fix nexthop error when adding route to PUBLIC_SUBNET_IP  https://review.opendev.org/c/openstack/ironic/+/96029918:33
iurygregoryJayF, will look in a bit19:29
iurygregorytks19:29
clifI realize the release cycle is in full swing so I'm not expecting a full review but if someone could take a look at how I'm propogating changes from a portgroup to its constituent ports I'd appreciate it: https://review.opendev.org/c/openstack/ironic/+/955625/comment/50a04612_fe429db3/20:19
clifin short: what's the most appropriate way to accomplish this?20:20
JayFI looked at this with Clif and our usage of RPC calls versus direct object calls in that layer is inconsistent20:37
JayFSo I too am now curious why do one way or why do the other way20:37

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