[
https://issues.apache.org/jira/browse/CLOUDSTACK-10167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag Sonstebo updated CLOUDSTACK-10167:
--------------------------------------
Description:
Environment:
* CloudStack 4.9.3 / CentOS7
* CloudStack 4.9.2 / CentOS7
* CloudStack 4.9.1 / CentOS7
* CloudStack 4.10.0 / CentOS7
* Tested and reproduced with:
** KVM / 4.9.1+4.9.2+4.9.3 / CentOS7
** XenServer 6.5 SP1
** VMware vSphere 6.5
* Issue observed on isolated and shared networks
* 4.6 "new" system VM templates:
http://packages.shapeblue.com/systemvmtemplate/4.6/new/
Steps to reproduce:
* Create isolated or shared network with running VM
* Confirm that everything works OK - DNS resolution and DHCP.
* Restart network with cleanup.
* On new VR check DNS and DHCP settings.
* Result:
** /etc/dnsmasq.d/cloud.conf: file is missing, hence no base DHCP config
** /etc/hosts: file present but missing all user VM entries, hence no DNS
resolution
** /etc/dhcphosts.txt: file is missing, hence no DHCP
** /etc/cloudstack/dhcpentry.json: file is present and contains expected JSON
VM entries
As a result the new VR:
* Will not hand out DHCP entries
* Will not do name resolution
Workaround:
* Creating new VM or stopping and starting a VM restores all settings.
was:
Environment:
* CloudStack 4.9.3 / CentOS7
* CloudStack 4.9.2 / CentOS7
* CloudStack 4.9.1 / CentOS7
* Tested and reproduced with:
** KVM / 4.9.1+4.9.2+4.9.3 / CentOS7
** XenServer 6.5 SP1
** VMware vSphere 6.5
* Issue observed on isolated and shared networks
* 4.6 "new" system VM templates:
http://packages.shapeblue.com/systemvmtemplate/4.6/new/
Steps to reproduce:
* Create isolated or shared network with running VM
* Confirm that everything works OK - DNS resolution and DHCP.
* Restart network with cleanup.
* On new VR check DNS and DHCP settings.
* Result:
** /etc/dnsmasq.d/cloud.conf: file is missing, hence no base DHCP config
** /etc/hosts: file present but missing all user VM entries, hence no DNS
resolution
** /etc/dhcphosts.txt: file is missing, hence no DHCP
** /etc/cloudstack/dhcpentry.json: file is present and contains expected JSON
VM entries
As a result the new VR:
* Will not hand out DHCP entries
* Will not do name resolution
Workaround:
* Creating new VM or stopping and starting a VM restores all settings.
> New VR after network restart with cleanup is missing DNS and DHCP entries
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10167
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10167
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.2.0, 4.9.1.0, 4.9.0.1, 4.9.3.0
> Environment: * CloudStack 4.9.3 / CentOS7
> * CloudStack 4.9.2 / CentOS7
> * CloudStack 4.9.1 / CentOS7
> * CloudStack 4.9.0.1 / CentOS7
> * KVM / 4.9.1 + 4.9.2 + 4.9.3 + 4.10.0 / CentOS7
> * XenServer 6.5 SP1
> * VMware vSphere 6.5
> * Issue observed on isolated and shared networks
> * 4.6 "new" system VM templates:
> http://packages.shapeblue.com/systemvmtemplate/4.6/new/
> Reporter: Dag Sonstebo
>
> Environment:
> * CloudStack 4.9.3 / CentOS7
> * CloudStack 4.9.2 / CentOS7
> * CloudStack 4.9.1 / CentOS7
> * CloudStack 4.10.0 / CentOS7
> * Tested and reproduced with:
> ** KVM / 4.9.1+4.9.2+4.9.3 / CentOS7
> ** XenServer 6.5 SP1
> ** VMware vSphere 6.5
> * Issue observed on isolated and shared networks
> * 4.6 "new" system VM templates:
> http://packages.shapeblue.com/systemvmtemplate/4.6/new/
> Steps to reproduce:
> * Create isolated or shared network with running VM
> * Confirm that everything works OK - DNS resolution and DHCP.
> * Restart network with cleanup.
> * On new VR check DNS and DHCP settings.
> * Result:
> ** /etc/dnsmasq.d/cloud.conf: file is missing, hence no base DHCP config
> ** /etc/hosts: file present but missing all user VM entries, hence no DNS
> resolution
> ** /etc/dhcphosts.txt: file is missing, hence no DHCP
> ** /etc/cloudstack/dhcpentry.json: file is present and contains expected JSON
> VM entries
> As a result the new VR:
> * Will not hand out DHCP entries
> * Will not do name resolution
> Workaround:
> * Creating new VM or stopping and starting a VM restores all settings.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
