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 06:32:44 GMT

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

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

Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/1917
  
    @jayapalu thanks, yes it seems an intermittent issue with `ipmisim`, `pyghmi` library
that is used by the test to simulate a live ipmi server/board. I'll try to fix it soon, meanwhile
you can push -f or close/open the PR to re-kick Travis.
    Exception: Job failed: {jobprocstatus : 0, created : u'2017-02-09T13:17:54+0000', cmd
: u'org.apache.cloudstack.api.command.admin.outofbandmanagement.ChangeOutOfBandManagementPasswordCmd',
userid : u'9f69561f-eec8-11e6-8c34-42010a0a0806', jobstatus : 2, jobid : u'752cba20-e8f8-4b53-9675-8aa98186ee01',
jobresultcode : 530, jobresulttype : u'object', jobresult : {errorcode : 530, errortext :
u'Failed to change out-of-band management password for host (40328dc0-d290-481f-a6cc-f084ecf88661)
due to driver error: Failed to find IPMI user to change password, error: > Error: no response
from RAKP 1 message\n> Error: no response from RAKP 1 message\n> Error: no response
from RAKP 1 message\n> Error: no response from RAKP 1 message\nSet Session Privilege Level
to ADMINISTRATOR failed\nError: Unable to establish IPMI v2 / RMCP+ session\n'}, accountid
: u'9f693066-eec8-11e6-8c34-42010a0a0806'}


>  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