[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977212#comment-14977212
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8993:
--------------------------------------------

Github user serbaut commented on the pull request:

    https://github.com/apache/cloudstack/pull/981#issuecomment-151652563
  
    Getting errors when running test/systemvm/test_update_config.py.
    
            from envassert import file, process, package, user, group, port, 
cron, detect, ip
        ImportError: cannot import name ip
    
    Got other errors when setting up devcloud by following 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/devcloud-kvm but I 
managed to work around it.
    
        Exception Occurred Under createLogs :['Traceback (most recent call 
last):\n', '  File 
"/usr/local/lib/python2.7/site-packages/Marvin-4.6.0_SNAPSHOT-py2.7.egg/marvin/marvinLog.py",
 line 157, in createLogs\n    (\'LogFolderPath\' in log_cfg.__dict__.keys()) 
and\n', "Attri
        buteError: 'list' object has no attribute '__dict__'\n"]
    
    Not sure how to proceed. Are these tests supposed to work at all?


> DHCP fails with "no address available" when an IP is reused
> -----------------------------------------------------------
>
>                 Key: CLOUDSTACK-8993
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8993
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: SystemVM
>    Affects Versions: 4.6.0
>            Reporter: Joakim Sernbrant
>
> CsDhcp.process() appends new entries to /etc/dhcphosts.txt causing duplicates 
> like:
> {code}
> 06:49:14:00:00:4d,10.7.32.107,node1,infinite
> 06:42:b0:00:00:3a,10.7.32.107,node2,infinite
> {code}
> This makes dnsmasq fail with "no address available".
> CsDhcp.process() should repopulate the file to remove old entries with the 
> same IP address.



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

Reply via email to