Comment 3 for bug 1923198

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/785606
Committed: https://opendev.org/openstack/neutron/commit/bfaf0ebc116cc5e3d5ae0fe5cd41bcc6fde58717
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit bfaf0ebc116cc5e3d5ae0fe5cd41bcc6fde58717
Author: Slawek Kaplonski <email address hidden>
Date: Fri Apr 9 15:28:41 2021 +0200

    Always use absolute path for custom kill-scripts

    When rootwrap was used to run custom kill-scripts, it worked fine with
    the executable name without full path as path was in the rootwrap's
    exec_dirs config option thus rootwrap was able to find it.

    But as we migrated to privsep it don't works like that anymore.
    It's better to use absolute path of the kill-script always and that
    patch changes to do it like that.

    Change-Id: I66d70304530935e2add3345aba6aa3c549a0a2df
    Closes-Bug: #1923198
    (cherry picked from commit e5ccfee6cfb503c3ba7cce816fae331dd017f3ce)