Asynchronous processing — python-neutronclient — branch stable/2026.2
Branch
stable/2026.2@596a9d99b188(14.0.0+ 2 maintenance commits) — repository https://opendev.org/openstack/python-neutronclient — analysed on 2026-11-01
None. The package has no bus consumer, periodic task, event listener, thread or background process. The inventory finds 0 RPC calls and 0 triggers ([_inventory/inventory_stable-2026.2.md](_inventory/inventory_stable-2026.2.md)). A command runs in the short-lived openstack process, and the library in the caller's thread.
No command has a --wait option, and none polls a status. For example, sfc port chain create returns with what the server answered.
Loops that exist
| Loop | Purpose | Stops when | Source |
|---|---|---|---|
_pagination | follow <collection>_links with rel=next | no such link, or no _links key | neutronclient/v2_0/client.py:383-401 |
retry_request | re-send GET, PUT, DELETE after a connection error, with retry_interval = 1 s | retries + 1 attempts; 0 extra attempts by default | neutronclient/v2_0/client.py:326-352 |
| delete commands | one attempt per name, continuing on failure | end of the list | neutronclient/osc/v2/logging/network_log.py:173-188 |
A server that always answers a next link makes _pagination loop forever: there is no page limit [inferred from the code; not run].
The retry was run against a closed port, with retry_interval set to 0 [observed connection-refused-retries].
Source: reverse-spec-python-neutronclient/05-async-processing_stable-2026.2.md. The _rewrite/ and _inventory/ files are not published on the site.