All in one test environment with contrail-ansible-deployer issue

[server...@gmail.com]

Hi All,

I'd like to get an all in one deployment of TF going. A couple weeks ago contrail-ansible-deployer was working fine if I had the most recent CentOS kernel. However, a few days after that was working I started getting all kinds issues on a new deployment--CPU lockups and df would hang and kolla-contrail would not install. I moved to device mapper and was able to get kolla contrail to depoy, but now I'm running into an issue with vrouter. The vrouter agent init container failed, but I manually added the vrouter kernel module. Now I get this error:

[root@tungsten-1 centos]# docker logs vrouter_vrouter-agent_1 | tail
INFO: Preparing /etc/contrail/contrail-lbaas-auth.conf
Config file </etc/contrail/contrail-vrouter-agent.conf> parsing completed.
log4cplus:ERROR No appenders could be found for logger (SANDESH).
log4cplus:ERROR Please initialize the log4cplus system properly.
contrail-vrouter-agent: controller/src/vnsw/agent/vrouter/ksync/ksync_memory.cc:107: void KSyncMemory::Mmap(bool): Assertion `0' failed.
/entrypoint.sh: line 248: 20495 Aborted                 (core dumped) "$@"

Pretty sure I have the right kernel.

[root@tungsten-1 centos]# uname -a
Linux tungsten-1.local 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[root@tungsten-1 centos]# lsmod | grep vrouter
vrouter               460243  0

Any thoughts?

Another question -- What's the best way to get an all in one test environment?

Thanks,
Curtis.

[pc2929 att]

You're on the right track with contrail-ansible-deployer. That's still the recommended method for an individual install (although contrail-helm-deployer should also be a viable alternative) provided that you're running on CentOS, on bare metal and with a direct Internet connection. If you don't have all three of those, you might have trouble, but the fact that it was working for you before suggest that those aren't your problem.

I'd suggest opening a bug on Launchpad (under the opencontrail project since we haven't created a tungstenfabric project and are currently still in discussion of whether to continue using Launchpad or switch to Jira).

Can you see if you can locate the debug log (I'm not sure if debug logging has to be switched on somewhere, maybe someone else can answer that) and locate the error referenced in the code. Looking at where the assert failed, there should be a log message that contains the acctual mmap_error_msg:

from controller/src/vnsw/agent/vrouter/ksync/ksync_memory.cc

105     if (mmap_error_msg) {
106         LOG(DEBUG, "Error mapping KSync memory. Device: " << table_path_ << "; " << mmap_error_msg);
107         assert(0);
108     }

[server...@gmail.com]

On Wednesday, April 25, 2018 at 8:43:24 AM UTC-4, pc2929 att wrote:

You're on the right track with contrail-ansible-deployer. That's still the recommended method for an individual install (although contrail-helm-deployer should also be a viable alternative) provided that you're running on CentOS, on bare metal and with a direct Internet connection. If you don't have all three of those, you might have trouble, but the fact that it was working for you before suggest that those aren't your problem.

I'd suggest opening a bug on Launchpad (under the opencontrail project since we haven't created a tungstenfabric project and are currently still in discussion of whether to continue using Launchpad or switch to Jira).

OK, I entered a bug report into opencontrail on launchpad.

Will take a look for any debug logs as well.

Thanks for your help. :)