[
https://issues.apache.org/jira/browse/CLOUDSTACK-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinav Roy reopened CLOUDSTACK-95:
-----------------------------------
> IP address allocation not working when a user tries to allocate IP addresses
> in a Project.
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-95
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-95
> Project: CloudStack
> Issue Type: Bug
> Components: Projects
> Affects Versions: pre-4.0.0
> Environment: OS : Rhel6.3
> BUILD : [Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git]
> Reporter: Abhinav Roy
> Assignee: Brian Federle
> Fix For: pre-4.0.0
>
> Attachments: After IP Allocation Domain-Admin Dashboard.jpg, After IP
> Allocation Domain-Admin Network.jpg, After IP Allocation ROOT-Admin
> Dashboard.jpg, Before-IP-Allocation Domain-Admin Dashboard.jpg,
> Before-IP-Allocation ROOT-Admin Dashboard.jpg
>
>
> Steps :
> =========================================
> 1. Deploy Advanced zone CloudStack setup.
> 2. Create a Domain 'user-domain' inside ROOT domain.
> 3. Create 3 accounts inside user-domain. user1 as domain-admin and user2 &
> user3 as regular users.
> 4. login to user3 and create a project.
> 5. Add user4 and user5 to the project.
> 6. Switch to project-view
> 7. Create a network and few VM instances.
> 8. Goto Network -> IP Addresses and try to acquire an IP address.
> Expected Behaviour :
> =========================================
> 1. The IP addresses should be acquired successfully and the acquired IP
> should be seen in the UI at Network -> IP Address
> 2. There should be an increase in the IP address count in the project
> dashboard as well as in the dashboard when you login as ROOT admin.
> Observed Behaviour :
> =========================================
> 1. The IP address doesn't get acquire and there is an error shown in the UI
> as well as the management server logs
> 2012-09-13 23:40:17,039 DEBUG [cloud.user.AccountManagerImpl]
> (catalina-exec-23:null) Access to Acct[17-PrjAcct-user5-project-2] granted to
> Acct[5-user3] by DomainChecker2012-09-13 23:40:17,040 DEBUG
> [cloud.network.NetworkManagerImpl] (catalina-exec-23:null) Associate IP
> address called by the user 5 account 17
> 2012-09-13 23:40:17,042 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-23:null) Associate IP address lock acquired2012-09-13
> 23:40:17,048 DEBUG [cloud.network.NetworkManagerImpl] (catalina-exec-23:null)
> Got 10.102.125.69 to assign for account 17 in zone 1
> 2012-09-13 23:40:17,052 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-23:null) Releasing lock account
> Acct[17-PrjAcct-user5-project-2]
> 2012-09-13 23:40:17,052 DEBUG [cloud.network.NetworkManagerImpl]
> (catalina-exec-23:null) Associate IP address lock released
> 2012-09-13 23:40:17,074 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-23:null) submit async job-116, details: AsyncJobVO {id:116,
> userId: 5, accountId: 5, sessionKey: null, instanceType: IpAddress,
> instanceId: 5, cmd: com.cloud.api.commands.AssociateIPAddrCmd, cmdOriginator:
> null, cmdInfo:
> {"id":"5","response":"json","sessionkey":"YEiFPlSInA8mdZRoF3X3HrwFMOA\u003d","ctxUserId":"5","_":"1347559874247","projectid":"91d915f6-ec6a-49ba-9a6e-205eae66e447","ctxAccountId":"5","networkid":"b13be5fd-9499-4ba4-a68c-cd955ff016af","ctxStartEventId":"504"},
> cmdVersion: 0, callbackType: 0, callbackAddress: null, status: 0,
> processStatus: 0, resultCode: 0, result: null, initMsid: 129936880108802,
> completeMsid: null, lastUpdated: null, lastPolled: null, created:
> null}2012-09-13 23:40:17,077 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-23:job-116) Executing com.cloud.api.commands.AssociateIPAddrCmd
> for job-116
> 2012-09-13 23:40:17,082 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-23:job-116) Sync job-116 execution on object
> network.2152012-09-13 23:40:17,093 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-23:job-116) job com.cloud.api.commands.AssociateIPAddrCmd for
> job-116 was queued, processing the queue.2012-09-13 23:40:17,099 DEBUG
> [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-116) Executing sync
> queue item: SyncQueueItemVO {id:15, queueId: 15, contentType: AsyncJob,
> contentId: 116, lastProcessMsid: 129936880108802, lastprocessNumber: 1,
> created: Thu Sep 13 23:40:17 IST 2012}2012-09-13 23:40:17,100 DEBUG
> [cloud.async.AsyncJobManagerImpl] (Job-Executor-23:job-116) Schedule queued
> job-116
> 2012-09-13 23:40:17,104 DEBUG [cloud.async.SyncQueueManagerImpl]
> (Job-Executor-23:job-116) There is a pending process in sync queue(id: 15)
> 2012-09-13 23:40:17,105 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-24:job-116) Executing com.cloud.api.commands.AssociateIPAddrCmd
> for job-116
> 2012-09-13 23:40:17,128 DEBUG [cloud.user.AccountManagerImpl]
> (Job-Executor-24:job-116) Access to Ip[10.102.125.69-1] granted to
> Acct[5-user3] by DomainChecker
> 2012-09-13 23:40:17,140 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-24:job-116) Complete async job-116, jobStatus: 2, resultCode:
> 530, result: Error Code: 531 Error text: Unable to use network with id= 215,
> permission denied
> 2012-09-13 23:40:17,150 DEBUG [cloud.async.SyncQueueManagerImpl]
> (Job-Executor-24:job-116) Sync queue (15) is currently empty
> 2012-09-13 23:40:21,041 DEBUG [storage.secondary.SecondaryStorageManagerImpl]
> (secstorage-1:null) Zone 1 is ready to launch secondary storage VM
> NOTE
> ==========================================
> 1. Here we see that the IP address is allocated but is not acquired with the
> Network . This can be seen in the UI also where we see an increase in no. of
> allocated IP addresses at the dashboard since the IP has been acquired.
> This is not the expected behaviour. The IP address should have been
> acquired as well as associated with the network.
> 2. When we create a project as ROOT admin and then login as ROOT admin and
> acquire the IP , then the acqisition as well as association is successful and
> we don't see any error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
