Comment 7 for bug 1835044

Stable branches of the requirements repo are effectively frozen for purposes of tracking external dependencies, and are merely used to indicate the known working versions contemporary with the coordinated release corresponding to that branch. Production deployments need to be using a security-supported distribution to obtain those instead. To rephrase, unless the memory leak you've found is preventing OpenStack from testing for potential regressions in proposed stable/queens branch changes, we should not be touching the pyroute2 version in the openstack/requirements repository's upper-constraints.txt file.