cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9756) IP address must not be allocated to other VR if releasing ip address is failed
Date Mon, 20 Feb 2017 05:35:44 GMT

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

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

Github user jayapalu commented on the issue:

    https://github.com/apache/cloudstack/pull/1917
  
    Travis CI test_outofbandmanagement  is failing which is not related to this PR changes.
 It seems there is problem with the test case.
    @rhtyd  Do you have any idea on this ?
    Running tests:  smoke/test_outofbandmanagement smoke/test_over_provisioning smoke/test_password_server
smoke/test_portable_publicip smoke/test_primary_storage smoke/test_privategw_acl smoke/test_public_ip_range
smoke/test_pvlan smoke/test_regions smoke/test_reset_vm_on_reboot smoke/test_resource_detail
smoke/test_router_dhcphosts smoke/test_router_dns smoke/test_routers smoke/test_routers_iptables_default_policy
smoke/test_routers_network_ops smoke/test_scale_vm smoke/test_secondary_storage smoke/test_service_offerings
smoke/test_snapshots smoke/test_ssvm smoke/test_staticroles smoke/test_templates smoke/test_usage_events
smoke/test_vm_life_cycle smoke/test_vm_snapshots smoke/test_volumes smoke/test_vpc_redundant
smoke/test_vpc_router_nics smoke/test_vpc_vpn smoke/misc/test_deploy_vm smoke/misc/test_escalations_templates
smoke/misc/test_vm_ha smoke/misc/test_vm_sync
    
    Traceback (most recent call last):
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 596, in process_request_thread
    
        self.finish_request(request, client_address)
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 331, in finish_request
    
        self.RequestHandlerClass(request, client_address, self)
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 652, in __init__
    
        self.handle()
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 436,
in handle
    
        return IpmiServerContext().handle(data, address, socket)
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 112,
in handle
    
        self.initiate_session(data, address, self.session)
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 143,
in initiate_session
    
        myaddr, netfnlun = struct.unpack('2B', data[14:16])
    
    error: unpack requires a string argument of length 2
    
    Traceback (most recent call last):
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 596, in process_request_thread
    
        self.finish_request(request, client_address)
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 331, in finish_request
    
        self.RequestHandlerClass(request, client_address, self)
    
      File "/opt/python/2.7.12/lib/python2.7/SocketServer.py", line 652, in __init__
    
        self.handle()
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 436,
in handle
    
        return IpmiServerContext().handle(data, address, socket)
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 112,
in handle
    
        self.initiate_session(data, address, self.session)
    
      File "/home/travis/.local/lib/python2.7/site-packages/ipmisim/ipmisim.py", line 143,
in initiate_session
    
        myaddr, netfnlun = struct.unpack('2B', data[14:16])
    
    error: unpack requires a string argument of length 2


>  IP address must not be allocated to other VR if releasing ip address is failed
> -------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9756
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9756
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>            Reporter: Jayapal Reddy
>            Assignee: Jayapal Reddy
>             Fix For: 4.10.0.0
>
>
> Apply rule (delete) is success on failure of ip assoc on back end. Cloudstack ignored
the ip assoc failure.
> Due to this the ip got freed and assigned to another network/account. It caused the ip
to be present in more than one router.
> Fix: Failing the apply rule (delete) on ipassoc failure
> Repro steps:
> 1. Configure PF/static nat/Firewall rules
> 2. Delete the rule configured.
> On deleting the rule, fail the ip assoc on the router.
> 3. Delete rule fails because ip assoc got failed.
> For RVR:
> 1. acquire several public ips,
> 2. add some rules on those public ips, so ips should show up in RVR,
> 3. change ipassoc.sh in RVR, make it always returns error on disassociate ip.
> 4. disassociate ip from  UI, ip should  is freed even though disassociate fails inside
VR.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message