vdns: Zone files are not created

[Senthilnathan Murugappan]

Have provisioned via microservices model using contrail-ansible-deployer and observed that the zone and jnl files are not being generated under /etc/contrail/dns dir inside the container.

OS: Centos7.4
Used contrail RPM based on version: CB-181~mitaka
Cluster, if need be: 10.84.7.206

[Nipa (nipak)]

Can u pls dump contrail-named.conf and check if configs are populated and named logs furthur to see any error?

[Nipa (nipak)]

Hi Hari,

both containers can run in host pid mode. With that they will deal with the correct PID.
This will solve this particular problem but in general I am not a big friend of leveraging PIDs as a health check mechanism.
The right way would be to query bind9 on application layer.

Regards,
Michael

Am 13.03.2018 um 07:33 schrieb Hari Prasad Killi <email address hidden>:
Hi Michael, Andrey, Alex,
Contrail-named writes its pid to /etc/contrail/dns/contrail-named.pid, which is used by contrail-dns to identify that named is up / down or if it got restarted (when pid changes). With these two being in two different containers, the pid of each one is 1. As contrail-dns doesn’t see pid 1 being contrail-named (it reads /proc to find out the command for the pid and match it against contrail-named), it doesn’t consider named to be up and never pushes the DNS records to named. Is there a way to handle this ? Or should these two run in a single container ? Please note that named is third party, with minimal changes done to suit our needs.
Also, contrail-dns need not run as root (user contrail).
Regards,
Hari

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/40693
Submitter: Hari Prasad Killi (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/40693
Committed: http://github.com/Juniper/contrail-ansible-deployer/commit/bad3d638a0e9b826557beb7083429b76fa28a5d9
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit bad3d638a0e9b826557beb7083429b76fa28a5d9
Author: Hari Prasad Killi <email address hidden>
Date: Thu Mar 15 16:09:57 2018 +0530

Run contrail-named & contrail-dns containers in host pid mode

Named pid is used by contrail-dns to identify named start & restart, to
push the records to named. For this reason, changing contrail-named &
contrail-dns containers to run in host pid mode.

Change-Id: I82d5241071ed0b5cb37ecd6acdeea2ba82054ae4
closes-bug: #1747224

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/40743
Submitter: Andrey Pavlov (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/40743
Committed: http://github.com/Juniper/contrail-helm-deployer/commit/5d560bfff9173c2f34d34a0fce595b74b9e31f2e
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 5d560bfff9173c2f34d34a0fce595b74b9e31f2e
Author: Andrey Pavlov <email address hidden>
Date: Fri Mar 16 14:55:07 2018 +0300

add hostPID to contrail-control pod

contrail-dns and contrail-named must have one PID namespace.
It'll be better to use shareProcessNamespace from kubernetes 1.10
but now we have only 1.8 and will use host pid sharing.

Change-Id: Ibf0d714fe61dc55ded8cb2dbf5f1c43ac287730a
Partial-Bug: #1747224