So, I think I see where it is failing, but I'm not quite sure how to
resolve. It appears that the functional test for the namespace module and
strongswan module, will end up invoking neutron-vpn-netns-wrapper script,
which is setup to point to
neutron-vpnaas/services/vpn/common/netns_wrapper.py.
The latter. If you look at Jenkins results for 168115, it shows that there
is an invalid config file at /etc/neutron/rootwrap.conf. However, it should
be accessing
/opt/stack/new/neutron-vpnaas/.tox/dsvm-functional-sswan/etc/neutron/rootwrap.conf.
The deploy_rootwrap.sh call in tox.ini should
The tox.ini entry for dsvm-fullstack sets OS_ROOTWRAP_CMD=sudo
{envbindir}/neutron-rootwrap {envdir}/etc/neutron/rootwrap.conf (and
something similar for rootwrap-daemon).
Is this the answer you were looking for, or are you saying OS_ROOTWRAP_CMD
doesn't appear to be honoured in your case?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/24/2015 03:48 PM, Paul Michali wrote:
Hi, I'm floundering a bit, and could use some guidance on this...
For the neutron-vpnaas repo, I am trying to modify the functional
jobs (dsvm-functional and dsvm-functional-sswan) to act in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/24/2015 04:02 PM, Ihar Hrachyshka wrote:
On 04/24/2015 03:48 PM, Paul Michali wrote:
Hi, I'm floundering a bit, and could use some guidance on
this...
For the neutron-vpnaas repo, I am trying to modify the
functional jobs
