Wednesday, 2025-01-29

opendevreviewmelanie witt proposed openstack/nova master: pwr mgmt: power down free PCPUS when updating compute node  https://review.opendev.org/c/openstack/nova/+/93292602:14
*** ralonsoh_ is now known as ralonsoh08:08
opendevreviewBalazs Gibizer proposed openstack/nova-specs master: Extend image-properties-in-server-show spec with rebuild  https://review.opendev.org/c/openstack/nova-specs/+/94036008:09
gibidansmith, melwitt, sean-k-mooney: thanks for the quick response. Here are the spec update ^^08:12
masahitogibi: hi, could you review the small bug fixes for the v2.96 or later API bug if you have time? It has been +2ed already so it needs one more W+1.  https://review.opendev.org/c/openstack/nova/+/939673 and https://review.opendev.org/c/openstack/nova/+/93965808:17
gibimasahito: looking...08:21
gibimasahito: I've approved the reproducer and left some API concerns in the fix. We probably need other cores to express opinion about the API impact. 08:48
gibisean-k-mooney: ^^08:49
*** tkajinam is now known as Guest733409:05
masahitogibi: thanks for the quick review :)09:33
mikalsean-k-mooney: that SPICE patch series has now been updated and passes CI.09:34
opendevreviewMark Goddard proposed openstack/nova master: ironic: Let Ironic handle deployment cleanup actions during destroy  https://review.opendev.org/c/openstack/nova/+/88341109:57
stephenfinsean-k-mooney: feck :(10:02
stephenfinsean-k-mooney: Yeah, that checks out. Let me think on it. If you're doing further reviews, maybe just ignore/call out the places I've made those assumption and move on. I'll rejig10:04
sean-k-mooney[m]sure we have merged one already the flavor acess schema10:05
sean-k-mooney[m]we should fix that10:05
sean-k-mooney[m]but there are very few apis that take either a project id or user id10:05
stephenfinsean-k-mooney[m]: Potential proposal. I'm going to drop https://review.opendev.org/c/openstack/nova/+/937013 from the stack and see how clean the rebase is10:15
stephenfinIf it's horrific, I might keep it and rejig the commit message to indicate that no, these things aren't UUIDs but they often look like UUIDs so this is a little more realistic??10:15
sean-k-mooney[m]sure, i would jsut assert that its a stiring between 1 and 64 printable characters10:16
stephenfinHopefully not an issue but I'd _love_ to avoid a multi-hour rebase if possible šŸ˜‡10:16
stephenfinprintable or ascii?10:16
stephenfin*alphanumeric10:16
stephenfin(if you know off the top of your head)10:17
sean-k-mooney[m]you can look at the keystone def its effectivly base6410:17
sean-k-mooney[m]i think10:17
sean-k-mooney[m]alphanumeric  and _ perhaps -10:17
sean-k-mooney[m]i dont recall exactly but a subset of ascii10:18
sean-k-mooney[m]stephenfin:  https://github.com/openstack/keystone/blob/master/keystone/api/validation/parameter_types.py#L67-L7310:19
stephenfinideal, copy-paste job so10:21
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for server topology API  https://review.opendev.org/c/openstack/nova/+/94030010:39
fricklerwell this is more explicit, so likely for domains the full answer is "UUID4 without dashes or 'default'"? https://opendev.org/openstack/keystone/src/branch/master/keystone/resource/schema.py#L24910:53
sean-k-mooneyfrickler: domain are not used in any nova api10:54
sean-k-mooneyproject and user ids are and have different rules10:54
fricklerah, ok10:55
sean-k-mooneyfrickler: user ids for federated keystone are the first 64 bytes of the sha256 of the user objects fields by default btu thte hash is both plugable and configurable10:56
sean-k-mooneyfrickler: this basically all stems out of the fact that when using ldap/active directory they dont produce uuids for the identifer10:56
sean-k-mooneyso orginally keystone pass that through directly10:57
sean-k-mooneythe sql backend that most use does produced the hex dump of a uuid410:57
sean-k-mooneyits one of those things where it will almost alwasy be a uuid in practice but in reality we cant depend on that10:59
sean-k-mooneyfrickler: my real concer is that the sdk or some other code has made the same assumation11:00
sean-k-mooneyquick glance says no, they are constucitng fake ides usign uuid4 but prepeending user-id https://github.com/openstack/openstacksdk/blob/c6459ae0b0983530d8db75178bbfe213c8022396/openstack/tests/unit/identity/v3/test_proxy.py#L3811:04
opendevreviewJohn Garbutt proposed openstack/nova master: ironic: Fix ConflictException when deleting server  https://review.opendev.org/c/openstack/nova/+/88341111:11
johnthetubaguysean-k-mooney: I have reworded the commit message on this old patch, because it is now really urgent. We have a big regression on the Ironic driver after merging those convert to SDK patches, basically we lost the ability to retry on HTTP Conflict for the silly unplug_vif code. This old patch looks to fix the problem. It would be ace if you have chance to review this one please (you added some comments saying you wanted to look at11:17
johnthetubaguythis in the past): https://review.opendev.org/c/openstack/nova/+/88341111:17
opendevreviewMerged openstack/nova master: Add ServersViewBuilderTestV296 unit test class  https://review.opendev.org/c/openstack/nova/+/93967311:29
sean-k-mooneyjohnthetubaguy: so retrying on http conflict is not really a thing we shoudl do in general11:32
sean-k-mooneya 409 means the request is invaild for the current state and we shoudl not expect resending it to work11:33
sean-k-mooneyjohnthetubaguy: with that said i dont crrently have the context of this patch loaded so i will take a look11:34
sean-k-mooneyjohnthetubaguy: i had previoulys agreed to allow fixign the current sate even thought he ironci workfow violates our driver api 11:39
johnthetubaguy[@_oftc_sean-k-mooney:matrix.org](https://matrix.to/#/@_oftc_sean-k-mooney:matrix.org)I agree with you, we should add more retry on conflict back in. But in this specific case, after we retry for around 15-30 mins, what we get is Bad request, and only then we consider the operation complete. Basically when unprovision has succeded, all the other work has already been done for us.11:39
sean-k-mooneyso johnthetubaguy with that in mind i assume you have tested this?11:39
sean-k-mooneywe do have a greeen ironic-tempest-ipa-wholedisk-bios-agent_ipmitool-tinyipa but that boot and deelete like 1 instance11:40
johnthetubaguy[@_oftc_sean-k-mooney:matrix.org](https://matrix.to/#/@_oftc_sean-k-mooney:matrix.org)I haven't tested this on master, but it has been running in some old clouds for a while. I haven't heard back if this works on Caracal yet either I am afraid. Just had this reported to me yesterday evening internally.11:41
sean-k-mooneyso this obviouly does nto entrily break everythign but it does not validate that the node can be used again11:41
sean-k-mooneyjohnthetubaguy: ack11:41
johnthetubaguySure, but we call unprovison, and that goes into either error or available, let me find that graph a sec in the ironic docs to check.11:42
sean-k-mooneyjohnthetubaguy: that not really the issue11:42
johnthetubaguyOK, what bit are you worried about? I could easily be missing something?11:43
sean-k-mooneyso there are two conferns one is practically does this work which is what you were answering. and i trust you when you say that unprovision will do all the actions that cleanup_deploy does11:43
sean-k-mooneythe issue with that is ironic is not allow to modify neturon ports or cinder volume attachments assocated with a nova instnace. so it doing the cleanup as part of unprovision by makign api calls ironic si not allowed to do11:44
sean-k-mooneyso long term that is a probelem that shoudl be fixed11:45
johnthetubaguyAh, I was missing your concern before. Now I see what you mean. It is a ā€œdifferent danceā€ with Ironic, for sure. And we do hit issues because of the oddities going on there, e.g.: https://bugs.launchpad.net/nova/+bug/208543211:46
sean-k-mooneyi agreed that we can move forward with the current state. that does not mean the current state is correct. i condier this to just be a workaround11:46
sean-k-mooneyjohnthetubaguy: well its not jsut that its also this https://security.openstack.org/ossa/OSSA-2023-003.html11:48
johnthetubaguyI mean, this is Nova better respecting Ironicā€™s API semantics, in my book, but I donā€™t think we have connects on what we want it to look like. I know Ironic are keen to re-work the networking stack for their standalone cases, and making NGS suck much less would be aceā€¦ I should take a look at that soon ish.11:49
johnthetubaguyAh, so, volumes and Ironic, I mostly hard ignore myself. So that probably is an aspect we need someone to test better. Or at least get some lovely Ironic people to take a look at our reasoning here.11:50
sean-k-mooneyform my perspecitve ironci is not allwoed ot make any calls to neutorn or cinder for ports or volumes port are assocated with a nove instance11:50
sean-k-mooneyjohnthetubaguy: nova does not allow you to add/remove voluvmes or port to/form an instnace via the cidner/neutrion api inluciding createing/modifying volume attachments or port bindings11:51
sean-k-mooneyjohnthetubaguy: ironic is doign both11:51
johnthetubaguyYeah, true.11:51
sean-k-mooneyso unprovision in ironic should not be cleanign up the neutorn prots ro removing the volume attahcments11:52
sean-k-mooneythat shoudl be done by our generic code in the compute manager as part of the instance delete flow11:53
sean-k-mooneyjohnthetubaguy: anyway what importnt right now is this is impacting actual users11:53
sean-k-mooneyso we need to do the best we can in the current state11:54
sean-k-mooneybut if we have simialr CVEs in the future ironic integation may break11:54
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for hosts APIs  https://review.opendev.org/c/openstack/nova/+/93704711:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for instance actions  https://review.opendev.org/c/openstack/nova/+/93704811:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for hypervisors APIs (1/3)  https://review.opendev.org/c/openstack/nova/+/93724511:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for hypervisors APIs (2/3)  https://review.opendev.org/c/openstack/nova/+/93724611:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for hypervisors APIs (3/3)  https://review.opendev.org/c/openstack/nova/+/93724711:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for server IPs APIs  https://review.opendev.org/c/openstack/nova/+/93760811:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for remote consoles  https://review.opendev.org/c/openstack/nova/+/94011411:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for keypairs APIs  https://review.opendev.org/c/openstack/nova/+/94011511:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for image metadata APIs  https://review.opendev.org/c/openstack/nova/+/94029911:58
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for server topology API  https://review.opendev.org/c/openstack/nova/+/94030011:58
opendevreviewStephen Finucane proposed openstack/nova master: api: project/tenant and user IDs are not UUIDs  https://review.opendev.org/c/openstack/nova/+/94036911:58
sean-k-mooneyjohnthetubaguy: anyway +211:59
sean-k-mooneyjohnthetubaguy: there is another ironci change that you might want to take a look at if you feel like doing a review12:00
sean-k-mooneyit fixes a regression added in dalmation so you may not have hit it yet12:01
sean-k-mooneyhttps://bugs.launchpad.net/nova/+bug/209257012:03
sean-k-mooneyjohnthetubaguy: https://review.opendev.org/c/openstack/nova/+/93941112:03
johnthetubaguyI will take a look now.12:40
*** whoami-rajat_ is now known as whoami-rajat14:02
*** Guest7381 is now known as bbezak14:56
johnthetubaguy[@_oftc_sean-k-mooney:matrix.org](https://matrix.to/#/@_oftc_sean-k-mooney:matrix.org)got distracted by chasing outage fun, but I am +2 that patch. I don't feel in-sync enough to +W right now, but that sure looks broken. I guess we don't test rebuild in that ironic CI you mentioned?15:09
johnthetubaguy(as in we look broken without that patch)15:09
sean-k-mooneywe have exactly 1 job and it boot 1 vms and deletes it15:09
sean-k-mooneyso ya no rebuild testing15:09
sean-k-mooneywe really shoudl fix that...15:09
sean-k-mooneythis is a simple case where mypy and type checking would have saved use. we just mixed up the paramater order15:10
sean-k-mooneyjohnthetubaguy: if no one else has ocmmend ill loop back and +w next week15:10
sean-k-mooneymikal: looking at https://review.opendev.org/c/openstack/nova/+/924844 melwitt comment form pathset 18 have not been adressed15:11
kpdevhi all, need review on https://review.opendev.org/c/openstack/nova/+/92747415:12
kpdevI had also mentioned at https://etherpad.opendev.org/p/nova-bug-triage-2024090415:12
sean-k-mooneymikal: sorry https://review.opendev.org/c/openstack/nova/+/924844/2415:13
sean-k-mooneymikal: i shoudl slow down https://review.opendev.org/c/openstack/nova/+/924844/24/nova/api/openstack/compute/remote_consoles.py the api change relate to the get_spice_console api that was remvoed in 2.615:14
sean-k-mooneykpdev: that change is not valid15:15
kpdev@sean-k-mooney: what is missing ? Can you please reply on pull request ?15:17
sean-k-mooneythe bug report is invliad15:17
sean-k-mooneyif we were to implemnt what you propsoe it would be a feature with a non tivial upgrade impact15:17
sean-k-mooneykpdev: nova assumes that all cpus can be use by default, if that is not the case you are requried to use the [compute]cpu_shared_set and [compute]cpu_dedicated_set or the legacy [default]vcpu_pin_set to specify which cpu can be used15:19
sean-k-mooneyif your host cgroups are configure in such a way as they cannot be assigned to the vm becuase of the cpu_exclisve bit or otherwise and you do not use the provided config option that is not a nova bug15:20
kpdevso you mean, using provided config option there is no need of this PR15:21
sean-k-mooneycorrect i dont think this change is required if you correctly confire nova via the cpu_share_set15:22
sean-k-mooneynova should not be parssing the cgoup configuration to determin which cpu can be used15:23
sean-k-mooneythe the installer shoudl be configuring that via the aviabel options15:23
kpdevok15:25
kpdevI have added this on bug and update after checking with engineer15:26
sean-k-mooneyi have tiraged the bug as opipion, if you stongly feel that the ux should be imporved i think we would need to have a disgin dicussion on how before proceedign with this as a new feature15:32
sean-k-mooneyi dont think this is in the scope of nova to adress however15:32
kpdevlet me check internally as you are saying its not then in scope of nova to address.15:37
opendevreviewRajesh Tailor proposed openstack/nova master: Add support for showing image properties in server show response  https://review.opendev.org/c/openstack/nova/+/93964915:43
melwittsean-k-mooney: hey I just read your comment on the power management patch. are you saying that you think we should not be offlining CPU for STOPPED instances?16:26
opendevreviewMasahito Muroi proposed openstack/nova master: Use defaultdict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/93965817:35
opendevreviewMasahito Muroi proposed openstack/nova master: Use defaultdict object for request_specs_dict in the _list_view  https://review.opendev.org/c/openstack/nova/+/93965817:43
masahitogibi sean-k-mooney: thank you for the review for the patch. I did the further investigation for the current response value pattern. Please check the result and document update, too. https://review.opendev.org/c/openstack/nova/+/93965817:45
mikalsean-k-mooney: I think you're saying you just want the changes to that file that you commented on removed? Is that right?18:47
sean-k-mooneyso im unsure18:47
sean-k-mooneymikal: melwitt made a comment that that api was remvoed in 2.618:47
mikalsean-k-mooney: IIRC Mel was confused by an old removed API and in the end I didn't need to do anything. I am trying to reload state on that file at the moment.18:48
sean-k-mooneyso we shoudl not need to update it18:48
sean-k-mooneyand as a result we likely dont need that addtional validation schema18:48
mikalsean-k-mooney: yeah, Mel wanted a test for the HTTP GET on that API, which was removed.18:48
sean-k-mooneybecause if you were to use the 2.5 microversion it shoudl not return the new spice console anyway18:49
sean-k-mooneyso it was removed in a micorversion but we did not remove the functionaltiy18:49
sean-k-mooneyif we did the funciton woudl be returnign a 410 18:49
melwittthis sounds familiar and maybe I forgot to reply (and don't remember at the moment)18:50
sean-k-mooneymelwitt: context is i started reviewing mikal spice console serise again yesterday18:50
sean-k-mooneyand noticed your comment did not seam to be adressed18:50
mikalSo I can revert the changes to that file. Honestly I'm not across the validation stuff much, but if you think that's correct I believe you.18:51
melwittok, I'll take a look18:51
mikalsean-k-mooney: I'm just removing the validation for the HTTP GET right, not the POST?18:52
sean-k-mooneymikal: i think you can revert the changes to that file and also remove the other changes melwitt mention in ps 1818:52
sean-k-mooneyi would also need ot load context18:52
sean-k-mooneyim looking for the patch now18:52
sean-k-mooneyok so https://review.opendev.org/c/openstack/nova/+/924844/24/nova/api/openstack/compute/remote_consoles.py18:53
sean-k-mooneyso the changes to create are correct18:53
sean-k-mooneyschema.get_spice_console_v298 is not needed and the changes to get_spice_console can be reverted 18:54
mikalOk, doing that now.18:54
sean-k-mooneymel mention you can remvoe the scheme here https://review.opendev.org/c/openstack/nova/+/924844/comment/bcfe7166_8d9bb51c/18:55
sean-k-mooneymikal: i think all the other comments were adress looking over them quickly18:56
mikalYeah honestly I thought I'd addressed them all but I definitely missed that one.18:56
sean-k-mooneybeyond that i dont see anything quickly that i would -1 for18:57
sean-k-mooneyi need to finsih reading the release note but i suspect we could proceed ith it as is18:57
sean-k-mooneyor adress other issue in a followup18:57
mikalAs an aside, I learned the other day that libvirt's equivalent to oVirt VDSM hooks _does_ _not_ allow modifying the domain XML or qemu command line on instance start. There are some times you can change the XML, mostly around live migration, but not for a domain create.18:58
sean-k-mooneyoh ya one trivial issue in the release note18:58
sean-k-mooney"spice-direct" shoudl be ``spice-direct``18:58
sean-k-mooneydouble backtics to make it bold18:58
sean-k-mooneybtu honstly it fine with quotes18:58
mikalI cna fix that now too.18:58
sean-k-mooneysame for spice_direct_proxy_base_url18:59
mikalDo you want it bold in the API reelase notes too?18:59
sean-k-mooneyyou mena the api ref18:59
mikalnova/api/openstack/compute/rest_api_version_history.rst18:59
sean-k-mooneyah the microversion history doc19:00
sean-k-mooneyit does not hurt to call it out19:00
sean-k-mooneybut up to you19:00
sean-k-mooneyi was more commenting on not useing "" for empahsie19:00
sean-k-mooney*emphasis19:00
mikalOk19:00
sean-k-mooneyonce that is resovled i think im +2 on the 3 main patches19:02
sean-k-mooneyill try and review the remaing too now while i have context19:03
mikalThank you. I am in the process of prepping to upload a new version now that address those comments.19:04
opendevreviewMichael Still proposed openstack/nova master: libvirt: direct SPICE console object changes  https://review.opendev.org/c/openstack/nova/+/92687619:08
opendevreviewMichael Still proposed openstack/nova master: libvirt: direct SPICE console database changes  https://review.opendev.org/c/openstack/nova/+/92687719:08
opendevreviewMichael Still proposed openstack/nova master: libvirt: allow direct SPICE connections to qemu  https://review.opendev.org/c/openstack/nova/+/92484419:08
opendevreviewMichael Still proposed openstack/nova master: libvirt: Add extra spec for sound device.  https://review.opendev.org/c/openstack/nova/+/92612619:08
opendevreviewMichael Still proposed openstack/nova master: libvirt: Add extra specs for USB redirection.  https://review.opendev.org/c/openstack/nova/+/92735419:08
sean-k-mooneymikal: im just finishing for today. im +2 on the first 3 pathces and -1 for the last two, comments in line20:17
mikalOk cool, I'll take a look at the comments today.20:32
opendevreviewMichael Still proposed openstack/os-traits master: Add traits for sound and USB devices on instances.  https://review.opendev.org/c/openstack/os-traits/+/94041823:24
mikalsean-k-mooney: ^--- a first swing at the os-traits change23:25
opendevreviewMichael Still proposed openstack/os-traits master: Add traits for sound and USB devices on instances.  https://review.opendev.org/c/openstack/os-traits/+/94041823:45

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