Wednesday, 2021-07-07

*** pmannidi is now known as pmannidi|AFK01:36
*** pmannidi|AFK is now known as pmannidi|Away02:45
*** pmannidi|Away is now known as pmannidi|AFK02:50
*** pmannidi|AFK is now known as pmannidi|Away02:50
*** pmannidi|Away is now known as pmannidi|AFK02:50
*** pmannidi|AFK is now known as pmannidi|Away02:50
*** pmannidi|Away is now known as pmannidi|AFK02:54
*** pmannidi|AFK is now known as pmannidi|Away02:54
*** pmannidi|Away is now known as pmannidi|AFK02:56
*** pmannidi|AFK is now known as pmannidi|Away02:56
*** pmannidi|Away is now known as pmannidi|AFK02:56
*** pmannidi|AFK is now known as pmannidi|Away02:56
iury|holidaygood morning janders and Ironic o/05:53
*** iury|holiday is now known as iurygregory05:53
jandershey iurygregory o/05:55
iurygregoryo/05:55
arne_wiebalckGood morning janders iurygregory and Ironic!06:44
iurygregorymorning arne_wiebalck o/06:44
arne_wiebalckTheJulia: thanks, much clearer! I still left some comments :)07:08
jandershey arne_wiebalck o/07:16
jssfrhiho! I’m currently looking hardware inventorization/introspection using the ironic python agent. I note that it exports bmc_address, but not the BMC MAC address, even though that’d be readily available when queried from ipmitool. Is there any specific reason against implementing that? I might provide a patch.07:46
vmud213jssfr: I think it's because we don't really use BMC MAC address07:56
vmud213Most of the times the BMC provides REST API or xmlrpcs or some other mechanism to connect to it. So all that one may need to connect to the BMC is IP, port and some other essential connection properties07:58
jssfrvmud213, aha. My use case would be matching the introspection data with an existing hardware inventory/IPAM thing to automatedly decide what to do with the node (I should’ve mentioned that this is some "undercloud" standalone ironic use case)08:03
vmud213jssfr: Sry i interpreted it wrong way. I got it now. So if you are introspecting, you also expect the BMC MAC and not just the BMC IP. Makes sense to me.08:06
jssfrThanks for your feedback!08:24
arne_wiebalckjssfr: I think it does not hurt to add it (we are using the inventory data as well in some data centre inventory management system). I did not miss the BMC MAC yet, but I don't see a reason not to add it either :)08:35
jssfrI guess I’ll then have to finally figure out the OpenStack contribution process :)08:36
cenne++08:40
dtantsurgood morning ironic! nearly half of the work week is done, right?08:43
arne_wiebalckjssfr: let us know in case you need help with this, the first time can be a little daunting :) 09:06
jssfrthanks! I’m reading through the getting started docs and I guess I’ll play with the sandbox first :)09:08
*** rpittau|afk is now known as rpittau09:42
rpittaugood morning ironic! o/09:42
opendevreviewRiccardo Pittau proposed openstack/sushy stable/wallaby: Fix Processor.sub_processors  https://review.opendev.org/c/openstack/sushy/+/79976210:17
opendevreviewRiccardo Pittau proposed openstack/sushy stable/victoria: Fix Processor.sub_processors  https://review.opendev.org/c/openstack/sushy/+/79976310:18
opendevreviewMerged openstack/sushy master: Add Drive.volumes  https://review.opendev.org/c/openstack/sushy/+/79961211:04
opendevreviewMerged openstack/sushy stable/wallaby: Protect Connector against empty auth object  https://review.opendev.org/c/openstack/sushy/+/79958311:12
opendevreviewMerged openstack/sushy stable/victoria: Protect Connector against empty auth object  https://review.opendev.org/c/openstack/sushy/+/79958411:37
janderssee you tomorrow Ironic o/12:50
rpittaubye janders :)12:52
opendevreviewDmitry Tantsur proposed openstack/ironic master: Bring boot_iso/deploy_iso handling in iLO closer to Redfish  https://review.opendev.org/c/openstack/ironic/+/79969612:59
opendevreviewDmitry Tantsur proposed openstack/ironic master: [WIP] Clean up images when ejecting an ISO with Redfish  https://review.opendev.org/c/openstack/ironic/+/79982013:13
TheJuliagood morning tzumainn 13:22
tzumainnTheJulia, hi!13:22
TheJuliahow goes it?13:23
tzumainnnot too bad!13:24
TheJuliaexcellent13:24
TheJuliaarne_wiebalck: trying to remember, are you on victoria or wallaby?13:52
arne_wiebalckTheJulia: Victoria (for Ironic)13:53
opendevreviewDmitry Tantsur proposed openstack/bifrost master: Allow configuring enabled vendor interfaces  https://review.opendev.org/c/openstack/bifrost/+/79983713:57
opendevreviewJames Denton proposed openstack/networking-generic-switch master: Support multiple links in link_local_information dict of portgroups  https://review.opendev.org/c/openstack/networking-generic-switch/+/55705114:13
opendevreviewDmitry Tantsur proposed openstack/ironic master: Clean up images when ejecting an ISO with Redfish  https://review.opendev.org/c/openstack/ironic/+/79982014:31
dtantsurbfournie: JFYI ^^^14:31
dtantsurah damn, forgot a release note14:32
opendevreviewDmitry Tantsur proposed openstack/ironic master: Clean up images when ejecting an ISO with Redfish  https://review.opendev.org/c/openstack/ironic/+/79982014:35
dtantsur"The `libvirt` module is not importable. Check the requirements."14:46
dtantsurugh14:46
TheJuliaarne_wiebalck: ack14:53
dtantsurokay, so bifrost CI is broken, and I still have no clue why. Help welcome.14:58
rpittaucentos 8 ?15:00
dtantsuryep15:00
opendevreviewMerged openstack/ironic-lib master: Use the json format output of qemu-img info  https://review.opendev.org/c/openstack/ironic-lib/+/79966415:04
JayFI backported (wallaby) that resource provider fix in the nova driver here, https://review.opendev.org/c/openstack/nova/+/799772, if anyone wants to take a look15:07
TheJuliaJayF: thanks, +1'ed :)15:08
arne_wiebalckJayF: we have seen RPs being deleted as well in the past, but did not get round to have a closer look (it is a rare, but happens). IIRC, this was indeed *during* instance deployment. I wonder if that patch would fix the issue for us as well ... I will point our Nova/Placement expert to it, thanks!15:18
JayFIt's in nova xena (master) already15:19
JayFthat's just the wallaby backport, which was direct and clean15:19
dtantsur.. and of course I cannot reproduce it locally ....15:21
arne_wiebalckJayF: Right. I was not aware of that patch at all, maybe my Nova/Placement colleagues are.15:23
JayFoh, yeah, nice15:24
JayFwe were talking abuot it in SPUC along with your reported bug15:24
arne_wiebalckJayF: Our Nova is still on Stein, and the patch is tiny, so it makes sense to have a look if this is our issue.15:24
JayFah, yeah go for it15:25
JayFarne_wiebalck: the ocata-ish version https://gist.github.com/jayofdoom/4fa315489330430ea7aeaa6e8ad62dec if that's easier to forward-port than backporting from master15:25
arne_wiebalckIt has become much better, though. In the past we had situations where *all* was erased under certain circumstances :-S 15:26
arne_wiebalckJayF: oh, cool, thanks!15:26
rpittaudtantsur: are you using python 3.6 locally ?15:27
dtantsurrpittau: 3.6.8, yes15:28
dtantsursame as in the CI, I would expect?15:28
TheJuliaThe code in nova has definitely evolved and it is less likely of a possibility with conductor groups since you have a smaller window between while your retrieving the node list15:28
rpittauyeah15:28
dtantsurrpittau: but I use "normal" CentOS, not Stream15:28
rpittauoh ok15:29
arne_wiebalckTheJulia: The main incidents were maybe before conductor groups.15:29
arne_wiebalckTheJulia: I think ...15:29
TheJuliayeah, that window being opened by the data set is really just huge in terms of where things can go sideways15:30
arne_wiebalckConductor groups ftw!15:31
TheJuliawell, zer0c00l's patch FTW15:32
arne_wiebalckAs well, and Ironic FTW!15:32
dtantsur\o/15:32
arne_wiebalckOn a side note, we are moving our batch infra from VMs to bare metal, all via Ironic ofc.15:33
dtantsurarne_wiebalck: interesting, why?15:33
arne_wiebalckdtantsur: the main reason is Ironic15:33
dtantsur:D15:34
arne_wiebalckdtantsur: we accepted a virtualisation tax since the batch service got an API with OpenStack15:34
arne_wiebalckdtantsur: now that Ironic provides that API, we claim the tax back15:34
dtantsurgot it15:34
dtantsurhave you ever estimated how high the tax is?15:35
arne_wiebalckdtantsur: oh, yes: it is about 2-5%15:35
* dtantsur collects fact for the "Why ironic" slide on numerous presentations15:35
dtantsur5% is substantial15:35
arne_wiebalckdtantsur: yes15:35
arne_wiebalckdtantsur: we were paying it to get the API15:36
arne_wiebalckdtantsur: now, since the same API can be used with physical nodes, the batch team can keep their machinery15:36
arne_wiebalckdtantsur: they have some provisioner code which creates instances, does not matter if virtual or physical :)15:37
dtantsurcool!15:38
arne_wiebalckdtantsur: I said conductor groups ftw, since we now distribute nodes over groups to use all conductors in parallel, and their provisioner can be configured to create N nodes in parallel ... they did 10, so I asked them to crank it up a bit to see where the limits are :) 15:39
arne_wiebalckdtantsur: they moved to 50 in parallel, still all ok, now we need to wait for more/larger deliveries to come ...15:40
dtantsur:)15:40
arne_wiebalck(this is more an academic exercise, doing 10 in parallel and let it chew on the available resources is totally fine)15:40
JayFat onmetal, we used to do bulk builds and see how it went15:43
JayFwe did 100 over the course of like 5 minutes, I think 2/3 succeeded even if a lot had to reschedule15:43
JayFand that was long before the agent driver was any good :P15:43
opendevreviewJulia Kreger proposed openstack/ironic master: Use selectinload for all list queries  https://review.opendev.org/c/openstack/ironic/+/79733715:44
TheJuliaarne_wiebalck: ^^ revised15:44
arne_wiebalckTheJulia: +2'ed, thanks!15:50
arne_wiebalckJayF: 60 was a limit for us in the past, but this was with 1 controller and our previous PXE infra, so I am curious to see how far we can go now (while at the same time) I do not want to give the impression to users that doing nothing for weeks and then expect to install 1000 nodes in one go is a sensible way of working :)15:53
TheJulianever a sensible way of working15:53
TheJuliaThe analogy that comes to mind is when you try to delete rows from a huge database15:53
TheJuliaYou can slip in lots of small deletes and not impact service/performance that much. Things will just chug along. But if you say "I want to delete these million rows", your database is locked and your not going anywhere fast15:54
opendevreviewRiccardo Pittau proposed openstack/bifrost master: [DNM] downgrade ansible  https://review.opendev.org/c/openstack/bifrost/+/79985815:54
dtantsurbaremetal-operator uses batches of 20 IIRC15:56
TheJuliaI actully had 1.6 million rows to delete once. I did the math on how long it would take after our monitoring system was down for 45 minutes while something like 40k rows were deleted.15:57
dtantsuroh omg15:58
dtantsureasier to create a new table and move the remaining data there15:58
arne_wiebalckdtantsur: exactly ... the "issue" is that new resources do not trickle in, but come in big chunks15:58
TheJuliaI ended up putting a cron job in to slowly delete out the rows and once a week do the needful db work.15:59
TheJuliadtantsur: didn't have the disk space on the physical server, nor could I add any space, to make a copy of the table.15:59
TheJuliaThat was so painful16:00
dtantsurwow16:01
arne_wiebalckTheJulia: this is how we prune our (OpenStack) databases, in fact, regularly in small chunks16:01
TheJuliaI think I did that in April, and the job finally failed to execute anymore when 0 matching rows were found in January16:01
TheJulia(i... completely... forgot about the cron job by then)16:01
dtantsurhuh, we don't run online_data_migrations in bifrost? Oo16:02
TheJuliadtantsur: I'm fairly sure we used to16:02
dtantsurI'm upgrading my environment, and it complains on dbsync...16:02
dtantsurwe do run it at some point.. I wonder if "some point" is wrong?16:03
TheJuliamaybe?16:03
dtantsurIt's after starting ironic, so should be correct? hmmmm...16:04
rpittaudtantsur: I can't reproduce it either on centos stream, wondering if it's transient ?16:05
dtantsur"Please run "ironic-dbsync online_data_migrations" using the previous release"16:05
TheJuliaoh...16:06
dtantsurit is a bad joke. openstack doesn't support downgrades, so anyone who gets in this situation will have to edit the database..16:06
* dtantsur is not sure why he's never thought about it16:06
TheJuliaSo you jumped 2 releases?16:06
dtantsurnope16:06
TheJuliathen you shouldn't have needed to16:06
dtantsurI suspect this environment was created in wallaby16:06
dtantsursomething feels really off16:06
TheJuliayeah, something does16:06
dtantsur(especially since I've just upgraded another environment without problems)16:06
TheJuliaprevious release makes me think you've got some really old objects in the db but that doesn't make sense16:07
dtantsuryeah, I'll dive into the database now16:07
dtantsurnodes 1.35, ports 1.10. wtf16:08
rpittaubye! o/16:09
*** rpittau is now known as rpittau|afk16:09
dtantsurhmmm, it's the same on my old environment16:09
dtantsurwut16:09
dtantsurs/old/another/16:09
dtantsurBIOS settings. I have 1.0 for BIOS settings.16:12
arne_wiebalcknodes 1.35 is Victoria, no? During the upgrade I had some controllers stay behind on Ussuri and I got "Nodes 1.34 is bad" message all over the place :-D16:13
opendevreviewMerged openstack/ironic master: Support "swift" for ramdisk_image_download_source  https://review.opendev.org/c/openstack/ironic/+/79968516:14
dtantsurNode 1.35 is current16:14
arne_wiebalckso it has not changed since Victoria then16:15
TheJuliaarne_wiebalck: well that is a bug too then16:18
TheJuliaWell, common db, you can't do the data migration until your fully upgraded and your supposed to do it after upgrade, but it is redundant on a single hop upgrade if I'm remembering correctly16:19
dtantsurI don't understand how this logic is supposed to work any more16:19
JayFarne_wiebalck: https://review.opendev.org/c/openstack/ironic/+/794880/9 is before that selectinload patch and needs a core vote, too16:19
JayFarne_wiebalck: if you're still around and wanna look and land it16:19
JayFarne_wiebalck: if you do, I'll backport the whole series to wallaby today16:19
dtantsurhow are version updated if you can run dbsync until versions are updated?16:20
arne_wiebalckJayF: checking ...16:20
dtantsurmmm, I suspect I know the problem. BIOSSetting removed 1.0 immediately after adding 1.1. there has to be an overlap16:21
TheJuliawell, can't run... I do believe we have another bug in the migrations usage16:21
TheJuliaoh!... 16:21
TheJuliathat seems like it could do it16:21
TheJuliaAnd yeah, there has to be if memory serves16:21
dtantsuralthough I see the same was done for nodes as some point and nobody complained..16:21
dtantsurI don't get it any more. but yes, I think there should be an overlap16:21
TheJuliarloo made sure the docs are very explicit, likely need to go back and check them16:22
* dtantsur is reading https://docs.openstack.org/ironic/latest/contributor/rolling-upgrades.html16:24
opendevreviewMerged openstack/ironic master: Avoid double file removal in create_boot_iso  https://review.opendev.org/c/openstack/ironic/+/79969516:28
dtantsurno, I don't understand anything...16:29
opendevreviewMerged openstack/ironic master: Add note regarding configuration drives to tuning docs  https://review.opendev.org/c/openstack/ironic/+/78962316:29
opendevreviewDmitry Tantsur proposed openstack/ironic stable/wallaby: Avoid double file removal in create_boot_iso  https://review.opendev.org/c/openstack/ironic/+/79977416:29
TheJuliaarne_wiebalck: you may want to look at https://review.opendev.org/c/openstack/ironic/+/794880/916:37
JayFTheJulia: jinx :P16:39
JayFI'm tryin' to get your patches merged too so I can backport them to wallaby16:39
TheJuliaheh16:39
TheJuliaPart of my take over the world plan16:40
TheJuliaOur armies of metal shall be efficiently provisioned and managed16:40
opendevreviewDerek Higgins proposed openstack/ironic stable/wallaby: Skip port create if MAC is blank  https://review.opendev.org/c/openstack/ironic/+/79986816:40
opendevreviewDmitry Tantsur proposed openstack/ironic master: Add overlap in BIOSSettings versions between 17.0 and 18.0  https://review.opendev.org/c/openstack/ironic/+/79986916:43
dtantsurTheJulia, rloo, feel free to tell me it's completely misguided ^^^ because I don't understand how versions work16:43
TheJuliasince 18 is a mid-cycle release, yes, that *is* correct16:45
rloough, you want me to remember that stuff? :) I trust TheJulia but will take a quick look...16:45
dtantsurI think there should be an overlap between the cycles as well16:45
dtantsurrloo: yes please. I'm completely confused, maybe your memory serves you better (quite likely)16:46
TheJuliarloo: you if you quickly dd if=/dev/urandom of=/path/to/file/with/that/memory, it will all be okay :)16:46
rloodoubtful about memory. hopefully the docs i wrote will trigger something!16:46
TheJuliaIf memory serves, and I didn't look at the docs first, but the version needs to know what it can be upgraded from16:47
TheJuliaor at least, what it is at so it can be upgraded16:47
* TheJulia may be oversimplifying it16:47
rlooBIOSSetting is new? no 1.0 entry at all... when did it get added?16:47
* dtantsur is clueless16:48
dtantsurI suspect we default to 1.0 anyway, that's what my table had16:48
TheJuliabios setting has been around for a long time16:48
TheJuliamaybe 3-4 years16:48
TheJuliaI think16:48
dtantsuryeah, it's not quite new16:51
opendevreviewDmitry Tantsur proposed openstack/ironic master: Bring boot_iso/deploy_iso handling in iLO closer to Redfish  https://review.opendev.org/c/openstack/ironic/+/79969616:52
arne_wiebalckTheJulia: LGTM! As usual, I am picking on some typos as well. Let me know if you would like to patch, or if I shall +W as is.16:53
*** mgoddard- is now known as mgoddard16:54
TheJuliaarne_wiebalck: editing the patch requires the latter one to need to rebased, so you can just +W and a follow-up should be fine as long as it is not actual code16:54
TheJuliaor if it is release note16:54
* TheJulia looks16:54
rloook, 3 years ago (https://opendev.org/openstack/ironic/commit/9eaff34b5ba4712bc10a521026d513d93cb019a2). we must have forgotten to add it to the mapping table. prob not worth adding it in retroactively.16:54
TheJuliaarne_wiebalck: yeah, so... workflow it, I'll do a follow-up since it makes sense to keep clean moving forward and it is just comments/doc string stuff16:56
NobodyCamGood Morning Ironic folks16:56
TheJuliaGood Morning NobodyCam 16:56
NobodyCamhehehe16:56
arne_wiebalckTheJulia: done, thanks16:56
NobodyCamhttps://www.irccloud.com/pastebin/6xlaRVIR/16:57
arne_wiebalckGood morning NobodyCam o/16:57
NobodyCammorning arne_wiebalck 16:57
TheJuliaWe're slowly taking over the world using the ironic, although I sense bifrost unhappiness?16:57
bfourniedtantsur: hmm, yeah I think I see, there was no BIOSSetting field in the mappings prior to https://review.opendev.org/c/openstack/ironic/+/786707/18/ironic/common/release_mappings.py as rloo noticed16:57
NobodyCamLOL no unhappy here. just having a giggle at the note for dnsmasq to be last 16:58
TheJuliaNobodyCam: dnsmasq + dns resolution stuffs == root of all evil16:59
NobodyCam:) 16:59
TheJuliaShould we ever do something silly like create our own version of http://www.eviloverlord.com/lists/overlord.html, it shall be that DNS is the root of all evil.16:59
dtantsurNobodyCam: yep, I keep forgetting to remove this note :)17:00
dtantsuralso, yes. DNS, IPv6, what else?17:01
JayFI can't believe you all are talking about roots of evil17:01
JayFand nobody mentioned IPMI, or hardware in general17:01
dtantsurIPMI, yes17:02
NobodyCamI was just about to bring up tftp 17:02
* arne_wiebalck shivers17:02
TheJuliaThis is starting to sound like we need to have a midcycle and create such a list17:03
dtantsurmaybe one day meeting each other is a thing again....17:03
TheJuliaI sure hope so17:04
dtantsurwell, eventually we'll run out of greek letters!17:04
rloodtantsur: does our code support both v1 and v1.1 of BIOSSetting?17:04
dtantsurrloo: for some definition of "support"?17:05
dtantsurwe have version conversion in place17:05
rloodtantsur: i'm trying to remember/understand. I don't think we need an 'overlap' unless we want to continue supporting those versions. the migration is meant to convert from an older version to a newer one.17:05
dtantsurrloo: if there is no overlap, the migration will refuse to work17:05
dtantsurboth dbsync and online_data_migrations verify versions before running17:05
rlooi think the problem is that there isn't any BIOSSetting 1.0 in the previous release mapping17:05
dtantsurI don't think so, what would it change?17:06
rlooi could be wrong though17:06
rlooam looking at Node versions. sometimes there is overlap, sometimes not. eg, 11.1 -> 12.0 no overlap.  Trying to remember...17:08
dtantsuryep, that's what is confusing me17:10
dtantsurI don't understand how it works without an overlap... but it used to work?17:10
rloothat list of versions is due to this: https://review.opendev.org/c/openstack/ironic/+/408556/52/ironic/db/sqlalchemy/api.py, L1128. lots of comments but ... what does 'supported versions' mean.17:12
rloois there code that migrates BIOSSetting from 1.0 to 1.1?17:13
TheJuliathere is no data transformation, just additional fields aiui17:13
TheJuliaso what *changes* is the object model has an additional field17:14
dtantsurin theory online_data_migrations have to update versions17:14
dtantsurand do any changes required (beyond dbsync)17:14
TheJuliayup17:14
TheJuliayup17:14
rlooonline_data_migrations is connected to this check_versions code I think... dtantsur, you mention that the upgrade fails. what was the error?17:15
opendevreviewJulia Kreger proposed openstack/ironic master: Fix typos in API sanitization change notes  https://review.opendev.org/c/openstack/ironic/+/79987217:15
rloo(looking back at irc...)17:16
arne_wiebalckbye everyone o/17:17
dtantsurrloo: The database is not compatible with this release of ironic (18.0.1.dev90). Please run "ironic-dbsync online_data_migrations" using the previous release17:19
dtantsurI also think we should provide a better recommendation than "use the previous release", which is practically impossible in many cases17:19
dtantsurbut that's a different topic for another day17:19
rloodtantsur: i think if we add BIOSSetting 1.0 to the previous releases, that will solve it.17:20
dtantsurrloo: how?17:20
rloodtantsur: we don't want to support 1.0 in wallaby17:20
dtantsurthen we need to remove the check on versions from dbsync17:20
dtantsuralso, s/wallaby/xena/ you mean?17:20
TheJuliacan I please get reviews on https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/797521 so I can one day move the overall secure rbac model implementation effort to the proverbial done column?17:20
rloo'using the previous release' means that this release cannot handle the migration cuz it had to have been doen with the previous release.17:21
dtantsurrloo: yep, and the previous release does nothing17:21
dtantsurbecause 1.0 is the maximum version there17:21
rlooi think it is cuz there is no explicit 1.017:21
rlooi saw somewhere that if it isn't specified, default is to use the latest version.17:21
dtantsurmy table had 1.0 quite happily17:21
opendevreviewDerek Higgins proposed openstack/ironic stable/wallaby: Skip port create if MAC is blank  https://review.opendev.org/c/openstack/ironic/+/79986817:21
rloooh, so you tried adding 1.0 to 17?17:21
dtantsurrloo: no, it worked automatically for me17:22
dtantsurmy initial state was BIOSSettings with 1.0 versions17:22
dtantsurI upgraded to latest master, and dbsync failed17:22
dtantsurbecause 1.0 is not compatible with ['1.1'] in Xena17:22
dtantsurI can reproduce it again and try adding 1.0 to 17 if you want to17:23
dtantsurhmm, interesting, it didn't fail indeed17:25
dtantsurnow I officially have no clue how this works17:25
dtantsurrloo: ^^^17:25
rlooi think (but haven't verified) that the situation with eg Node having more than one version in the list is due to us supporting interim versions (so eg we changed Node often w/i the older->latest releases. Cuz we support from previous named release to master or something like that.17:26
dtantsuryeah. it doesn't explain how the check magically works if I update an ancient release17:27
rloofor BIOSSetting, i think 1.1 was added in v 18.0. which is hmm.. not the first wallaby release.17:27
rlooRELEASE_MAPPING['victoria'] = RELEASE_MAPPING['16.0']17:28
rlooRELEASE_MAPPING['wallaby'] = RELEASE_MAPPING['17.0']17:28
rloodtantsur: i think it has soemething to do with ^^17:28
dtantsuryeeeep, this starts making some sense17:28
TheJuliawell, 18.0 is xena17:29
dtantsur(we should have removed victoria before the first point release)17:29
TheJuliawell, master really in xena17:29
TheJulia++17:29
rloooh. 17:29
dtantsurokay, so I feel like check_versions doesn't do what we think it does17:29
dtantsurit literally just checks if a version has EVER been supported17:29
rlooi think check_versions is used to see IF the db-migration stuff can handle the objects in the DB. if the objects have older versions than it can handle, it errors with that error you got.17:30
dtantsuryeah, but what's the real case?17:31
dtantsurwe still happily support Node 1.21 from ironic 9.217:31
rloonot sure we need it now. it might have been when we/openstack was saying we'd only support migrations from previous named release to latest/master.17:31
dtantsuryeah, I think this was the intention17:32
dtantsurbut that's not what the code does17:32
rloobut then we added stuff to do migrations from previous ones (unless we deleted that code, which we might have... can't recall now...)17:32
TheJuliahmmm17:32
rlooso i think stuff should work if we didn't delete migrations from older versions...17:32
dtantsurI suspect we were supposed to remove ancient versions from RELEASE_MAPPING17:32
dtantsur# Just after doing a named release, delete any entries associated with the17:32
dtantsur# oldest named release.17:32
rlooi thought we might have though.17:32
dtantsurfrom the code ^^^17:32
dtantsurwe never did that, we still have 9.2 in the mappings17:32
dtantsurwhich was Queens17:33
TheJuliaYeah, I think we only removed one... once.17:33
dtantsurokay, let me figure out which release added BIOSSettings, fix my patch and figure out the rest tomorrow17:33
TheJuliasounds like a plan17:33
dtantsur11.0.0, Rocky17:34
rloothx dtantsur!17:35
dtantsurthank YOU rloo for diving into that17:35
dtantsurwe'd be still scratching heads without your help17:35
rloo(fingers crossed... this is why i try to document. no memory..)17:35
rloothat upgrade stuff is somewhat fragile in the sense of humans needing to do stuff... :-(17:36
dtantsuryeah, I'll think about some more automatic checks tomorrow (unless you beat me to it)17:37
opendevreviewDmitry Tantsur proposed openstack/ironic master: Add missing BIOSSettings version mapping for older releases  https://review.opendev.org/c/openstack/ironic/+/79986917:38
dtantsurokay, on this ^^ positive note I'm calling it a day17:38
dtantsuro/17:38
opendevreviewJulia Kreger proposed openstack/ironic stable/wallaby: Ironic index docs/command check backport  https://review.opendev.org/c/openstack/ironic/+/79287318:23
opendevreviewMerged openstack/ironic master: Allow node_sanitize function to be provided overrides  https://review.opendev.org/c/openstack/ironic/+/79488018:25
JayFTheJulia: when I backport that db-perf-1 topic, should I include the typo fixes? Leaning towards no18:58
TheJuliaJayF: yeah, I don't think it is really needed to be backported, tbh18:59
JayFcool, in that case, keep eyes peeled, the last one is about to land then I'll mass-backport18:59
JayFhopefully before standup/lunch18:59
opendevreviewMaksim Malchuk proposed openstack/tenks master: Fix the error 'The `libvirt` module is not importable'  https://review.opendev.org/c/openstack/tenks/+/79990119:07
opendevreviewMerged openstack/ironic master: Use selectinload for all list queries  https://review.opendev.org/c/openstack/ironic/+/79733719:13
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: Only return the requested fields from the DB  https://review.opendev.org/c/openstack/ironic/+/79988019:16
JayFTheJulia: hmm, when backporting a chain like this, should I jsut do it one at a time, wait for them to merge? or set depends-on?19:17
JayFoh, this is going to be 100x easier if I do it from a cli, won't it19:17
JayFI'm going to do that, I thikn19:17
JayFanyone have insight into these failures? Am I missing some permissions or something? https://gist.github.com/jayofdoom/df50627ae77f06d0ce3e18bdb805b29419:24
JayFaha, I think I get it19:25
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: Only return the requested fields from the DB  https://review.opendev.org/c/openstack/ironic/+/79988019:25
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: Set stage for objects to handle selected field lists.  https://review.opendev.org/c/openstack/ironic/+/79990419:25
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: API to pass fields to node object list  https://review.opendev.org/c/openstack/ironic/+/79990519:26
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: Allow node_sanitize function to be provided overrides  https://review.opendev.org/c/openstack/ironic/+/79990619:26
opendevreviewJay Faulkner proposed openstack/ironic stable/wallaby: Use selectinload for all list queries  https://review.opendev.org/c/openstack/ironic/+/79990719:26
opendevreviewMaksim Malchuk proposed openstack/tenks master: Fix the error 'The `libvirt` module is not importable'  https://review.opendev.org/c/openstack/tenks/+/79990119:28
JayFugh, I didn't topic those well and now I can't change the topic19:29
JayFhttps://etherpad.opendev.org/p/DBPerfBackports I put those, and the nova change, in here so it's easy to link to and review19:32
TheJuliaJayF: thanks19:38
* TheJulia reads19:38
opendevreviewMerged openstack/ironic-tempest-plugin master: Remove train testing from ironic-tempest-plugin  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/79967819:39
opendevreviewMerged openstack/ironic-tempest-plugin master: Update min version of tox to use allowlist  https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/79639319:39
TheJuliaJayF: U,mmmm you should be able to change the topic19:39
JayFTheJulia: when I try to repush with `git review -t [a better topic]` it is angry due to no changes19:39
TheJuliahmm19:40
TheJuliaInteresting19:40
JayFTheJulia: and since it's a clean cherry-pick, I don't wanna modify it19:40
JayFit's not a big deal if we just land them :)19:40
TheJuliaI wonder if that is something we lost in the most recent upgrade19:40
TheJuliawfm19:40
JayFyou go review them and put +2s on them and I'll wait like a shark to attack the next core to say something in here so it gets merged19:40
JayFlol19:40
TheJulialol19:43
TheJulia<319:43
TheJuliawill do, need to finish current though in the document I'm writing19:43
opendevreviewMaksim Malchuk proposed openstack/tenks master: Fix the error 'The `libvirt` module is not importable'  https://review.opendev.org/c/openstack/tenks/+/79990119:45
TheJuliaJayF: so fwiw, it is missing the cherry picked from xyz commit... but AFAIK that was only used by one of the downstream delta tracking between branch tools20:25
TheJuliaJayF: that got encoded in as "thou shall do this (so we don't break hpcloud branching)" a long time ago but I've never gotten a real answer on otherwise so I'm +2 on them. Someone can scream at me later if they can explain why it also needs to be human readable from just the commit message20:27
opendevreviewMerged openstack/ironic master: Fix typos in API sanitization change notes  https://review.opendev.org/c/openstack/ironic/+/79987220:30
stevebakergood morning20:39
TheJuliao/ stevebaker 20:42
JayFTheJulia: Probably because they were cherry-picked straight outta gerrit, not using the web ui20:51
JayFTheJulia: if it's an issue I can manually add (and fix thd topic)20:52
* TheJulia shrugs20:52
JayFTheJulia: given I -1'd a stable patch for that reason, I kinda feel like I should20:52
TheJuliagit review -X does the magic fwiw20:52
TheJuliaand if you just re-cherry-pick on to a clean branch off of stable/wallaby, then all of the cherry-pick topics should get updated20:52
JayFima leave it and not review for that in the future, either20:53
TheJuliak20:53
* TheJulia starts the "question policy dogma" club and adds JayF to it20:53
JayFstevebaker: if you got a second, would <3 some core reviews on the backports in this etherpad: https://etherpad.opendev.org/p/DBPerfBackports (the perf stuff julia has been working)21:16
TheJuliaJayF: I have this strange feeling I need to send you some sort of thing21:23
JayFWDYM?21:24
TheJuliahttps://www.amazon.com/Pieces-Accessory-Costume-Sharks-Adults/dp/B081JNWBB9 :)21:24
JayFI have my own cluesticks here, I'm sure my wife would volunteer to use one if you wanted 21:24
JayFahh21:24
JayFI promise you I'd never wear that :D21:24
JayFbut the thought is nice lol21:24
TheJulialol21:24
TheJulia:)21:24
JayFjroll once called me an unbalanced washing machine21:25
JayFso if I'm going to costume up, I think that's gotta be it lol21:25
TheJuliaoh noes....21:25
jrolllmao21:25
TheJuliaWell, if one must wear a costume21:25
* TheJulia pulls up the weather station data and wonders "how much am I going to roast"21:26
JayFTheJulia: real story: I used to have a roommate named "Rob", who was tall, skinny, and very very quiet21:26
JayFTheJulia: we went one year to work as "Jay and Silent Bob"21:27
JayFprobably #1 best costume usage ever, especially since Rob did a good job of actually being loud and obnoxious and I managed to STFU for a day21:27
TheJuliaHeh21:28
stevebakerJayF: sure thing21:34
JayFstevebaker: thanks buddy \o/21:34
opendevreviewJulia Kreger proposed openstack/ironic stable/wallaby: Ironic index docs/command check backport  https://review.opendev.org/c/openstack/ironic/+/79287321:35
TheJuliaYou know you live someplace hot when you ponder "Will 109F begin to overheat the car"21:36
JayFYou're talking to the guy who no more than 2 weeks ago spent 115F weather inside a house with broken AC21:36
JayF109F is wimpy temps /s21:37
TheJuliaheh21:42
TheJuliaWell, at least it is not 120F+ this week21:43
JayFAnyone got experience with setting up virtualbmc? AFAICT I'm doing everything right, but I'm getting errors https://gist.github.com/jayofdoom/4df151c28c8d90d36bc2609d66cee0f822:33
JayFand I have vmbcd running in debug/foreground, and there are no error messages from it22:33
JayFAFAICT vbmcd isn't even listening on the port after added22:34
JayFthank you empty IRC for rubber ducking; I needed a `vbmc start [domain]` https://github.com/openstack/ironic/blob/e3b401baf674a897883c27d2b0143283c2dd5acb/devstack/lib/ironic#L208522:35
jandersgood morning Ironic o/22:56

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