I explained in a first message last week the problem with vpnaas:
Neutron-l3-agent logs says: Command: ['ipsec', 'whack', '--status'] Exit code: 33 Stdout: Stderr: whack: Pluto is not running (no "/run/pluto/pluto.ctl »)
when I do the same things with Victoria (on a test lab, not on my student servers), no problem with vnaaas, no problem with horizon.
On the servers for, I try Victoria. Problem with the horizon container, but no logs, I don't understand the problem (I never had a problem with horizon). The only thing that's new: Rocky instead of Centos (I don't know whether to use Stream or Rocky, it's tricky this story).
How to find the horizon problem without logs? How to find the problem that prevents this container from starting (all the others are UP)
On Fri, Jul 16, 2021 at 9:36 AM Franck VEDEL<franck.vedel@univ-grenoble-alpes.fr> wrote:
Hello.
Hello,I try one last time to get some help, answers to my questions because I have been trying for 2 weeks to get the vpnaas service to work under Wallaby, without success. Still, I have no problem under Victoria with vpnaas. However, on my last installation which must work in September (to be used by students), without my understanding why, the horizon container of my centos (rocky) / kolla-ansible / victoria installation does not want to launch and I do not have no logs. So, can't use Victoria. I am trying Wallaby, everything works except vpnaas.
My questions: how to get the logs of this hoorizon container which does not start (restart every 20 seconds)?
how to know if it is a bug in wallaby with vpnaas?
Really thank you if anyone can help me move forward.
I don't really have experience with Neutron VPNaaS. Is there anythingmore specific than "it doesn't work"? What's the behaviour in V andwhat's in W?Regarding Horizon - it is known to be working. Perhaps it's breakingdue to some customisation. Did you check the docker logs on theHorizon container? They should contain a hint as to why the restart ishappening.-yoctozepto