Does a client-side timeout cancel in-flight work in OpenStack's Nova, Neutron, and Cinder?

OpenStack has no request-wide cancellation token or deadline propagation standard shared across its services. When a client times out or disconnects, work already accepted by Nova, Neutron, or Cinder generally continues server-side unless it is explicitly aborted through a service-specific action such as Nova's delete or force-delete.

The open question is how deadlines compose across layers. Timeouts are configured per service through oslo.config options such as rpc_response_timeout, and the effective limits can differ between the REST API layer, the message queue, and the driver or hypervisor. Whether an explicit abort actually halts a build or attach depends on driver support and the current task state, and both defaults and abort semantics vary between releases, so end-to-end behavior is not guaranteed to be consistent.

• Does a client-side timeout or disconnect cancel in-flight server-side work, or does the operation continue and require later reconciliation?
• Which configuration options determine the effective end-to-end deadline for a multi-step operation across the API, RPC, and driver layers?
• Where are partially created resources expected to be cleaned up when no abort path succeeds?