[5.0.2 Vcenter]with eam enabled dns not getting resolved on contrail-vms
Bug #1791242 reported by
aswani kumar
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R5.0 |
Fix Released
|
Critical
|
amudhar | |||
| Trunk |
Fix Committed
|
Critical
|
amudhar | |||
Bug Description
Deployed cluster with eam enabled
Dns name is not getting resolved on contrail-vms
all contrail-vms are brought up with same dns-name "ContrailVM-23-27"
Because of this agents not able to register with controller and are down
| tags: | added: vmware |
Revision history for this message
| amudhar (amudha) wrote | #1 |
To post a comment you must log in.
Issue fixed and vmdk saved at /cs-shared/
centos-7.5-7
============
- added rename_interface, invoked on boot when ContrailVM is respawned
from Esx Agent Manager and vcenter playbook is re-run
- DNS name unresolved issue fixed (#1791242)
- when ContrailVM is respawned from EAM, it is powered on and
/etc/hostname is updated to default entry
- remove these entries in /firstboot, this updates the DNS resolved
name in /etc/hostname when the ContrailVM is powered back on at
the end of vcenter playbook
- remove entries from /etc/resolv.conf