| gmaan | sean-k-mooney: gibi updated the graceful shurdown spec, please check - https://review.opendev.org/c/openstack/nova-specs/+/969299 | 00:10 |
|---|---|---|
| opendevreview | melanie witt proposed openstack/nova master: WIP Make QEMU_IMG_LIMITS process limits configurable https://review.opendev.org/c/openstack/nova/+/969538 | 00:34 |
| sean-k-mooney | gmaan: ack ill take a look in my morning | 00:44 |
| opendevreview | sean mooney proposed openstack/nova-specs master: add spec for resource tracker notifications https://review.opendev.org/c/openstack/nova-specs/+/967712 | 01:04 |
| opendevreview | Merged openstack/nova stable/2025.2: [ironic] Ensure unprovision happens for new states https://review.opendev.org/c/openstack/nova/+/968208 | 02:17 |
| *** mhen_ is now known as mhen | 02:17 | |
| opendevreview | Jay Faulkner proposed openstack/nova stable/2025.1: [ironic] Ensure unprovision happens for new states https://review.opendev.org/c/openstack/nova/+/969547 | 02:36 |
| opendevreview | zhou zhong proposed openstack/nova master: Create ephemeral and private secret when attaching encryptor https://review.opendev.org/c/openstack/nova/+/969019 | 02:50 |
| opendevreview | Merged openstack/nova master: ensure correct cleanup of multi-attach volumes https://review.opendev.org/c/openstack/nova/+/916322 | 07:00 |
| ratailor | gibi, sean-k-mooney bauzas could you please check this schema validation failure https://e88fada250d77d396ef5-a605dbf95134d478b50bec2dfa092555.ssl.cf1.rackcdn.com/openstack/146bb31174804bc5bebdba2b537c97db/testr_results.html related to https://review.opendev.org/q/topic:%22bp/show-instance-action-finish-time%22 | 07:59 |
| * bauzas can look briefly | 08:00 | |
| bauzas | but I want to give a swing on the left specs I didn't read yet | 08:00 |
| ratailor | In my local devstack env, I could get the instance action finish_time for create and attach_volume actions here https://paste.openstack.org/show/bWzmPfwfOZ9FQpfCpVPm/ | 08:00 |
| ratailor | bauzas, ack. | 08:01 |
| ratailor | gmaan, ^^ | 08:01 |
| bauzas | ratailor: I'm not really a tempest expert about schema validations | 08:06 |
| bauzas | I saw the patch that got -1 review.opendev.org/c/openstack/tempest/+/953331 but honestly I don't know why | 08:06 |
| ratailor | bauzas, ack. I think stephenfin can help here. ^^ | 08:07 |
| bauzas | I see you're depending on the nova patches | 08:07 |
| bauzas | so everything looks correct to me at a first glance | 08:07 |
| ratailor | bauzas, could you please review nova-spec and implementation and suggest if anything is missing. | 08:08 |
| bauzas | as I said, I'll do another round of open specs today | 08:08 |
| gibi | Details: HTTP response body is invalid (Additional properties are not allowed ('finish_time' was unexpected) | 08:09 |
| gibi | so I assume your nova patch added a new field to the response | 08:09 |
| gibi | that was not there before | 08:09 |
| ratailor | gibi, yes | 08:09 |
| gibi | and the tempest schema wasn't updated to accept that field in the new microvresion | 08:09 |
| ratailor | gibi, this is what I have done to update tempest schema | 08:21 |
| ratailor | https://review.opendev.org/c/openstack/tempest/+/953331/7/tempest/lib/api_schema/response/compute/v2_101/servers.py | 08:21 |
| jkulik | ratailor: looks like you're overwriting your changes to show_instance_action in line 19 again in line 40 | 09:00 |
| ratailor | jkulik, nice catch, thanks! | 09:13 |
| zigo | Hi there! | 09:36 |
| zigo | Looks like I have 2 unit tests failing in Nova's autopkgtest because our ppc64el servers are too fast, no ? | 09:36 |
| zigo | https://ci.debian.net/packages/n/nova/testing/ppc64el/66782181/ | 09:36 |
| zigo | gibi: ^ Your thoughts? | 09:39 |
| zigo | Should we add a sleep() in these unit tests? | 09:40 |
| opendevreview | Thomas Goirand proposed openstack/nova master: Fix race condition in DB updates https://review.opendev.org/c/openstack/nova/+/969745 | 10:57 |
| opendevreview | Dominik proposed openstack/nova master: Regression test for Placement allocations remaining during failed schedule (bug #2132020) https://review.opendev.org/c/openstack/nova/+/969251 | 11:12 |
| opendevreview | Dominik proposed openstack/nova master: Regression test for Placement allocations remaining during failed schedule https://review.opendev.org/c/openstack/nova/+/969251 | 11:19 |
| sean-k-mooney | zigo: we try not ot add sleeps in gerneal so ideally no | 11:39 |
| sean-k-mooney | zigo: we normally contol time in these test | 11:40 |
| sean-k-mooney | so it looks like the test has a race condtion. if we add a sleep it woudl be somethign liks sleep(0.001) | 11:41 |
| sean-k-mooney | zigo: i think gibi fixed a few cases likt this before when they started workign on the eventlet removal | 11:42 |
| stephenfin | ratailor: bauzas: you need to define a new schema for tempest before the nova patch can merge. gmaan is a better person again to ask https://github.com/openstack/tempest/tree/8e2e854051b247ce914982ab0c3c0ed5e2f01b09/tempest/lib/api_schema/response/compute | 12:02 |
| stephenfin | hopefully the duplication can be removed once the final patches merge against nova (hint hint) | 12:02 |
| stephenfin | *final OpenAPI patches | 12:03 |
| opendevreview | Thomas Goirand proposed openstack/nova master: Fix race condition in DB updates https://review.opendev.org/c/openstack/nova/+/969745 | 12:06 |
| ratailor | stephenfin, ack. | 12:12 |
| zigo | sean-k-mooney: You're wrong, IMO. | 12:19 |
| zigo | sean-k-mooney: The issue is getting 2 timestamps in less than 1 second. | 12:19 |
| zigo | Then they are equal, and later on, the test checks if they are NOT equal. | 12:19 |
| sean-k-mooney | zigo: what im saying is we normlaly try to decouple the unit test entirly form teh infra | 12:23 |
| sean-k-mooney | for example by mockign time.now() so that each call woudl increment by 1 second or some other way | 12:23 |
| sean-k-mooney | zigo: for functional test we might uses sleeps as we try to avoid mockign if we cna btu for unit test we usually mock otu the tiem functions | 12:24 |
| opendevreview | Merged openstack/nova stable/2025.1: [ironic] Ensure unprovision happens for new states https://review.opendev.org/c/openstack/nova/+/969547 | 12:37 |
| zigo | sean-k-mooney: Oh ok, I get it now. Then I can just do that (ie: do timestamp2 = timestamp+1) | 12:40 |
| zigo | Though it may be harder than just mocking the timestamp function, no? I don't know how the updated_at is generated. | 12:44 |
| sean-k-mooney | we can likely mock time.now() and that shoudl be enough i think but i woudl have to look at the specific tests | 12:51 |
| gibi | zigo: sean-k-mooney: we should have a fixture for the time.now() already in our tests maybe it is not used in those specific tests | 12:55 |
| gibi | but overall I agree to make the test independent of the value of time.now | 12:55 |
| zigo | I'd say: please, feel free to takeover my patch and make it better. | 12:56 |
| zigo | I don't have enough available time to do so. | 12:56 |
| gibi | I don't have time for that at the moment too. sorry | 12:59 |
| sean-k-mooney | gibi: we do have a fixture for that yes but i didnt check if it was used either | 14:14 |
| sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/test.py#L828 | 14:14 |
| sean-k-mooney | that works a littel defently then i descrbed making all calsl return a fixed time | 14:15 |
| sean-k-mooney | in this case the test logic is either incorect or we need one to monotmicly march forward to fit this test | 14:16 |
| sean-k-mooney | https://github.com/openstack/nova/blob/master/nova/tests/functional/test_nova_manage.py#L2172-L2175 | 14:16 |
| opendevreview | Dominik proposed openstack/nova master: Regression test for Placement allocations remaining during failed schedule https://review.opendev.org/c/openstack/nova/+/969251 | 14:24 |
| opendevreview | Dominik proposed openstack/nova master: Remove Placement allocations in the broken build cleanup https://review.opendev.org/c/openstack/nova/+/968446 | 14:39 |
| opendevreview | Merged openstack/nova-specs master: Propose Spec 1 of Graceful shutodwn for 2026.1 https://review.opendev.org/c/openstack/nova-specs/+/969299 | 14:45 |
| gibi | dansmith: sorry no progress yet with the utils.spawn issue. I was distracted with other things | 15:08 |
| dansmith | gibi: no worries, I found it while doing other things, so once I found the issue I went back to those things | 15:08 |
| gibi | dansmith: but now I found the change I had a hunch about https://review.opendev.org/c/openstack/nova/+/953121/2/nova/tests/fixtures/nova.py#b1248 so before this change the utils.spawn in untit test executed the passed in function and *raised back* any exception. But that is semantically wrong as only utils.spawn(f).wait() should raise it. So I changed the unit test fixture semantics to not raise from | 15:18 |
| gibi | __init__ | 15:18 |
| gibi | so that is way in the past the test got the exception without the code under test ever waiting for the result of the spawned thread | 15:19 |
| gibi | a/way/why/ | 15:19 |
| gibi | s/way/why/ | 15:19 |
| dansmith | gibi: okay but we don't wait() on the result of the spawn there, that's the point right? | 15:20 |
| gibi | right. the live migration code never wait for that spawned thread to finish hence it cannot get the exception from it | 15:21 |
| dansmith | we should have wait()ed on the result of the greenthread before, so the exception showed up at that point, so it was probably not semantically right before, but we still need a change | 15:21 |
| sean-k-mooney | dansmith: gibi thanks for the review. ill remove the storage stuff and try and adress the other comments | 15:21 |
| gibi | dansmith: I don't know yet if the livemigration code needs to wait or not. In the past it did not waited. | 15:22 |
| dansmith | gibi: but if it doesn't we would never notice if we failed to call guest.migrate() or raised any exception within | 15:23 |
| dansmith | this example was a bad mock, but it stands for any failure within the thread we spin up to do the actual migration | 15:25 |
| gibi | yeah I got you. The errors in the thread are either handled within that thread or lost and the migration_monitor just detects the failed migration independetly | 15:27 |
| dansmith | will it? it will eventually time out or something, but I'm not sure that's really the same | 15:27 |
| dansmith | but yeah, either way.. I think we need to collect the result regardless | 15:27 |
| dansmith | and certainly by not doing it here, any unit testing we do will always pass no matter what happens inside that "thread" | 15:28 |
| gibi | yeah I'm not against collecting the result | 15:28 |
| gibi | I will do some trials locally what happens in devstack if I break the call to guest.migrate() | 15:28 |
| dansmith | okay | 15:29 |
| gibi | do I understand correctly that such result collection is anyhow after the monitor already finished the monitoring so the migration either happened or failed and we just want to get better logs by knowing any exceptions from the thread? | 15:31 |
| dansmith | sean-k-mooney: quick before you revise, I think storage_fsid is fine.. we could even make that support(able) on other things by saying "put a .fsid file with a uuid in the root and we'll report it".. it's the local|shared I think is a lie :) | 15:32 |
| dansmith | gibi: I'll have to go back and look and the monitor behavior if nothing ever starts | 15:32 |
| gibi | OK. No need to jump back yet. I will verify that locally. I just wanted to see that my general understading is not totally wrong | 15:33 |
| dansmith | kinda looks like it will wait forever if DOMAIN_JOB_NONE right? | 15:33 |
| opendevreview | Merged openstack/nova master: pre-commit: Bump versions https://review.opendev.org/c/openstack/nova/+/966089 | 15:33 |
| gibi | yeah there is a loop | 15:33 |
| dansmith | we can probe the future in that loop if we pass it right? and stop waiting if the thread has ended for any reason? | 15:34 |
| gibi | future.done() is non blocking so yes we can probe | 15:35 |
| dansmith | right | 15:36 |
| dansmith | if future.done(): future.result() | 15:36 |
| dansmith | ^ will raise where we're already try..excepting for migration failure | 15:36 |
| dansmith | if done inside the loop | 15:36 |
| gibi | yeah I think so | 15:38 |
| sean-k-mooney | dansmith: ok so if i removed storage_type and kept stroage_fsid you woudl be fine with that | 15:39 |
| sean-k-mooney | and sure we culd make that declarbale in some way vai a file or config option where we cant dicusver it easily. | 15:39 |
| dansmith | sean-k-mooney: yes, I called out storage_type specifically because we can't know.. we _can_ know storage_fsid | 15:40 |
| sean-k-mooney | ack | 15:40 |
| dansmith | man, I do not get it.. | 15:41 |
| sean-k-mooney | oh you mean each compute cant know that its shared even if its nfs | 15:41 |
| sean-k-mooney | oh ya your right | 15:41 |
| opendevreview | Takashi Kajinami proposed openstack/nova master: libvirt: Use firmware auto-selection by libvirt https://review.opendev.org/c/openstack/nova/+/969132 | 15:41 |
| dansmith | correct | 15:41 |
| dansmith | sometimes I load the spec and gerrit shows me tons of unresolved comments and other times, not. | 15:41 |
| sean-k-mooney | ya... | 15:41 |
| sean-k-mooney | i noticed that too for the last few days | 15:41 |
| sean-k-mooney | i dont know if its a recent regression or browswer caching | 15:42 |
| gibi | dansmith: heh we have a convoluted way already in place to detect early end of the thread. The code adds a callback to the future to execute when it finishes. That callback sets finish_event (which is an Event) that is passed into the monitoring loop and checked there https://github.com/openstack/nova/blob/5d3d0c870a1c37dcd6ce9cd0d542282c7c7994f3/nova/virt/libvirt/driver.py#L11405 | 15:45 |
| gibi | so the monitoring loop detects the early end of the thread via that event | 15:46 |
| dansmith | gibi: that detects when the future ends yes, but doesn't care why | 15:46 |
| gibi | (still it does not collect the resutl) | 15:46 |
| dansmith | right | 15:46 |
| dansmith | yep | 15:46 |
| dansmith | gibi: fwiw, I wasn't actually seeing that callback be called when I was pdb'ing the unit test | 15:47 |
| dansmith | but that might be specific to the unit test environment or something | 15:47 |
| gibi | the unit test fixture calles the callback right when it is registered :/ | 15:47 |
| dansmith | ah | 15:47 |
| gibi | that fixture is suboptimal to serve the unit test needs | 15:48 |
| gibi | OK. I'm convinced enough now that collecting the result after the monitor make sense | 15:48 |
| dansmith | do we actually need the convoluted done event? is that maybe to give the same behavior in both models or something, instead of just checking future.done? | 15:49 |
| gibi | as far as I think we don't need the convoluted way, we can just use future.done instead within the monitor | 15:50 |
| dansmith | okay that might be better anyway then | 15:51 |
| gibi | using the future directly removes the callback which is a nice symplification | 15:51 |
| dansmith | yup | 15:51 |
| gibi | I have context now should I just pick you patch up and update it? or you would like to do it? | 15:51 |
| dansmith | you're welcome to, but if you need to do other stuff I can do it also | 15:53 |
| gibi | I take it. I need to write some code to keep my sanity :) | 15:53 |
| dansmith | yeah, I've been just reviewing for weeks now.. sanity gone :( | 15:54 |
| gmaan | dansmith: gibi: bauzas: I did one ammended in graceful shutdown backlog spec as spec3, please check. it is for backlog only and to keep it out of scope from the scope of this cycle spec https://review.opendev.org/c/openstack/nova-specs/+/969543 | 16:21 |
| gibi | gmaan: make sense to me thanks. | 16:22 |
| opendevreview | sean mooney proposed openstack/nova-specs master: add spec for resource tracker notifications https://review.opendev.org/c/openstack/nova-specs/+/967712 | 16:30 |
| opendevreview | Ghanshyam proposed openstack/nova-specs master: Follow up fixes for graceful shutdown spec https://review.opendev.org/c/openstack/nova-specs/+/969813 | 16:48 |
| gmaan | gibi: bauzas ^^ quick follow up for fixing some comments | 16:50 |
| gmaan | and thanks dansmith sean-k-mooney gibi bauzas for review and help on the shaping graceful shutdown specs. | 16:51 |
| gmaan | ratailor: most probably it is missing schema but let me review todaty | 16:52 |
| opendevreview | Merged openstack/nova-specs master: Follow up fixes for graceful shutdown spec https://review.opendev.org/c/openstack/nova-specs/+/969813 | 17:07 |
| opendevreview | sean mooney proposed openstack/nova-specs master: Repropose and update cyborg vGPU (mdev) support https://review.opendev.org/c/openstack/nova-specs/+/967515 | 17:18 |
| sean-k-mooney | bauzas: gibi i adresss bogdans feedback and the other open comments if you have time to review that too. | 17:22 |
| opendevreview | Balazs Gibizer proposed openstack/nova master: Collect result of _live_migration_operation https://review.opendev.org/c/openstack/nova/+/969501 | 17:51 |
| opendevreview | sean mooney proposed openstack/nova-specs master: Repropose and update cyborg vGPU (mdev) support https://review.opendev.org/c/openstack/nova-specs/+/967515 | 18:08 |
| opendevreview | Jay Faulkner proposed openstack/nova stable/2024.2: [ironic] Ensure unprovision happens for new states https://review.opendev.org/c/openstack/nova/+/969833 | 18:17 |
| JayF | The next step backport for the ironic bugfix, for your consideration ^^^^ :) thank you! | 18:17 |
| melwitt | dansmith: EZ io=native config patch that you have expressed some interest before 😇 https://review.opendev.org/c/openstack/nova/+/964848 | 19:06 |
| dansmith | oh yeah I literally have it open already | 19:12 |
| dansmith | I shall hit for sure eventually | 19:12 |
| sean-k-mooney | the only concern i have with that | 19:13 |
| melwitt | :) | 19:13 |
| sean-k-mooney | is live migration btween host with diffent values | 19:13 |
| sean-k-mooney | i assume we need to make sure we do not change the mode during a live mifation | 19:13 |
| sean-k-mooney | *migration | 19:13 |
| sean-k-mooney | its ok if it change on hard reboot or cold migraion | 19:14 |
| sean-k-mooney | melwitt: did you try that | 19:15 |
| sean-k-mooney | we coudl also tweak one of the zuul jobs to enable this | 19:15 |
| melwitt | no, I did not | 19:16 |
| sean-k-mooney | for example the normal nova-live-migration job which uses iscsi | 19:16 |
| melwitt | yeah that sounds like it would be easy to try, just configure the subnode different and run the job? | 19:17 |
| sean-k-mooney | yep | 19:18 |
| sean-k-mooney | we have live_migration_back_and_forth enabled in that job | 19:18 |
| melwitt | in general I wasn't thinking config like this would be different than two computes having various config not matching but maybe none of the others affect xml | 19:18 |
| sean-k-mooney | so if you enable it on one or both host it will give us interesting data | 19:19 |
| melwitt | ok, I'll try it | 19:19 |
| sean-k-mooney | well libvirt might not care im currnetly tying to see if this is confire a backend option or not | 19:20 |
| sean-k-mooney | some thing it will happly allow change in a live migrtion and others it wont an i have never played with seting io="threads" vs io="native" ectra difently on a migration | 19:22 |
| sean-k-mooney | melwitt: related question do we just let libvit choose for local disks or is that also hardcoded to native today | 19:23 |
| melwitt | sean-k-mooney: yes local disks are left to default. this io=native hard-coded thing is only for iSCSI, NFS, and FC Cinder volumes | 19:24 |
| sean-k-mooney | ack | 19:25 |
| melwitt | it comes from this spec from mitaka https://specs.openstack.org/openstack/nova-specs/specs/mitaka/implemented/libvirt-aio-mode.html | 19:25 |
| sean-k-mooney | ya i was asking ai about libvirt io modes and that actullythe firt link it found | 19:27 |
| sean-k-mooney | so it seam like we did adopt the best practices that were recommend at the tiem and optied into native but we pessimsed some backend so the change makes sens | 19:27 |
| melwitt | oh heh | 19:28 |
| sean-k-mooney | number 2 was https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/virtualization_tuning_and_optimization_guide/sect-virtualization_tuning_optimization_guide-blockio-io_mode which is a littel more useful but im actully surpised this is not coverd in the libvirt domain xml docs | 19:29 |
| sean-k-mooney | they are useable pretty good at docuemtning the difent values | 19:29 |
| melwitt | yeah I guess it only says "The optional io attribute controls specific policies on I/O; qemu guests support "threads" and "native" Since 0.8.8, io_uring Since 6.3.0 (QEMU 5.0)." in https://libvirt.org/formatdomain.html#hard-drives-floppy-disks-cdroms | 19:31 |
| sean-k-mooney | ah yep just roudn it deep in the driver section | 19:32 |
| sean-k-mooney | unfortuetly you cant deep link that far into the doc | 19:33 |
| sean-k-mooney | io_uring support could be very interesting in teh future | 19:33 |
| melwitt | yeah I wish their doc pages had more fine grain links | 19:34 |
| sean-k-mooney | https://kb.blockbridge.com/technote/proxmox-aio-vs-iouring/ is interesting but i have not had time to read i tyet | 19:39 |
| sean-k-mooney | finding 1 "IOThreads significantly improve performance for most workloads" well i guess its a good thing we are finally going to turn them on | 19:39 |
| melwitt | haha yeah. I saw similar things when i first started reading up on io=native vs io=threads | 19:42 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 19:42 |
| gmaan | ratailor if you see it when online. I commented in tempest change. maybe you can run the same tests which is executing same action on isntance in your devstack end and see why finsih_time is None - https://review.opendev.org/c/openstack/tempest/+/953331 | 19:47 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 19:47 |
| gmaan | there should be difference between API, action you call via tempest test or osc but somewhere it is missing the recording of finish time. | 19:48 |
| sean-k-mooney | gmaan: os that comment thread on the swap voluem one only show up on v2 for me | 19:52 |
| sean-k-mooney | i didnt see that in the latest revsion at all when i went to revie it | 19:52 |
| gmaan | sean-k-mooney: yeah, there are multiple way to do lile task state as melwitt suggested early or checking migration status or based on request (your latest comment). but we should not make RPC call whenever we have GET volume attachment call | 19:53 |
| sean-k-mooney | ya i agree | 19:54 |
| gmaan | and that is something we need to agree as design in spec and should not delay to implementation. | 19:54 |
| sean-k-mooney | i just didnt see that rad on the spec yestready because the commens are not propagating the way i expect | 19:54 |
| melwitt | gmaan: yeah, thanks for commenting on that spec. it seemed crazy to me to do the RPC call about swap progress every time when 99% of the time no swap would be in progress | 19:54 |
| gmaan | true | 19:55 |
| gmaan | sean-k-mooney: comment propagation in gerrit is really weird. i hate that many times :) | 19:56 |
| gmaan | last spec I am going through today is rajesh finish_time one, and previous comments are all lost there either due to Gerrit or they are marked resolved before agreement was reached. that is adding more time to review specs | 19:58 |
| sean-k-mooney | ya i normlly try not to mark thing resovled unlless i made the change that was requested | 20:02 |
| sean-k-mooney | even then i generaly prefer for non trivial thing if the orginal review acks it intesad of me | 20:02 |
| gmaan | yeah | 20:04 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 21:26 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 21:27 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 21:31 |
| opendevreview | melanie witt proposed openstack/nova master: Make QEMU_IMG_LIMITS process limits configurable https://review.opendev.org/c/openstack/nova/+/969538 | 22:10 |
| melwitt | sean-k-mooney: fyi the DNM patch test run finished -- nova-live-migration passes if [libvirt]use_default_aio_mode_for_volumes = true on the subnode only https://review.opendev.org/c/openstack/nova/+/969844 | 22:30 |
| melwitt | looks like live_migrate_back_and_forth was not enabled though | 22:33 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 22:35 |
| melwitt | running again with live_migrate_back_and_forth = true ^ | 22:35 |
| opendevreview | melanie witt proposed openstack/nova master: Reproducer for bug 2016173 https://review.opendev.org/c/openstack/nova/+/946222 | 22:37 |
| opendevreview | melanie witt proposed openstack/nova master: Call volume detach rollback API if detach fails https://review.opendev.org/c/openstack/nova/+/880399 | 22:37 |
| opendevreview | melanie witt proposed openstack/nova master: DNM test io=threads => io=native live migration https://review.opendev.org/c/openstack/nova/+/969844 | 23:31 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!