Tuesday, 2023-05-16

NobodyCamanyone happen to know if Ramdisk deploy interface works with nova?00:21
JayFI can't forsee a reason why not, but I've not personally tested it00:29
*** eandersson15 is now known as eandersson02:08
opendevreviewPierre Riteau proposed openstack/bifrost stable/2023.1: Fix ansible-lint  https://review.opendev.org/c/openstack/bifrost/+/88311903:41
rpittaugood morning ironic! o/06:46
TheJuliaGood night!07:55
dtantsurJayF: I don't think I have any of my lp dashboards still up, but I can look into that.08:10
genekuostevebaker: DIB_RELEASE=bullseye disk-image-create -t raw -o debian-bullseye -p mdadm vm block-device-efi debian08:49
genekuoI do modify this line to add mdraid1x to grub modules08:51
genekuohttps://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/bootloader/finalise.d/50-bootloader#L28608:51
Sandzwerg[m]Hmmm question regarding the hardware burn-in. Are they executed on a specific state change like managed -> available or also on every cleaning?11:28
iurygregorygood morning Ironic11:43
dtantsurSandzwerg[m]: I think it's designed to run on manual cleaning (manageable -> (clean) -> manageable)11:55
Sandzwerg[m]hmkay from the documentation it's not clear to me when it runs: https://docs.openstack.org/ironic/latest/admin/hardware-burn-in.html12:01
JayFdtantsur: honestly, I was just hoping you had the code still13:17
opendevreviewMerged openstack/ironic bugfix/21.0: Handle MissingAttributeError when using OOB inspections to fetch MACs  https://review.opendev.org/c/openstack/ironic/+/88252613:17
dtantsurJayF: I probably have it somewhere on github..13:18
dtantsurJayF: https://github.com/dtantsur/ironic-bug-dashboard13:25
* TheJulia tries to wake up now14:16
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298515:26
TheJuliaSandzwerg[m]: clean steps, look for "Then launch the test with"15:39
TheJuliaso manual cleaning, specifically15:39
TheJulia... or I guess in deploy templates if the burnin steps are so decorated in the agent15:40
TheJuliagenekuo: hmm, I guess debian dosn't have signed artifacts for EFI boot?15:41
rpittaubye everyone, see you next week! o/15:52
TheJuliao/15:58
genekuoTheJulia: Do you mean secure boot? It's not enabled in my env.16:27
TheJuliawell, so the conundrum here is grub-install prevents UEFI loader building in newer versions because the grub maintainers want people to be able to use secure boot16:28
TheJuliawhich means a signed shim and all16:29
TheJulia(and well, signed efi binaries)16:29
TheJuliabut the path missing is kind of telling16:29
TheJuliagenekuo: find /boot/EFI might be helpful context wise16:29
genekuo /boot/efi/EFI/debian is missing in the image, but after I ran grub-install on the deploy host it appears.16:39
genekuoGuess that may be the issue16:39
TheJuliayup, that would be it16:39
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298516:44
TheJulia... I guess it is missing in the original base image? Are there any other folder in /boot/efi/EFI ?16:45
TheJulias/Are/Is/16:45
JayFdtantsur: any idea the last python version that worked on? 3.8 appears to be nonworking16:45
genekuoSorry my mistake, it's in the image.16:45
dtantsurJayF: oh, a great question.. could be even 2.716:45
JayF:-|16:46
JayFaight16:46
JayFdtantsur: any config required that you can remember?16:46
JayFdtantsur: it seems to be trying to work w/o any...16:46
JayFdtantsur: tox.ini had basepython=python3 so it's not 2.7 bad16:46
dtantsurmy brain is completely blank, sorry16:47
JayFnot a problem :) I'll try to poke it until I figure it out16:47
NobodyCamgood morning OpenStack Folks16:50
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298516:51
TheJuliao/ NobodyCam 16:51
NobodyCamo/ TheJulia 16:51
genekuoTheJulia: It seems like efiboot is set to \EFI\BOOT\BOOTX64.EFI instead of \EFI\debian\grubx64.efi17:00
TheJuliaokay17:01
TheJuliaso... the first value is the expected x86_64 default file path17:01
TheJuliathe latter is the vendor preferred path17:01
TheJuliaso, I guess the question is does EFI17:02
TheJuliaerr17:02
genekuoI'm testing if boot works with "\EFI\debian\grubx64.efi" path17:02
TheJuliaEFI\BOOT\BOOTX64.EFI has the necessary code embedded17:02
genekuoI guess there some issue with the code (probably referring to the wrong prefix for grub to load). And rerunning grub install fixed the issue.17:05
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298517:05
genekuoCause after rerunning grub-install the EFI boot file is still EFI\BOOT\BOOTX64.EFI17:05
genekuoIs it possible to let IPA not reboot after deployment for debugging purpose?17:11
TheJuliagenekuo: set it to maintenance mode while it is running the deployment17:20
TheJuliapreferably *while* it is writing the disk image17:20
TheJuliathat will likely block the bootloader from installing though :\17:21
* TheJulia used to do this by short circuiting the conductor intentionally17:21
JayFfirewall off the bmc from ironic during the install ;) 17:21
JayFprobably not an actual good suggestion, but might get the behavior you seek17:22
genekuoThanks for the suggestions :)17:38
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298517:57
opendevreviewJulia Kreger proposed openstack/ironic master: CI: Mark BFV job non-voting for now  https://review.opendev.org/c/openstack/ironic/+/88329618:19
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298519:05
TheJuliaI'm feeling good about ^, but my hopes are ~35 minutes from being dashed19:06
JayFfixing bfv jobs after triple OT 19:20
JayFimpressive :P 19:20
JayFI usually pick easy things for the morning of a late hockey 'hangover' LOL19:20
TheJuliacloser...19:44
TheJuliahttps://www.irccloud.com/pastebin/0XMc4F5X/19:44
JayF🤞19:47
iurygregory🤞19:47
iurygregorygrenade job is still broken right?19:54
iurygregoryat least I saw TIMED_OUT in some runs 19:55
TheJuliaso, looks like we'll need to do some additional checks, we get a different failure now with cinder19:55
iurygregoryso I think this is a good sign?19:59
TheJuliakind of20:01
TheJuliaerr, no, same error20:03
TheJuliaerr, too many windows20:05
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298520:16
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298521:25
genekuostevebaker: I did find /boot/efi/debian/grubx64.efi in the image, but it seems to be built incorrectly, probably pointing to the disk when image is built instead of the disk after installation.21:37
NobodyCamany one happen to know if `Baremetal node deploy` will build the pxe cfg file 21:41
TheJuliaNobodyCam: if your using ramdisk deploy, yes21:44
NobodyCamhummm :(21:45
TheJuliaunder normal circumstances, if your doing a non-ramdisk deploy, it will populate the config for ramdisk booting21:45
TheJuliaerr21:45
TheJuliasorry, I mean, under normal non-ramdisk deploys, a configuration is still generated21:45
TheJuliabut that config is generally for the agent21:45
TheJuliaunless post-deploy21:45
TheJuliaNobodyCam: not sure why that would be an issue21:48
NobodyCamoh21:55
NobodyCamI think I see21:55
NobodyCamits the pxe conf file22:02
NobodyCamgoto boot_ramdisk22:02
NobodyCamI have no boot_ramdisk stanza :'(22:02
TheJuliawhat version of ironic?22:03
TheJuliawhat boot_interface?22:03
NobodyCamramdisk for interface , ussuri22:04
TheJuliaramdisk is deploy_interface22:06
TheJulianot boot_interface22:06
TheJuliahttps://github.com/openstack/ironic/blob/stable/ussuri/ironic/drivers/modules/ipxe_config.template#L34 <-- the base template22:06
TheJuliafrom ussuri22:06
TheJuliafor ipxe22:06
NobodyCam:doh22:07
NobodyCamipxe22:08
TheJuliaso unless your carrying your own base pxe template....22:08
NobodyCamyep 22:09
NobodyCamthat's it22:10
TheJuliatechdebt == fun22:10
TheJulia:(22:10
NobodyCamheheheh22:11
* TheJulia wonders.... if the long tempest run is a good sign, or a bad sign22:27
opendevreviewMerged openstack/ironic master: CI: Mark BFV job non-voting for now  https://review.opendev.org/c/openstack/ironic/+/88329622:27
JayFTheJulia: ^ that's the best possible sign you fixed it22:27
JayFlol22:27
TheJulianormally ~45 minutes22:28
TheJuliawe're approaching an hour I think22:28
TheJuliabut it could just be a slow node22:28
TheJuliatempest run in that one was ~4 minut4s22:30
TheJuliawe're at 20 now22:30
JayFI was just making a joke; you'd fix the job shortly after the -nv lands22:31
TheJuliain accordance with the prophecy22:33
genekuostevebaker: here's what I get from the working debian nodes22:50
genekuohttps://paste.opendev.org/show/bBpuoXsXZiUExWA4j0qt/22:50
TheJuliaand it finally exited tempest22:50
TheJuliagenekuo: are they the same file?22:50
genekuoI believe the EFI application is pointing to the wrong disk causing the issue22:50
TheJuliait depends on what the grub binaries get built with actually22:51
TheJulia(These are the most fun issues, btw)22:51
TheJulia((I'm being sarcastic)22:51
TheJulia)22:51
genekuoTheJulia: They are different, currently the boot option is using BOOTX64.efi22:52
TheJuliais shim an installed package?22:53
genekuoNo, it's not22:56
TheJuliaI guess that makes sense22:57
TheJuliazigo: does debian not have a stock signed binary? is it always built?23:00
TheJuliahttps://packages.debian.org/bullseye/amd64/grub-efi-amd64-bin/filelist shows some monolithic binaries23:01
TheJuliaAnyway, regardless, the standard pattern is to load grub.cfg from the same file as the binary23:03
TheJuliawe lean towards BOOTX64.EFI because it is standardized23:03
TheJuliaand if there is no loader csv hint file, we would end up with that as the default. 23:03
genekuoI don't think chain loading is the issue though, it seems like the efi file is loading grub from a unknown disk23:06
genekuoHere's the different I found in BOOTX64.efi from extracting strings from binary23:06
genekuohttps://paste.opendev.org/show/belHDo8rTVax0DgwpdEc/23:06
TheJuliaokay, then it is the stock binary doesn't have what is needed23:12
TheJuliaso the incoming image needs to have the appropriate bits then to find it23:12
genekuostevebaker: Both BOOTX64.efi and grubx64.efi is set to look up grub from /boot/grub23:28
genekuoI'm not sure if this is the behavior when not enabling secure boot23:28
genekuoOther nodes not using software RAID also don't have grub.cfg in /boot/efi/EFI/debian23:32
genekuoThey are located in /boot/grub23:32
TheJuliawell, at least it is detectable, I guess23:37
opendevreviewJulia Kreger proposed openstack/ironic master: WIP bfv service change  https://review.opendev.org/c/openstack/ironic/+/88298523:39
genekuostevebaker: I see, (,gpt3)/boot/grub seems to work without software RAID, but with software RAID it might have to specify mduuid. I reach out to debian community and see if this is the expected behavior 23:45
TheJuliainteresting... I'm not seeing stevebaker's comments in irccloud23:47
genekuoIt might because the message is too long23:49
TheJulianah, dunno though.23:51
TheJuliaI'm out of spoons for the day23:51

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