This issue was fixed in the openstack/nova 27.5.1 release.
** Changed in: nova/antelope
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2065927
Title:
cpu power management can fail with OSError: [Errno 16] Device or
resource busy
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) 2024.1 series:
Fix Committed
Status in OpenStack Compute (nova) antelope series:
Fix Released
Status in OpenStack Compute (nova) bobcat series:
Triaged
Bug description:
as reported downstream in https://issues.redhat.com/browse/OSPRH-7103
if you create a vm, reboot the host, start the vm,
and finally delete it.
that may fail
May 16 15:54:26 edpm-compute-0 nova_compute[3396]: Traceback (most recent
call last):
May 16 15:54:26 edpm-compute-0 nova_compute[3396]: File
"/usr/lib/python3.9/site-packages/nova/filesystem.py", line 57, in write_sys
May 16 15:54:26 edpm-compute-0 nova_compute[3396]: fd.write(data)
May 16 15:54:26 edpm-compute-0 nova_compute[3396]: OSError: [Errno 16] Device
or resource busy
this prevents the VM from being deleted on the inial request but it
can then be deleted if you try again
this race condition with the kernel is unlikely to happen and appeared
to be timing related.
i.e. there is a short period of time where onlineing or offlining of a
CPU may not be possible
to mitigation this nova should retry the operation with a backoff and then
eventually squash the error allowing the vm to delete without failing if we
cant offline the core.
power management of the core should never block or cause the vm delete to
fail.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2065927/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
