cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-7974) deleted VM entries still exists in /etc/hosts and /etc/dhcphosts.txt files on virtual router
Date Wed, 10 Dec 2014 12:57:14 GMT


Rohit Yadav commented on CLOUDSTACK-7974:

I've opened a new issue that aims to
add an improvement to delete entries when VM is destroyed.

> deleted VM entries still exists in /etc/hosts and /etc/dhcphosts.txt files on virtual
> --------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-7974
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.3.0
>            Reporter: Yiping Zhang
>            Assignee: Rohit Yadav
>             Fix For: 4.5.0, 4.6.0, 4.4.2, 4.4.3, 4.3.2
> We have noticed that entries for hosts which have been destroyed for a long time still
exist in both /etc/dhcphosts.txt and /etc/hosts files on our Virtual Routers.
> To reproduce this bug,  just create an instance, note down its MAC and IP address, then
destroy the instance from web UI.  Now check virtual router, and you will find that the entries
still exist in /etc/dhcphosts.txt and /etc/hosts files.
> I did a bit more digging on virtual router, and immediately noticed the following:
> 1. /root/ script is only called when an instance is created, but not when
an instance is destroyed.
> 2. After reading /root/ script, I am pretty certain that the function of
this script is to add info about newly created instances into /etc/hosts and /etc/dhcphosts.txt
files.  So the script should really be renamed as /root/ to reflect its true function.
> 3.  there is no script to properly delete entries from /etc/hosts and /etc/dhcphosts.txt
file when instances are destroyed

This message was sent by Atlassian JIRA

View raw message