Tuesday, 2023-03-07

vanougood morning ironic00:27
jlvillalTheJulia, Thanks. That's confusing for my little brain :D00:34
vanouJayF: How about communication with OpenStack vul team?02:41
kaloyankmorning everyone o/06:21
kaloyankdtantsur: yes, it looks like it's working, I tested in last night06:22
rpittaugood morning ironic! o/08:56
opendevreviewHarald Jensås proposed openstack/metalsmith stable/yoga: list_instances - cache allocations  https://review.opendev.org/c/openstack/metalsmith/+/87667109:05
opendevreviewHarald Jensås proposed openstack/metalsmith stable/xena: list_instances - cache allocations  https://review.opendev.org/c/openstack/metalsmith/+/87667209:06
opendevreviewHarald Jensås proposed openstack/metalsmith stable/wallaby: list_instances - cache allocations  https://review.opendev.org/c/openstack/metalsmith/+/87667309:06
dtantsurkaloyank: nice, thanks for confirming!09:16
kaloyankdtantsur: Thanks for looking into my case09:17
kaloyankon a side note, do you need more information for the missing PXE boot parameters on the Neutron port when fast-track deployment fails?09:18
dtantsura report in storyboard with ironic-conductor logs (if possible) could be a good start09:22
dtantsurI cannot promise to jump on it right away, unfortunately - too many other things to do09:22
kaloyankdtanstur: I'll see to it09:36
opendevreviewDmitry Tantsur proposed openstack/ironic master: Do not recalculate checksum if disk_format is not changed  https://review.opendev.org/c/openstack/ironic/+/87659510:57
dtantsurkaloyank: the final version of the fix ^^10:57
dtantsurI had to adjust the code for non-glance images10:58
kaloyankThanks, I'll update the patch11:17
kaloyankOK, another question: When cleaning a node with fast-track, why do we remove the cleaning port from Neutron after the node moves to "available" state? The node is still powered on and still has an IP assigned by Neutron11:32
kaloyankLogs https://pastebin.com/XmxXALDa ^^11:33
iurygregorymorning Ironic11:47
kubajjmorning iurygregory 12:51
timeuquit13:13
mnasiadkaTheJulia: I was able to run the upgrade through to Yoga based on your patch - thanks again :)13:25
dtantsurkaloyank: it's a bit of a grey area. Theoretically, it's wrong to keep the cleaning port when cleaning is not running.13:41
dtantsurWorst case, you're going to exhaust the cleaning subnet with ports that correspond to available nodes13:42
dtantsurThere is also a question of when to delete it.13:43
rpittauif any core has a moment please check a small fix for bifrost CI https://review.opendev.org/c/openstack/bifrost/+/87263413:43
kaloyankdtantsur: well since I share the cleaning subnet with instances running, sometimes there are IP conflicts because Neutron hands out IP addresses that are already assigned to alive IPAs13:47
kaloyankI was thinking that it may be useful to "switch" from the cleaning network to the provisioning network and leave it as it if it's the same Neutron subnet13:48
dtantsurSwitching means re-creating the port, so it may receive a different IP anyway?13:49
kaloyankit most certainly will, I'm not exactly familiar but the IPA should update it's callback URL once it has the new IP address13:50
dtantsurupdating callback URL is explicitly forbidden (I think the reason was to minimize a possibility of hijacking the agent - TheJulia will remember).13:56
dtantsuryou'll need to reboot the node using the ironic API. at which point the value of fast-track is questionable..13:56
kaloyankI see.. So it only makes sense to retain the port if the cleaning subnet is the same as the provisioning?14:00
kaloyankand callback URL is the URL the agent is available at or I'm mistaken?14:00
TheJuliagood morning14:01
kaloyanko/14:03
opendevreviewMerged openstack/ironic bugfix/21.2: Fixes for tox 4.0  https://review.opendev.org/c/openstack/ironic/+/87640914:10
TheJuliamnasiadka: awesome! That is the best news!14:10
TheJuliaYeah, it was to prevent a man in the middle attack14:11
opendevreviewMerged openstack/ironic bugfix/21.2: Update .gitreview for bugfix/21.2  https://review.opendev.org/c/openstack/ironic/+/86782614:12
TheJuliaI guess code could be added around port changes to permit updating the callback URL14:12
TheJuliaOne thing I have been thinking about is supporting multiple callback urls14:12
TheJulia... Since most physical machines have multiple interfaces in various networks14:13
TheJuliakaloyank: I think your base question is worthy of discussion during the PTG, would you be willing to join and discuss ?14:17
kaloyankTheJulia: I'd love to, two questions: What's a PTG and when is it held?14:19
TheJuliakaloyank: https://openinfra.dev/ptg/14:19
TheJuliaMarch 27-31st, virtual this time around14:19
TheJuliaOur etherpad of discussion topics https://etherpad.opendev.org/p/ironic-bobcat-ptg14:20
TheJuliakaloyank: there is a similar topic down by line 72 on that etherpad. Honestly I think the topic your looking for is more along the lines of "can we make fast track work with neutron integrated usage"14:25
kaloyankTheJulia: found it, I'll read thoroughly in a bit :)14:26
TheJuliakaloyank: I added thoughts, please feel free to add/change what I wrote14:31
dtantsurmeanwhile, https://review.opendev.org/c/openstack/ironic/+/876595 is ready for review14:31
TheJuliadtantsur: sure, I just need to send a board related email first which will take me a few minutes14:33
opendevreviewDmitry Tantsur proposed openstack/ironic bugfix/21.2: Do not move nodes to CLEAN FAILED with empty last_error  https://review.opendev.org/c/openstack/ironic/+/87617414:54
TheJuliaAlways fun when you get to go dig through bylaws first thing in the morning14:57
TheJuliadtantsur: reviewed, +2 although two comments one likely just informational for another reviewer15:03
dtantsurthx!15:05
opendevreviewMerged openstack/bifrost master: Finally fix jinja[spacing]  https://review.opendev.org/c/openstack/bifrost/+/87263415:22
kaloyankTheJulia: I updated the issue description15:27
opendevreviewJulia Kreger proposed openstack/ironic master: Fix online upgrades for Bios/Traits  https://review.opendev.org/c/openstack/ironic/+/87662616:51
rpittaugood night! o/16:58
kaloyankgood night everyone o/17:42
opendevreviewJulia Kreger proposed openstack/ironic master: add default conductor group capability  https://review.opendev.org/c/openstack/ironic/+/85570518:06
jlvillalMaybe dumb question. If I do an `lsblk` should I see a partition for the configdrive on a deployed system?18:08
jlvillalReal reason I'm asking. My SSH key isn't getting added to the system and I'm trying to figure out why...18:10
JayFjlvillal: I believe so, yes.18:19
JayFjlvillal: that's how cloud-init works, it looks for it and mounts it up and gets the data out18:19
JayFjlvillal: so you can totes interact w/config drive using stnadard linux block tools18:20
jlvillalJayF, Thanks. I don't seem to see one. Thus why I am confused...  But would make sense why the SSH keys aren't being added.18:20
JayFI'd check conductor logs and see if it appears to be picking up a config drive at all 18:28
jlvillalThanks18:29
JayFiurygregory: rpittau: TheJulia: Is there any reason you all know of I should not approve the releases to cut 2023.1 branches for all Ironic stuff right now?19:07
JayFI guess 876626 would be good to get in19:08
JayFalthough we could backport it19:08
JayFI just +2'd 876626, someone could land it and I'll update that change req19:09
* iurygregory looks 19:11
iurygregorylet's get 876626 in19:12
kubajjJayF, TheJulia: sorry for bothering you, but have you managed to have a look at the email? there is still no rush, but don't want to forget about it and leave it to the last mine.19:13
iurygregoryat least we save some CI resources =)19:13
JayFkubajj: you should be bothering me, yikes, I'm so sorry19:13
JayFiurygregory: you landing it? 19:13
JayFkubajj: I'm going to go take care of it right now19:13
iurygregoryjust +W 87662619:13
iurygregorywe can probably land https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/876361  and update https://review.opendev.org/c/openstack/releases/+/87661119:17
iurygregoryhttps://review.opendev.org/c/openstack/releases/+/876571 we are good to go19:18
iurygregoryfor bifrost I saw some patches, so we can probably wait and update I would say19:19
iurygregoryfor ironic we need to wait and update virtualpdu I think? 19:24
TheJuliakubajj: sorry, forgot. Things have been chaos :(19:26
TheJuliaJayF: afaik no as long as the commit hash lines up with something not weeks ago  19:27
jlvillalJayF, I figured out why `lsblk` didn't show the partition. I had sshed into the wrong system. Duh! :(  But now to figure out why the SSH keys didn't get added to the authorized_keys file...19:34
JayFjlvillal: did the correct one at least have the configdrive?19:42
jlvillalJayF, Yep.19:42
JayFif that has your key, it's a cloud-init issue19:42
JayFwhich is an entire world of pain I'm lucky enough not to have scoped into my life 19:43
JayFalthough if it breaks when looking for a BM configdrive, it is still my problem :|19:43
jlvillalHehe. Yeah. I've done it before and I always get confused. Since I only dig into it like once a year and forget everything the next time I need to do something.19:43
stevebaker[m]hey, does anybody know the package which provides tgt on recent centos? It hasn't been scsi-target-utils since centos720:10
JayFin Gentoo, it's literally sys-block/tgt20:11
JayFmaybe it split into it's own package in RH-land?20:11
stevebaker[m]oh, its not a thing since centos8. I'm including the ramdisk element, which ironic-python-agent-builder doesn't actually use20:23
JayFif we want https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/876361 in antelope, someone needs to W+1 it nowish... TheJulia you have a sec?20:38
JayFor stevebaker[m] 20:38
JayFI approved all release requests, some needed a small update, except Ironic (waiting for 876626 to land) and tempest plugin (hoping someone looks at dtantsur's change so we can get it in pre-branch)20:39
stevebaker[m]done20:40
JayFthanks steve!20:42
kubajjJayF: thanks20:45
kubajjTheJulia: no worries20:45
opendevreviewMerged openstack/ironic master: Fix online upgrades for Bios/Traits  https://review.opendev.org/c/openstack/ironic/+/87662620:57
opendevreviewMerged openstack/ironic master: Add missing include for inventory API reference  https://review.opendev.org/c/openstack/ironic/+/87494620:57
JayFAight, updating the ironic one21:02
JayFwe're going to have a stack! of opens! 21:02
JayFaight, Ironic release signed off on21:05
JayFjust gotta watch 876361 and get tempest21:05
JayFand we've stacked an open21:05
JayFdtantsur: rpittau: I'm trying to get https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/876361 in before https://review.opendev.org/c/openstack/releases/+/876611 lands. It's about to fail the gate. Can one or both of you own ensuring it 1) gets in and the releases PR is updated+approved or 2) is broken and we release without it21:59
iurygregoryJayF, also for ironic, we need the updates in the code to cut the release22:00
JayFiurygregory: what do you mean?22:00
opendevreviewVerification of a change to openstack/ironic-tempest-plugin master failed: Split the ramdisk ISO test  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/87636122:00
JayFiurygregory: I did the release notes prelude; what else needs to be done?22:01
iurygregoryhttps://docs.openstack.org/ironic/latest/contributor/releasing.html#things-to-do-after-releasing22:01
* JayF didn't recall doing anything extra last release, but you might have JFDI22:01
JayFiurygregory: that's after, yeah? not before?22:01
iurygregoryohhh right (in the past we did the release mappings before cutting it I think)22:03
JayFhonestly, you wanna help out with taking care of that?22:03
JayFotherwise I'll probably end up doing it on an airplane lol22:03
* TheJulia waits for unit tests to spin making a "whirrrrrrrrrrrrrrrrl" sound22:23
JayFTheJulia: what's the thing I need? I saw the -1 on the releases pr22:30
TheJuliaoh jebus, the 2023.1 crap breaks it22:31
TheJuliahttps://www.irccloud.com/pastebin/huYQoMUH/22:31
JayFTheJulia: we also need to update that comment on Ln544, we need to worry about SLURP now too22:33
TheJuliaso since antelope is not the actual named release anymore, it is 2023.1, I guess we justdrop the test?22:33
TheJuliakeep yoga around?22:34
JayFI gotta be honest, I know what this code is for in theory but I don't know how to exercise it22:34
JayFTheJulia: I know that we'll need to keep zed when we cut 2023.2; I'm not sure about yoga now22:34
JayFTheJulia: the simpler answer for us as a project is probably to just leave the extra at all times22:34
TheJuliayeah22:34
TheJuliaagree22:34
JayFso is this what gets called if, e.g., ironic-dbsync 2023.1 ? 22:35
JayFlike I'm trying to determine where the release version slug gets input from a user22:35
TheJuliaso, it is version mapping for objects if they need translation or not22:35
TheJuliaretesting....22:37
JayFwe could fix the sorting22:37
JayFhttps://github.com/openstack/ironic/blob/master/ironic/common/release_mappings.py#L554 could have a specified list of openstack versions that get sorted in first22:38
JayFidk; I trust you to handle this I'm going to point my brain elsewhere unless you need it22:38
TheJuliak22:38
TheJulia    AssertionError: Versions (21, 1) and (21, 4) are not sequential22:38
TheJulia... oh22:44
TheJuliaI see what is going on22:44
opendevreviewJulia Kreger proposed openstack/ironic master: Update release mappings for 21.4 release  https://review.opendev.org/c/openstack/ironic/+/87678622:52
iurygregorynow we will add 2023.1 and Antelope? O.o22:52
TheJuliawell, so technically it needs to match out to the branch name22:53
TheJuliabut people are going to get things mixed up no matter what22:53
TheJuliaso better to do both I think22:53
TheJuliajayf ^22:54
JayFI don't object22:54
JayFbut again, I don't fully understand when/where an operator would input this slug22:54
TheJuliaironic.conf to pin out versions22:54
TheJuliaone minute22:55
JayFyeah, so you pin the objects to the previous release22:55
JayFstart upgrading22:55
JayFremove the pin, yeah?22:55
JayFfor rolling upgrades22:55
TheJuliayeah22:55
JayFyou shook the dust free 22:55
TheJuliapin_release_version22:55
iurygregoryI'm ok with this approach =)22:56
TheJuliaThen +2+A's seem in order if there are no issues22:57
JayFin this same vein; it doesn't matter if the release_mappings are in place correctly for bugfix releases22:57
JayFbecause the cat is already out of the proverbial bag there22:57
TheJuliayou can run the version just fine22:57
JayFbut we should still be doing it22:57
TheJuliait is when you go to upgrade22:57
JayFspecifically a rolling upgrade22:57
TheJuliaany upgrade, the new version needs to know about the mappings22:58
TheJuliathe issue is we break the master branch immediately upon release if we don't do the mappings before the overall cycle stable branch22:58
JayFI'm saying, in your change, I suspect e.g. the node wasn't that version when 21.2 was cut22:58
TheJuliaJayF: I literally went to the bugfix branches and copied out the "master" state22:58
JayFI shoulda known you'd leave no i undotted22:59
JayFiurygregory: you wanna +2A https://review.opendev.org/c/openstack/ironic/+/87678622:59
* TheJulia thinks that is a compliment :)22:59
JayFwell you're literally cleaning up details that I think, with my PTL hat on, I was responsible for23:00
JayFhaving a higher attention to detail than me is not super difficult :D lol 23:00
iurygregoryJayF, doing now =)23:00
* TheJulia shrugs, it is a team effort23:00
JayFsure, but I wish there was a J in team :P23:00
TheJulia... Unfortuantely I don't have a grumpy cat to live stream at you for that ;)23:01
JayFI have a grumpy dog and a grumpy cat, my AI made them :D 23:01
TheJuliaanyhow, I think I'm going to call it a day, my brain is hello23:01
JayFyou got to meet them yesterday lol23:01
TheJuliahehehehe23:01
TheJulias/hello/jello/23:01
JayFcase-in-point 23:02
JayFhave a nice day :D see you tomorrow or Thurs :D 23:02
TheJuliao/23:03

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