You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/02/09 00:49:12 UTC
[jira] [Closed] (CLOUDSTACK-1141) Ipv6 - After network restart (and
reboot router) , we do not see the existing vms dnsentries not being
programmed in the router.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangeetha Hariharan closed CLOUDSTACK-1141.
-------------------------------------------
Closing this issue as the original issue mentioned in the bug is fixed and verified.
Will log a different bug to track the issue where the router Ip address gets changed after network restart.
> Ipv6 - After network restart (and reboot router) , we do not see the existing vms dnsentries not being programmed in the router.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1141
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1141
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Latest build from networkrefactor branch.
> Reporter: Sangeetha Hariharan
> Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - After network restart , we do not see the existing vms dnsentries not being programmed in the router.
> Steps to reproduce the problem:
> Create a Ipv6 network.
> Deploy vms in this network.
> Restart network with clean option.
> After network is restarted successfully , the router does not have any existing vm's dnsentries being programmed in the router.
> /etc/dhcphosts.txt is empty.
> We are not able to reach Vms with in the network using their names.
> rebbot router also does not bring back these entries to the router.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira