0a666bb10c
pyroute 0.6.6 introduced a new exception NetlinkDumpInterrupted which is raised when NLM_F_DUMP_INTR is set in the flags during dump of devices. The suggestion from pyroute developers is to retry in case of this exception (see [1]). For reference, this is how it was handled in neutron side: [2] [1] https://github.com/svinota/pyroute2/issues/874#issuecomment-1063139555 [2] https://review.opendev.org/c/openstack/neutron/+/833015 Change-Id: I6b5604266f29a585bb1e0f8e605ee5df523b5951
20 lines
694 B
Plaintext
20 lines
694 B
Plaintext
# The order of packages is significant, because pip processes them in the order
|
|
# of appearance. Changing the order has an impact on the overall integration
|
|
# process, which may cause wedges in the gate later.
|
|
|
|
pbr>=2.0 # Apache-2.0
|
|
|
|
Jinja2>=2.10 # BSD License (3 clause)
|
|
neutron-lib>=2.10.1 # Apache-2.0
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=6.1.0 # Apache-2.0
|
|
oslo.log>=3.36.0 # Apache-2.0
|
|
oslo.privsep>=2.3.0 # Apache-2.0
|
|
oslo.rootwrap>=5.15.0 # Apache-2.0
|
|
oslo.service>=1.40.2 # Apache-2.0
|
|
ovs>=2.8.0 # Apache-2.0
|
|
ovsdbapp>=1.4.0 # Apache-2.0
|
|
pyroute2>=0.6.6;sys_platform!='win32' # Apache-2.0 (+ dual licensed GPL2)
|
|
stevedore>=1.20.0 # Apache-2.0
|
|
tenacity>=6.0.0 # Apache-2.0
|