[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yiping Zhang updated CLOUDSTACK-7974:
-------------------------------------
    Description: 
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.

  was:
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, noted 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 exists in /etc/dhcphosts.txt and 
/etc/hosts files


> deleted host entries still exists in /etc/hosts and /etc/dhcphosts.txt files 
> on virtual router
> ----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7974
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7974
>             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
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to