[
https://issues.apache.org/jira/browse/CLOUDSTACK-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13886512#comment-13886512
]
ASF subversion and git services commented on CLOUDSTACK-5916:
-
Commit 85d0f8f93aaf118e0597fcbba0f4cf06efa9df1f in branch refs/heads/master
from [~saksham]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=85d0f8f ]
CLOUDSTACK-5916: associateIpAddress leaves an IP in allocating state
associateIpAddress leaves an IP in allocating state
Key: CLOUDSTACK-5916
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5916
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Network Controller
Affects Versions: 4.4.0
Environment: 4.3, Xenserver
Reporter: Saksham Srivastava
Assignee: Saksham Srivastava
associateIpAddress leaves an IP in allocating state (user_ip_address table),
although the API command is executed on incorrectly.
Steps to repro :
1) create a vpc tier.
2) Execute associateIpAddress API on the vpc tier but do not specify the
vpc id.
#cloudmonkey
associate ipaddress networkid=09ffc45f-beba-4690-8be7-425891915d44
Async job ea020246-d0e8-4e58-ac84-fccb55c3b646 failed
Error 530, Can't assign ip to the network directly when network belongs to
VPC.Specify vpcId to associate ip address to VPC
accountid = a6ba35b3-7e76-11e3-8490-7614eba325e6
cmd = org.apache.cloudstack.api.command.user.address.AssociateIPAddrCmd
created = 2014-01-21T10:46:46+0530
jobid = ea020246-d0e8-4e58-ac84-fccb55c3b646
jobprocstatus = 0
jobresult:
errorcode = 530
errortext = Can't assign ip to the network directly when network belongs to
VPC.Specify vpcId to associate ip address to VPC
jobresultcode = 530
jobresulttype = object
jobstatus = 2
userid = a6ba5844-7e76-11e3-8490-7614eba325e6
Expected behavior:
There should be no allocation of IP .
Actual behaviour:
The public IP remains in 'Allocating' state
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
