diff options
Diffstat (limited to 'results/classifier/accel-gemma3:12b/kvm/1994002')
| -rw-r--r-- | results/classifier/accel-gemma3:12b/kvm/1994002 | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/results/classifier/accel-gemma3:12b/kvm/1994002 b/results/classifier/accel-gemma3:12b/kvm/1994002 new file mode 100644 index 000000000..2bf1494eb --- /dev/null +++ b/results/classifier/accel-gemma3:12b/kvm/1994002 @@ -0,0 +1,24 @@ + +[SRU] migration was active, but no RAM info was set + +While live-migrating many instances concurrently, libvirt sometimes return internal error: migration was active, but no RAM info was set: +~~~ +2022-03-30 06:08:37.197 7 WARNING nova.virt.libvirt.driver [req-5c3296cf-88ee-4af6-ae6a-ddba99935e23 - - - - -] [instance: af339c99-1182-4489-b15c-21e52f50f724] Error monitoring migration: internal error: migration was active, but no RAM info was set: libvirt.libvirtError: internal error: migration was active, but no RAM info was set +~~~ + +From upstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2074205 + +[Impact] + + * Effects of this bug are mostly observed in large scale clusters with a lot of live migration activity. + * Has second order effects for consumers of migration monitor such as libvirt and openstack. + +[Test Case] +Steps to Reproduce: +1. live evacuate a compute +2. live migration of one or more instances fails with the above error + +N.B Due to the nature of this bug it is difficult consistently reproduce. + +[Where problems could occur] + * In the event of a regression the migration monitor may report an inconsistent state. \ No newline at end of file |