Comment 0 for bug 1409882

this is with Contrail release 1.20/63

the Contrail vDNS only works for VMs in the "ACTIVE" state. VMs that are shut down cannot be resolved.

For example (10.163.43.4 and 10.163.43.12 are my controllers):

root@gngsvm009d:/opt/contrail/utils# nova list --all-tenant |grep tmtest
| 9cfc5612-69c7-4452-b34f-a34f456f815f | tmtest | ACTIVE | - | Running | svec-private=192.168.0.2 |
| f301ccaf-343f-4d31-84fd-c284fecb12c7 | tmtest1 | ACTIVE | - | Running | svec-private=192.168.0.11 |

root@gngsvm009d:/opt/contrail/utils# nslookup tmtest1.svec - 10.163.43.12
Server: 10.163.43.12
Address: 10.163.43.12#53

Name: tmtest1.svec.juniper.net
Address: 10.163.0.12

root@gngsvm009d:/opt/contrail/utils# nslookup tmtest1.svec - 10.163.43.4
Server: 10.163.43.4
Address: 10.163.43.4#53

Name: tmtest1.svec.juniper.net
Address: 10.163.0.12

root@gngsvm009d:/opt/contrail/utils# nova stop f301ccaf-343f-4d31-84fd-c284fecb12c7
root@gngsvm009d:/opt/contrail/utils# nova list --all-tenant |grep tmtest
| 9cfc5612-69c7-4452-b34f-a34f456f815f | tmtest | ACTIVE | - | Running | svec-private=192.168.0.2 |
| f301ccaf-343f-4d31-84fd-c284fecb12c7 | tmtest1 | SHUTOFF | - | Shutdown | svec-private=192.168.0.11 |

root@gngsvm009d:/opt/contrail/utils# nslookup tmtest1.svec - 10.163.43.12
Server: 10.163.43.12
Address: 10.163.43.12#53

** server can't find tmtest1.svec: NXDOMAIN

root@gngsvm009d:/opt/contrail/utils# nslookup tmtest1.svec - 10.163.43.4
Server: 10.163.43.4
Address: 10.163.43.4#53

** server can't find tmtest1.svec: NXDOMAIN

A DNS client should not be dependent on a VM run state.