Oh !! Thanks a lot, really.
 
Indeed, I installed kolla-ansible 12.0, install wallaby (it works perfectly… expect Vpnaas), then I changed "wallaby" to « victoria » in globals.yml.

And in Wallaby's notes, there is the sentence:
The Karbor project is no longer maintained and retired since the Wallaby cycle. Its support and roles are also removed since Wallaby cycle.
So, it's not normal that it doesn't work. I understand…. There is a lot of things, it’s not easy to do the right thing the first time.

On the other hand ... and I hope not to abuse, I am not sure I understand "clone https://opendev.org/openstack/kolla-ansible".
Do you have to uninstall kolla-ansible 12 before putting 11?
How do you do "pip install that directory then"? Really sorry for these stupid questions, but I'm afraid to mess things up.

Franck 


Le 25 juil. 2021 à 18:00, Radosław Piliszek <radoslaw.piliszek@gmail.com> a écrit :

On Sun, Jul 25, 2021 at 2:52 PM Franck VEDEL
<franck.vedel@univ-grenoble-alpes.fr> wrote:

Hello

Hello Franck,

Having had no help with my Vpnaas (centos wallaby) problem, I came back to Victoria because I know from having tested that Vpnaas works as it should under Victoria.
A few weeks ago, I had the opportunity to use 3 test servers, I had set up Victoria (with Centos and kolla-ansible). No problem, everything was working as I wanted it to.
I have since set up 3 new servers to set up an Openstack for my students.
if i install Wallaby, no Vpnaas, and I need VPNaaS…. So Victoria.

if I install Victoria, and this is the 1st time that this happens to me, horizon does not work. The horizon docker does not start.
The "docker logs horizon" command ends with the following 3 lines:
++ config_karbor_dashboard
++ for file in $ {SITE_PACKAGES} / karbor_dashboard / enabled / _ * [^ __]. py
/ usr / local / bin / kolla_extend_start: line 121: ENABLE_KARBOR: unbound variable

This error suggests you are using Kolla Ansible Wallaby or later to
deploy Victoria.
You probably just set "openstack_release" to "Victoria" without
downgrading Kolla Ansible to a supported version.
There is a reason why "openstack_release" is commented with "Do not
override this unless you know what you are doing.". ;-)
It is only really meant to be used for very specific tasks, not really
meant for regular users.
Please have a look at
https://docs.openstack.org/releasenotes/kolla-ansible/victoria.html
The latest release for Victoria is 11.0.0 but there are lots of
unreleased fixes so I advise you to just clone
https://opendev.org/openstack/kolla-ansible
checkout stable/victoria
and pip install that directory then.
It will fix your current issue.

-yoctozepto