Thursday, 2024-02-22

opendevreviewArtom Lifshitz proposed openstack/nova master: POC: power up dedicated cores during pre_live_migration  https://review.opendev.org/c/openstack/nova/+/90980601:02
opendevreviewArtom Lifshitz proposed openstack/nova master: POC: power up dedicated cores during pre_live_migration  https://review.opendev.org/c/openstack/nova/+/90980601:22
opendevreviewArtom Lifshitz proposed openstack/nova master: POC: power up dedicated cores during pre_live_migration  https://review.opendev.org/c/openstack/nova/+/90980601:24
opendevreviewmelanie witt proposed openstack/nova master: Support create with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/87093205:18
opendevreviewmelanie witt proposed openstack/nova master: Support (resize|cold migration) with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/87093305:18
opendevreviewmelanie witt proposed openstack/nova master: Support live migration with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/90551205:18
opendevreviewmelanie witt proposed openstack/nova master: Support rebuild with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/87093905:18
opendevreviewmelanie witt proposed openstack/nova master: Support rescue with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/87367505:18
opendevreviewmelanie witt proposed openstack/nova master: Add encryption support to qemu-img rebase  https://review.opendev.org/c/openstack/nova/+/87093605:18
opendevreviewmelanie witt proposed openstack/nova master: Support snapshot with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/87093705:18
opendevreviewmelanie witt proposed openstack/nova master: Add backing_encryption_secret_uuid to BlockDeviceMapping  https://review.opendev.org/c/openstack/nova/+/90796005:18
opendevreviewmelanie witt proposed openstack/nova master: Support encrypted backing files for qcow2  https://review.opendev.org/c/openstack/nova/+/90796105:18
opendevreviewmelanie witt proposed openstack/nova master: Support cross cell resize with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/90959505:18
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Introduce support for raw with LUKS  https://review.opendev.org/c/openstack/nova/+/88431305:18
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Introduce support for rbd with LUKS  https://review.opendev.org/c/openstack/nova/+/88991205:18
opendevreviewAmit Uniyal proposed openstack/nova master: enforce remote console shutdown  https://review.opendev.org/c/openstack/nova/+/90182407:11
gibiartom: sean-k-mooney: nice catch on power mgmt. should I revert https://github.com/openstack-k8s-operators/nova-operator/pull/695 ? or we can live with the limitation?08:30
*** mklejn_ is now known as mklejn08:34
opendevreviewmelanie witt proposed openstack/nova master: Add backing_encryption_secret_uuid to BlockDeviceMapping  https://review.opendev.org/c/openstack/nova/+/90796008:36
opendevreviewmelanie witt proposed openstack/nova master: Support encrypted backing files for qcow2  https://review.opendev.org/c/openstack/nova/+/90796108:36
opendevreviewmelanie witt proposed openstack/nova master: Support cross cell resize with ephemeral encryption for qcow2  https://review.opendev.org/c/openstack/nova/+/90959508:36
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Introduce support for raw with LUKS  https://review.opendev.org/c/openstack/nova/+/88431308:36
opendevreviewmelanie witt proposed openstack/nova master: libvirt: Introduce support for rbd with LUKS  https://review.opendev.org/c/openstack/nova/+/88991208:36
noonedeadpunkhey folks. I guess I finally realized what is the usecase of root volume detach that was bothering me and which raised discussions here and there. And that is - volume resize. As in order to resize the disk, it must be in detached state. And you can't detach root volume.09:17
tkajinambauzas, hi. I just noticed I made a mistake in os-vif patch while discussion in another project and submitted a fix for it. I wonder we can merge this before we create os-vif release for caracal... https://review.opendev.org/c/openstack/os-vif/+/90968209:38
bauzastkajinam: I'm pretty busy those days, but I can take a look09:39
tkajinambauzas, thanks and sorry for bothering you. I've left a same comment in a release patch for os-vif...09:41
bauzastkajinam: that's cool, I'll review it today09:57
sean-k-mooney[m]gibi:  i think we can fix the edge cases and backport but we might want to keep a revirt ready incase we need it. my inclinations is it would be ok to have as a known issue in the context of a beta release but if we cant backport the bug fixes in time we might revert for ga10:05
sean-k-mooney[m]tkajinam:  i assume you would also like https://review.opendev.org/c/openstack/os-vif/+/90934110:08
sean-k-mooney[m]bauzas:  im +2 on both the os vif changes so let include them in the os-vif release10:09
sean-k-mooney[m]@gibi the isolate issue in particalar is a low probability of impacting people, the general live migration issue however is much more impactful.  so we should try and land rene’s fix for that.10:12
sean-k-mooney[m]gibi: looking at the second poc patch it looks like its also affecting live migration with pinned cpus10:17
sean-k-mooney[m]that is very surprising since i tought bauzas had tested that and it was covered10:17
bauzasI'm on a meeting 10:18
bauzasand I miss context, what are you guys discussing ?10:19
opendevreviewDoug Szumski proposed openstack/nova master: Revert "[libvirt] Live migration fails when config_drive_format=iso9660"  https://review.opendev.org/c/openstack/nova/+/90912210:34
gibisean-k-mooney[m]: OK i will open a revert with a hold10:34
gibibauzas: yet another bug in the power mgmt feature10:36
bauzaswhich is ?10:37
opendevreviewDoug Szumski proposed openstack/nova master: Revert "[libvirt] Live migration fails when config_drive_format=iso9660"  https://review.opendev.org/c/openstack/nova/+/90912210:38
sean-k-mooney[m]bauzas:  there are two, livemigation is broken and emultor thread policy=isolate10:39
bauzasack, any bug report to provide me ?10:39
gibisean-k-mooney[m]: the liv migration one is not specific to power mgmt isnt it?10:39
bauzassean-k-mooney: fwiw, I haven't tested live-migration 10:40
sean-k-mooney[m]i tought you had10:40
sean-k-mooney[m]but that explains why it was missed10:40
sean-k-mooney[m]there is a spereate live migration issue that is unrelated to power management10:41
sean-k-mooney[m]but there is also a power management live migration bug10:41
sean-k-mooney[m]we are not turning on the cores as part of pre live migrate10:41
sean-k-mooney[m]so thats just actully broken10:41
sean-k-mooney[m]the related issue is when cpu_shared_set is used and we dont have a numa topology10:42
sean-k-mooney[m]we dont update the cores of the vm for the desination10:42
sean-k-mooney[m]we have code up for review to fix that10:42
sean-k-mooney[m]that means when combined with mixed shared and dedicated cpus on the same host10:43
sean-k-mooney[m]its possible ot migrate a floating instnace to a core that is offline10:43
sean-k-mooney[m]if the cpu_shared_set and cpu_dedicated_set are not the same on all hosts10:43
sean-k-mooney[m]or rather the source and dest host10:44
sean-k-mooney[m]gibi:  the more i think about it the more im leaning towards truning it off by default again and trying to renable it after beta instead 10:44
bauzasI think I checked that we were turning the cores on on the right internal method that's called for *any* guest start10:45
bauzasbut maybe live-migration uses another path10:45
sean-k-mooney[m]bauzas:  the vm on the dest is started by libvirt not nova10:45
bauzasand then paused, right?10:45
sean-k-mooney[m]correct its started in the paused state and then libvirt unpauases it when it when we swap form executing on the source to the dest10:46
sean-k-mooney[m]so we need to power them on in pre-livemigration10:46
gibisean-k-mooney[m]: ack, we can land the revert and I reopen the tracker Jira10:46
bauzassean-k-mooney: I see then10:47
sean-k-mooney[m]on the plus side whitebox caught htis10:47
bauzaswhen is the target guest defined and paused ?10:47
sean-k-mooney[m]on the down side we are not yet running whitebox on nova10:47
bauzasI thought it was when we were calling qemu migrate10:48
gibiwould be nice to get bug reports i can link to. 10:48
sean-k-mooney[m]bauzas:  its defiend and paused by libvirt when we call migrateToUri310:48
bauzaswhich is not done in pre-livemigrate 10:48
sean-k-mooney[m]no10:48
bauzasbut I see the reason on turning on the core before10:48
bauzasthen in premigrate10:49
bauzasgotcha10:49
sean-k-mooney[m]its done after pre-livemigate10:49
sean-k-mooney[m]but its the call to libvirt on the source host that cause libvirt to create the vm in the paused sate on the dest10:49
bauzasyeah, same point than for the mdev things we discussed :)10:49
bauzasbad news is that internals of live-migration was blind for me in Antelope timle10:50
bauzasnow, this is no longer the case10:50
sean-k-mooney[m]yes its the same code paths as the mdevs10:50
gibihttps://github.com/openstack-k8s-operators/nova-operator/pull/702 revert is up10:50
sean-k-mooney[m]by the way nova-next is blocked10:51
sean-k-mooney[m]im going to fix that shortly10:51
sean-k-mooney[m]we are messing with the port bidnign profile for some reason in the post hook10:51
sean-k-mooney[m]we should not be doing that10:51
sean-k-mooney[m]gibi:  approved. im going to grab coffee and ill work on unblocking the gate when i get back10:54
opendevreviewDoug Szumski proposed openstack/nova master: Revert "[libvirt] Live migration fails when config_drive_format=iso9660"  https://review.opendev.org/c/openstack/nova/+/90912210:54
bauzassean-k-mooney: gibi: we could add a note in our upstream doc saying we don't support live-migration yet due to a bug11:04
gibiI would rather fix the bugs instead11:19
sean-k-mooneybauzas: same im not ok with doc fixes like that in general i would prefer an api block or an actual fix11:21
bauzascool then11:21
sean-k-mooneybauzas: artom has started workign on a fix11:22
bauzasgtk11:22
sean-k-mooneyso lets just help him do that and we can file an upstream bug to track it properly11:22
opendevreviewsean mooney proposed openstack/nova master: [S-RBAC] adapt nova-next for port's binding:profile field change  https://review.opendev.org/c/openstack/nova/+/90985912:11
sean-k-mooneybauzas: gibi ^ that will fix the gate blocker12:11
opendevreviewMerged openstack/os-vif master: Drop wrong stacklevel  https://review.opendev.org/c/openstack/os-vif/+/90968212:29
gibi+2 with some followup thinking12:30
artomgibi, sean-k-mooney, there's still something weird going on, https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/909785 isn't fully passing12:31
artomIt's _better_ with the two POC patches and Uggla's cpu_shared_set live migration patches, but still red12:32
sean-k-mooneygibi: we can likely refactor this to use python to set the extra atributes on the port12:55
sean-k-mooneyjust not right now12:55
sean-k-mooneywe can however just drop a python file into the hooks dir that import novas service user stuff and uses nova's code to set the my_key data12:56
gibisean-k-mooney: ack, i definitely wont block on this13:04
sean-k-mooneyi belvie we have unit tests that make sure we dont clobber but i agree the integration test was nice ot have13:07
gibiartom: Feb 22 03:45:17.085381 np0036833327 nova-compute[103912]: ERROR oslo_messaging.rpc.server NotImplementedError: Cannot load 'emulator_pins' in the base class13:08
sean-k-mooneyya so that depending on a patch that is not in the patch chain i belive13:08
sean-k-mooneygibi: i think the whitebox job is using two depend on again nova13:09
sean-k-mooneyhttps://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/90978513:09
sean-k-mooneyyep13:09
sean-k-mooneyor not13:10
gibiit seem the numa_info has no emulator_pin field13:10
sean-k-mooneyi tought it might be in https://review.opendev.org/c/openstack/nova/+/877773/813:10
gibia functional test in that patch probably can reproduce this issue13:11
sean-k-mooneythe emulator thread are ment to be included in cpu_pins13:11
sean-k-mooneygibi: one of the thing i disucssed with artom was https://github.com/openstack/nova/blob/master/nova/objects/instance_numa.py#L291-L29613:12
sean-k-mooneyis ment to have the emulator pinning in it too13:13
sean-k-mooneyactully looking at https://github.com/openstack/nova/blob/master/nova/objects/migrate_data.py#L14413:13
sean-k-mooneyemulator_pins is in the object13:14
sean-k-mooneyso artom is just missing an s13:14
sean-k-mooneysince it sa set since the a range13:14
sean-k-mooneyhum no the patch is correct which means its not populated?13:16
sean-k-mooneyhttps://github.com/openstack/nova/blob/3209f6551652cff7bef0b9d9719ab940dd05a0f8/nova/virt/libvirt/migration.py#L113-L11713:16
sean-k-mooney@artom i mostly aggre with this comment but i belive we dont alwasy set emulatorpin in the xml13:17
sean-k-mooneyhttps://github.com/openstack/nova/blob/3209f6551652cff7bef0b9d9719ab940dd05a0f8/nova/virt/libvirt/migration.py#L113-L12613:17
artomYeah, I think I need an if there13:18
artomIt won't be set if there's no emulator thread policy13:18
sean-k-mooneyif emulatorpin is not found you need to default it to vcpupin13:18
sean-k-mooneyso ya you need an if here https://github.com/openstack/nova/blob/3209f6551652cff7bef0b9d9719ab940dd05a0f8/nova/virt/libvirt/migration.py#L12713:19
sean-k-mooneywell13:19
sean-k-mooneyactully proably not there13:19
sean-k-mooneybut where we buidl teh dst_numa_info in the first place13:19
sean-k-mooneywell either works i guess13:19
sean-k-mooneyfor backport reason we proably want to have _update_numa_xml have the fallback if its not set in dst_numa_info13:20
sean-k-mooneybut we should fix where we are creating the numa info to also set it properly13:20
sean-k-mooneyso add somethign like13:22
sean-k-mooneyemulator_pin = info.emulator_pins if info.emulator_pins else info.cpu_pins.values()13:23
sean-k-mooney emulatorpin.set('cpuset',hardware.format_cpu_spec(emulator_pin))13:23
opendevreviewAmit Uniyal proposed openstack/nova master: enforce remote console shutdown  https://review.opendev.org/c/openstack/nova/+/90182413:42
*** haleyb|out is now known as haleyb14:52
opendevreviewPavlo Shchelokovskyy proposed openstack/nova master: Auto set heartbeat_in_pthread for wsgi services  https://review.opendev.org/c/openstack/nova/+/90988014:53
mnaserIt seems `nova-grenade-multinode` is broken in `stable/zed`.  Does anyone know of anything that sticks out15:31
mnaserhttps://review.opendev.org/c/openstack/nova/+/909098 we're eating up resources with folks rechecking it, we're at 3x, i think the job is deffo broken15:32
mnaserok, that's neutron being broken15:33
mnaserhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_39b/909098/2/check/nova-grenade-multinode/39bc664/controller/logs/screen-q-svc.txt15:33
frickleriiuc grenade jobs should be dropped from zed now that yoga is unmaintained?15:34
dansmithidk that we actually said that (removing grenade if the source is unmaintained) but that make sense to me15:43
clarkbhistorically we've dropped grenade jobs for N+1 when N is no longer maintained15:43
clarkbbeacuse the grenade jobs start at N and upgrade to N+1 and you very quickly bitrot15:44
dansmithyou mean historically...removed right? I meant in response to the recent policy to have branches that are specifically _unmaintained_ but still around15:46
clarkbcorrect historically15:46
dansmithin the past, IIRC, we'd remove a grenade when it upgrades from a branch that gets deleted because we can't land a fix to make it installable, but it's slightly less clear when the branch exists but is in the newly-minted unmaintained state15:47
opendevreviewArtom Lifshitz proposed openstack/nova master: POC: power up dedicated cores during pre_live_migration  https://review.opendev.org/c/openstack/nova/+/90980615:47
artomLet's see if the emulator_pins fix is enough15:48
fricklerthose grenade runs seem also have been in a weird situation where the stable/yoga branches were already removed in the repos, but still present in our in-image-git-cache. but I also don't understand why n-cond seems to get started, but doesn't produce any log15:53
melwittI dunno if yall have seen but it looks like nova-next is at a 100% fail rate, POST_FAILURE15:57
melwittDeleting allocation key from the binding:profile of the bandwidth aware port15:57
melwitt+ openstack port unset --binding-profile allocation port-normal-qos15:57
melwittForbiddenException: 403: Client Error for url: https://213.32.74.123:9696/networking/v2.0/ports/f5b273ab-1c98-44f6-9664-8c1a16d5abda, (rule:update_port and rule:update_port:binding:profile) is disallowed by policy15:57
melwittnot sure what changed that could have affected policy. I'll look around15:58
sean-k-mooneymelwitt: i have a fix for it16:02
melwittok thank goodness16:02
sean-k-mooneyhttps://review.opendev.org/c/openstack/nova/+/90985916:02
sean-k-mooneyi will readd the test coverage later16:02
sean-k-mooneytldr modifying binding_profile now needd a service token 16:03
sean-k-mooneyhence the 40316:03
melwittahh16:03
melwittsean-k-mooney: looks like there's at least one more thing that should be removed https://review.opendev.org/c/openstack/nova/+/909859/1/gate/post_test_hook.sh#17416:14
sean-k-mooney oh right16:15
sean-k-mooneyyep unset woudl also not work16:15
sean-k-mooneyim conflicted if we shoudl also remove that coverage16:16
sean-k-mooneyor if i shoudl bite the bullet and try and repalce it with a python script16:16
melwittyeah, I wondered that too. not sure how hard it would be to get something with service token working16:18
sean-k-mooneythe my-key stuff is not really that imporant16:18
sean-k-mooneybut the unset there is a key part of that test16:18
sean-k-mooneymelwitt: well we have nova avialabe in this env16:18
sean-k-mooneyso i was hoping we could just import some nova code for hat16:19
sean-k-mooneythis is running on the contoler16:19
sean-k-mooneyso the nova.conf should have all the setting set correctly16:19
sean-k-mooneyso in theory its improt the nvoa.conf module16:19
melwittyeah, it would16:19
sean-k-mooneycreate the neutron clinet form our clinet module16:19
sean-k-mooneyand do port update16:19
melwittI should know bc I added it but πŸ˜› 16:19
melwitthm k16:20
bauzasJayF: are you around ?16:20
JayFWhat's up?16:20
bauzasJayF: about https://review.opendev.org/c/openstack/nova/+/903915/ I wonder if you could provide a new revision due to sean-k-mooney's -1 ?16:21
bauzasalso, do we now have a Tempest job testing it ?16:21
JayFSean and I talked in depth about a testing plan earlier this week, and today and tomorrow is the time I set aside to implement it. At which point I'll re-stack all the sharding changes, make sure they pass CI, and do some manual testing16:22
JayFWe have implemented significant sharding testing in ironic for ensuring the API works properly, the second step I'm working on today is the scenario tests16:23
sean-k-mooneycool just an fyi tomorrow is a "rechage day" at redhat meaning none of us will be here tomorow16:23
sean-k-mooneybut we can take a look on monday16:23
JayFYeah I think I have all the information I need based on our conversation earlier, I just need to not have my day stolen by a thousand tiny conversations16:23
melwittsean-k-mooney: the new_websocket_client method is what gets called when a new request to the proxy comes in, so I also dunno why that would need to be called to close a connection ... ?16:32
sean-k-mooneyauniyal: can you try https://review.opendev.org/c/openstack/nova/+/901824/18/nova/console/websocketproxy.py#15416:37
auniyalsean-k-mooney, ack thanks16:46
auniyalsean-k-mooney, can we raise an Exception as invalid target token, inside  16:48
auniyalreason I am saying is https://github.com/openstack/nova/blob/master/nova/console/websocketproxy.py#L26516:49
sean-k-mooneythat is coming from self.do_proxy16:50
sean-k-mooneyright16:51
auniyalyes, so there some exception will be raised, like something happend in network or at client16:51
sean-k-mooneyso if we think about the reason why that might happen16:52
sean-k-mooneythe only reason i can think of is the client already disconnect before the time expired16:52
sean-k-mooneyin which case i dont think we should be raising an excption as that is an expected scenairo16:52
sean-k-mooneyso im not convinced raising an excption is correct16:53
auniyalack, 16:53
sean-k-mooneya debug level log woudl be fine16:53
sean-k-mooneybut do you have any other edge case in mind16:53
auniyalokay, also if something really happend at client side https://review.opendev.org/c/openstack/nova/+/901824/18/nova/console/websocketproxy.py#29416:53
auniyalno, so as you said, everytime we come to close connection we will have valid tsock16:54
auniyalack, will remove if-else then, thanks16:55
sean-k-mooneyyou have already protected agasint the socket being cloased with the OSError and the fileno being -116:56
sean-k-mooneyso i htink you have handled all the edgecase that are required there16:56
auniyalack, I'll just run tests locally and respin16:59
opendevreviewsean mooney proposed openstack/nova master: [S-RBAC] adapt nova-next for port's binding:profile field change  https://review.opendev.org/c/openstack/nova/+/90985916:59
sean-k-mooneymelwitt: by the way using blockcopy instead of blockrebase is a nice find17:06
sean-k-mooneymelwitt: it remiened me of something for future us17:07
sean-k-mooneywe currenly have some legacy code in hwo we do live snapshots to workaround some bugs with older version fo qemu/libvirt17:07
sean-k-mooneymy understanding is those issues have been fixed17:07
sean-k-mooneyso we may be able to simply that code alot in the future17:07
sean-k-mooneyby removing the legacy workaround17:08
melwittsean-k-mooney: yeah, I couldn't stop thinking about live snapshot not working so I asked in #virt and they advised to use blockcopy in order to provide encryption options17:08
melwittyeah, I think we likely could17:08
sean-k-mooneywe do this complciated dance where we start a rebase or copy jobs afte we copy a base iamge then abort it to do the live snapshot17:09
sean-k-mooneyi.e. we copy the backing file, start a jobs to sysnc the chagnes, briefly freese the guest file system and then abort17:09
sean-k-mooneythis https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L341217:10
melwittright yeah17:11
sean-k-mooneyso i need to do git balame locally because github hate doing it on that file17:11
sean-k-mooneybut that is a hack and should not be required17:12
bauzasJayF: (sorry, forgot to see your reply) sure, I'll lookup then your patch tomorrow (even if at RH, I'll work on tomorrow morning)17:12
JayFToday and tomorrow :) So look tomorrow but don't expect until Monday17:12
opendevreviewAmit Uniyal proposed openstack/nova master: enforce remote console shutdown  https://review.opendev.org/c/openstack/nova/+/90182417:14
sean-k-mooneymelwitt: so this dates form when we first added live snapshot https://github.com/uggla/nova/commit/46de2d1e2d0abd6fdcd4da13facaf3225c721f5e17:16
melwittquite a bit ago :)17:17
sean-k-mooneyyep so the simpeler ways of doign this were not "bug-free" in qemu 1.317:18
sean-k-mooneybut we havng used that in half a decade or more17:19
melwittyeah, agree it would be good to clean that up17:21
sean-k-mooneybased on https://libvirt.org/kbase/domainstatecapture.html we have a few options17:25
sean-k-mooneyi would hope we could use the direct backup functionaltiy or similar17:27
sean-k-mooneysomething like this https://libvirt.org/formatbackup.html#examples17:28
melwittah, ok17:29
sean-k-mooneythe thing is i dont know if any of that will work with encyption17:30
sean-k-mooneyif it does not virDomainSnapshotCreateXML may or we might just need to keep what we are doing17:31
sean-k-mooneybut it wooul dbe a good conversation to have with the virt folks about17:31
sean-k-mooney"if we were ot do it from scratch today what would you recommend"17:32
melwittyeah. I think they mentioned the real snapshot API would be the better way to do it (with encryption)17:32
sean-k-mooneythis one https://libvirt.org/html/libvirt-libvirt-domain-snapshot.html#virDomainSnapshotCreateXML17:33
sean-k-mooneyya qemu can aslo do memory snapshots and other fancy thigns via that17:34
sean-k-mooneywe can pass flags=VIR_DOMAIN_SNAPSHOT_CREATE_LIVE|VIR_DOMAIN_SNAPSHOT_CREATE_DISK_ONLY17:34
sean-k-mooneyand there is  VIR_DOMAIN_SNAPSHOT_CREATE_REUSE_EXT17:35
sean-k-mooneywhich alluse you ot resue a precreate file i think17:35
melwittyeah that's right17:36
sean-k-mooneyanway that a long way to say im +1 on the bockcopy usage and we may be able to simplfy later17:39
melwittack ++ :)17:40
opendevreviewDan Smith proposed openstack/nova master: Catch ImageNotFound on snapshot failure  https://review.opendev.org/c/openstack/nova/+/90531619:22
opendevreviewDan Smith proposed openstack/nova master: Support glance's new location API  https://review.opendev.org/c/openstack/nova/+/89103619:22
opendevreviewDan Smith proposed openstack/nova master: DNM: Test glance new location api  https://review.opendev.org/c/openstack/nova/+/89120719:22
melwittsean-k-mooney: nova-next is still unhappy :( https://zuul.opendev.org/t/openstack/build/3c2c7955a4b34112a377a857623d6a73/log/job-output.txt#3766219:25
melwittguess we can't check for healed port allocations19:26
sean-k-mooney really19:32
sean-k-mooneyor did i forget to delete on eof the checks19:33
sean-k-mooneyso tha tot me say that we have not configure bandwith qos properly19:36
sean-k-mooneyam i need ot go have somethign to eat but ok ill just drop all the port stuff19:36
sean-k-mooneyand if that does not work we can drop all the heal code19:36
mnaserhttps://bugs.launchpad.net/nova/+bug/2052915 is affecting nova right now but i have no idea where to look at the refernece19:39
sean-k-mooneythat sounds like neutron broke upgrades19:40
melwittsean-k-mooney: I'm not sure .. it's failing on "bandwidth_allocations=$(echo "$allocations" |  grep NET_BW_EGR_KILOBIT_PER_SEC)"19:40
sean-k-mooneyyep so if bandwith qos was working that allocation should exist19:40
melwittthe weird thing is that it's supposed to "echo "Failed to heal port allocations."" if the above returned "" but it's not echoing that19:41
sean-k-mooneyyep we have allcoations but not for that type19:42
melwittoh, I see. ok19:42
sean-k-mooneyso what i ment by not configre correctly is i think we may not have enabel the qos extionion in the job19:42
sean-k-mooneyor somethign liek that 19:43
opendevreviewsean mooney proposed openstack/nova master: [S-RBAC] adapt nova-next for port's binding:profile field change  https://review.opendev.org/c/openstack/nova/+/90985919:43
melwittdoesn't the fact that it used to work before the service token change mean the extension is present?19:44
sean-k-mooneyi would have to read the code but not nessiarlay19:44
melwittok19:45
sean-k-mooneythe allocation is create by nova but if we dont have teh qos extion is not loaded19:45
sean-k-mooneywhat will happen is neutron will not make a placement resouce request in teh port19:45
sean-k-mooneymelwitt: the hook was not asserting the bandwith resouce request existed before we healed19:46
sean-k-mooneyor that the the port has port resouce requests19:46
melwittπŸ˜΅β€πŸ’« 19:47
sean-k-mooney it does look like the qos plugin was loaded https://7afe9236b7eaaf244ae9-d98f699786987cf0f7a232f67c9b09f7.ssl.cf2.rackcdn.com/909859/2/check/nova-next/3c2c795/controller/logs/etc/neutron/neutron_conf.txt19:55
sean-k-mooneyand we see19:56
sean-k-mooney2024-02-22 18:53:27.154019 | controller | | resource_request        | {'request_groups': [{'id': '35e2b68f-9d87-54ff-a7c1-c0772986407e', 'required': ['CUSTOM_PHYSNET_PUBLIC', 'CUSTOM_VNIC_TYPE_NORMAL'], 'resources': {'NET_BW_EGR_KILOBIT_PER_SEC': 1000, 'NET_BW_IGR_KILOBIT_PER_SEC': 1000}}], 'same_subtree': ['35e2b68f-9d87-54ff-a7c1-c0772986407e']} |19:56
sean-k-mooneyin the neutron port19:56
sean-k-mooneyso the neutron port appears to have the port resouce reqquest in it19:57
sean-k-mooneyits also in allocations we fore we delete them19:57
sean-k-mooneymelwitt: but its not after we heal the allcoations19:58
sean-k-mooneyhttps://paste.opendev.org/show/bltzmAmf8ZoEE2NEimRR/19:58
sean-k-mooneymelwitt: i need to finish for today but i wonder if there is another regression here20:00
melwittsean-k-mooney: hm, ok. thanks for looking o/20:01
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L174920:06
sean-k-mooneyi would expec that to print somewhere firht20:06
sean-k-mooneyor this https://github.com/openstack/nova/blob/master/nova/cmd/manage.py#L1760C1-L1785C6220:07
sean-k-mooneyok im actully going to leave now but this is the neutron clien twe are using in nova_manage 20:16
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/network/neutron.py#L24820:16
sean-k-mooneywe are creating it with admin=true20:16
sean-k-mooneyand this is where the service auth token shoudl be enabled 20:16
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/network/neutron.py#L219-L23320:16
sean-k-mooneyso it shoudl have an admin client with service tokens20:17
sean-k-mooneybut the nova code seams to not be healign the port so we should see why20:18
melwittsean-k-mooney: thanks for the guidance20:20
melwittlooks like nova-ceph-multistore is at a 100% fail too with "Details: b'400 Bad Request\n\nThe Store URI was malformed.\n\n   '"21:55
melwitt😩 21:58
opendevreviewmelanie witt proposed openstack/nova-specs master: Update ephemeral encryption specs to reflect implementation  https://review.opendev.org/c/openstack/nova-specs/+/90765422:58

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