Friday, 2025-08-08

alegacyfrickler:  thank you ... I moved my VM to a CentOS 10 stream image.  Only had to remove "sgabios-bin" from the require package list since it doesn't seem to exist.  Not sure of the side effect yet, but install worked which is better than what I had earlier... will continue with enroll/deploy tomorrow.00:58
opendevreviewOpenStack Proposal Bot proposed openstack/ironic-ui master: Imported Translations from Zanata  https://review.opendev.org/c/openstack/ironic-ui/+/95685203:41
opendevreviewcid proposed openstack/ironic master: Handle race conditions in power state changes  https://review.opendev.org/c/openstack/ironic/+/95667404:19
opendevreviewTakashi Kajinami proposed openstack/networking-generic-switch master: etcd: Discover api version automatically  https://review.opendev.org/c/openstack/networking-generic-switch/+/95433104:50
opendevreviewMerged openstack/networking-generic-switch master: Replace LOG.warn  https://review.opendev.org/c/openstack/networking-generic-switch/+/95305605:13
adam-metal3rpittau, I have reviewd the ironic-image release and your PRs have been merged, and yes I think release 31 is safe and sound. Where this brokennes have effect is the main PR tests and periodics, I can clean up quay.io and retag an older main so CI will be happy again05:17
rpittauhappy friday ironic! o/07:13
rpittauadam-metal3: thanks! Yeah, no impact for the release07:13
rpittaualegacy: it's not possible to run bifrort on centos9, or better, we tried hard and we failed because of system limitations and libraries conflicts07:15
rpittauSorry, to run bifrost on cs9 using a different python than system python 07:15
rpittaualegacy: this is our tentative https://review.opendev.org/c/openstack/bifrost/+/94944907:19
rpittaualegacy: bifrost on CS10 runs well, I have a patch to support that officially, just need to clean it up before submitting it07:20
rpittauthe only thing is the hardware limitations, we can't run CI in all nodes07:20
rpittauTheJulia: I was also looking into modifying the m3job to increase node specs, mainly because I realized that for some reason the UEFI based deployment seems to require more resources, thanks for also looking into that :)07:21
queensly[m]Good morning o/ Happy Friday :)07:38
dtantsurrpittau: any code changes required for CS10? I wonder if we could backport it to the previous stable branch to support at least some upgrades (and get back upgrade testing)11:01
rpittaudtantsur: for bifrost you mean? I need to double-check11:02
rpittauI'll try to get to that next week11:02
dtantsurthx11:02
TheJuliabrraaains12:59
dtantsurI don't have any, sorry :)13:06
opendevreviewJulia Kreger proposed openstack/ironic master: ci: move metal3 job to larger memory node  https://review.opendev.org/c/openstack/ironic/+/95689113:07
TheJuliarpittau: added you to ^13:09
TheJuliaalegacy: makes sense, at least to me that sgabios-bin is gone, since it is serial graphics adapter bios blobs and maintainers are moving hard to eraidicate bios booting in centos 1013:12
rpittauThanks TheJulia :)13:12
TheJuliagiven the my squashed patch of the eventlet stuff, are folks good if I stack it all up with a change to disable metal3-integration to merge the patches in their present sequence, and then re-enable the job voting afterwards. Given the run doesn't operate with the entire stack of changes, it sort of becomes problematic until they actually the only patch on top of master13:14
dtantsurI guess it is what it is13:19
dtantsurLet's just make sure everything merges rather quickly13:19
iurygregory++13:20
TheJuliaYeah, that is my hope as well13:21
TheJuliarpittau: I don't know if you saw my note about metal3-integration only appears to apply latest ref on top of master branch. I'm not sure the best way to fix that but just wanted to make sure someone else was aware13:22
TheJuliaWell, I think the plan then basically becomes recheck the squash patch with the larger node set just to verify then to restack everything with disable/re-enable changes13:28
opendevreviewJulia Kreger proposed openstack/ironic master: DNM - Test change for Metal3 for threading changes  https://review.opendev.org/c/openstack/ironic/+/95682013:28
opendevreviewDmitry Tantsur proposed openstack/sushy-tools master: Add SUSHY_EMULATOR_VIRTUAL_MEDIA_IP_FAMILY environment variable support  https://review.opendev.org/c/openstack/sushy-tools/+/95690413:35
opendevreviewJulia Kreger proposed openstack/ironic master: ci: grenade: restart neutron-rpc-server  https://review.opendev.org/c/openstack/ironic/+/95680113:36
rpittauTheJulia: interesting.... anyway, sounds good to me13:56
TheJuliarpittau: yeah, the indirection api change passed metal3-integration just fine, and then I saw it ran with eventlet and I was like "oh!"13:59
TheJuliawhen 2 changes before removed eventlet....13:59
JayFrpittau: cardoe: iurygregory: Please -1 https://review.opendev.org/c/openstack/governance/+/956917 to ensure Ironic remains DPL :) 14:58
rpittauJayF: yeah, my brain was telling me something about that last week :D14:59
cardoedone15:14
TheJuliaas a general FYI, the squashed threading+indirection changes worked for metal316:31
TheJuliathe ironic log: https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_c97/openstack/c97a3a29a5c74e5f8f30bb86d090f571/controller/before_pivoting/ironic.log16:31
JayF\o/16:34
opendevreviewMerged openstack/ironic master: ci: move metal3 job to larger memory node  https://review.opendev.org/c/openstack/ironic/+/95689117:31
opendevreviewNahian Pathan proposed openstack/sushy master: Support expanded Chassis and Storage for redfish  https://review.opendev.org/c/openstack/sushy/+/95521117:32
opendevreviewNahian Pathan proposed openstack/sushy master: Support expanded Chassis and Storage for redfish  https://review.opendev.org/c/openstack/sushy/+/95521117:37
JayFI know it's early, but has anyone created a ptg etherpad yet?17:38
opendevreviewJulia Kreger proposed openstack/ironic master: Replace GreenThreadPoolExecutor in conductor  https://review.opendev.org/c/openstack/ironic/+/95293917:59
opendevreviewJulia Kreger proposed openstack/ironic master: Set the backend to threading  https://review.opendev.org/c/openstack/ironic/+/95368317:59
opendevreviewJulia Kreger proposed openstack/ironic master: Remove direct mapping from API -> DB  https://review.opendev.org/c/openstack/ironic/+/95651217:59
opendevreviewJulia Kreger proposed openstack/ironic master: Optional indirection API use  https://review.opendev.org/c/openstack/ironic/+/95650417:59
opendevreviewJulia Kreger proposed openstack/ironic master: Clean-up misc eventlet references  https://review.opendev.org/c/openstack/ironic/+/95563217:59
opendevreviewJulia Kreger proposed openstack/ironic master: ci: temporary metal3 integration job disable  https://review.opendev.org/c/openstack/ironic/+/95695217:59
opendevreviewJulia Kreger proposed openstack/ironic master: Revert "ci: temporary metal3 integration job disable"  https://review.opendev.org/c/openstack/ironic/+/95695317:59
TheJuliaJayF: afaik, no17:59
JayFty18:00
TheJuliaI've tagged the eventlet removal items with ironic-week-prio18:18
TheJuliaand added a procedural block on the start of the stack, but that doesn't mean folks should ignore them18:18
JayFmakes sense as ideally we'd drop that whole stack in one shot18:19
TheJuliathat is my plan18:21
alegacy_The new local-rpc changes that merged recently seem to be assuming that there would not be any other type of RPC API being used.  It's messing with the username/password in conf.json_rpc (amongst other settings) which is breaking RPC communication to the networking service which is using whatever username/password that bifrost initially created.  18:49
alegacy_I guess a more fundamental question, since even without this it is sort of assumed that all RPCs would be configured the same way, should each RPC client have its own settings in the conf file and somehow instantiate an RPC client unique to its own settings?18:49
guilhermespdtantsur:  alright i got your pr in19:09
guilhermespprogress?19:09
guilhermesp{"level":"info","ts":1754680113.0709114,"logger":"provisioner.ironic","msg":"found error","host":"metal3~fb10933","msg":"Deploy step deploy.prepare_instance_boot failed: Failed to install a bootloader when deploying node 5eac4993-5103-4c3d-b66d-188c1e48fc8b: Could not configure UEFI boot on device /dev/md126: Unexpected error while running command.\nCommand: sgdisk -F /dev/md/imsm\nExit code: 2\nStdout: ''\nStderr: 19:09
guilhermesp'Problem opening /dev/md/imsm for reading! Error is 2.\\nThe specified file does not exist!\\n'"}19:09
TheJuliaalegacy_: unique with it's own settings is likely best19:49
TheJuliauhh /dev/md/imsm what?!19:49
guilhermesplol yeah i dont know what that is 19:54
alegacy_TheJulia: ...ok, i'll try to refactor common/json_rpc/client.py a bit so that the whole config/client bits don't have to be outright duplicated.  19:58
TheJuliaguilhermesp: same.... no clue.19:59
guilhermespyeah, in any case, i have a spare node here to keep testing things. I know dtantsur asked to collect ramdisk logs but i didnt get to this part of catching the tar logs for that box once it fails, i might figure that on monday 20:04
guilhermespbut since i have ppl pushing me to get those beautiful boxes deployed im just deploying them on single disk and then try a software raid conversion when the node is live 20:05
TheJuliaguilhermesp: fun! :(20:15
opendevreviewJulia Kreger proposed openstack/ironic master: Fix the ability to escape service fail  https://review.opendev.org/c/openstack/ironic/+/95697221:38
TheJuliajanders: please test ^21:43
FreemanBoss[m]Please anyone willing to attend OpenInfra Summit Europe (Paris) here?22:30

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