[jira] [Updated] (CLOUDSTACK-4711) UCS:API: Premature API response prevent CS from syncing association status

2013-10-09 Thread Abhinandan Prateek (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhinandan Prateek updated CLOUDSTACK-4711:
---

Assignee: frank zhang

> UCS:API: Premature API response prevent CS from syncing association status
> --
>
> Key: CLOUDSTACK-4711
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Assignee: frank zhang
>Priority: Critical
> Fix For: 4.2.1
>
>
> We rely on association tag from UCS manager to determine the association 
> success.
> association="none" 
> However UCS sometimes send this response prematurely in which case CS fails 
> the API and association is unsuccessful.
> Eventually UCS finishes association and CS and UCS are now out of sync.
> Now if admin attempts to re-associate this blade then it will error out 
> saying the "Object already exists" 
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  
> [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
> 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
> used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
> called and that only one thread and/or method is using this connection 
> manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
> association response is   cookie="1379626356/ce72a30f-c52f-4772-a546-b2620243" response="yes"> 
>   assignedToDn="" association="none" availability="available" 
> availableMemory="65536" chassisId="1" checkPoint="discovered"  connPath="A" 
> connStatus="A" descr="" discovery="complete" dn="sys/chassis-1/blade-1" 
> fltAggr="0" fsmDescr="" fsmFlags="" fsmPrev="DisassociateSuccess" 
> fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" 
> fsmStageDescr="" fsmStamp="2013-09-19T14:35:06.906" fsmStatus="nop" 
> fsmTry="0" intId="36071" lc="discovered" lcTs="1969-12-31T16:00:00.000" 
> lowVoltageMemory="low-voltage" managingInst="A" memorySpeed="1333" 
> mfgTime="2012-10-14T01:00:00.000" model="UCSB-B200-M3" name="" 
> numOfAdaptors="1" numOfCores="12" numOfCoresEnabled="12" numOfCpus="2" 
> numOfEthHostIfs="0" numOfFcHostIfs="0" numOfThreads="24" operPower="off" 
> operQualifier="" operState="unassociated" operability="operable" 
> originalUuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber="73-13217-08" 
> presence="equipped" revision="0"  serial="FCH16407N8A" serverId="1/1" 
> slotId="1"  totalMemory="65536" usrLbl="" 
> uuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" vendor="Cisco Systems Inc" 
> vid="V03"/>  
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
> to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
> detailed error information
> at 
> com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
> at 
> org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
> async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
> profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
> for detailed error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  10.252.113.141 -- GET  
> command=queryAsyncJobResult&jobId=561e

[jira] [Updated] (CLOUDSTACK-4711) UCS:API: Premature API response prevent CS from syncing association status

2013-10-07 Thread Parth Jagirdar (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Parth Jagirdar updated CLOUDSTACK-4711:
---

Summary: UCS:API: Premature API response prevent CS from syncing 
association status  (was: UCS:API: Premature API response prevernt CS from 
syncing association status)

> UCS:API: Premature API response prevent CS from syncing association status
> --
>
> Key: CLOUDSTACK-4711
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4711
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API, UCS
>Affects Versions: 4.2.0
> Environment: UCS
>Reporter: Parth Jagirdar
>Priority: Critical
> Fix For: 4.2.1
>
>
> We rely on association tag from UCS manager to determine the association 
> success.
> association="none" 
> However UCS sometimes send this response prematurely in which case CS fails 
> the API and association is unsuccessful.
> Eventually UCS finishes association and CS and UCS are now out of sync.
> Now if admin attempts to re-associate this blade then it will error out 
> saying the "Object already exists" 
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  
> [commons.httpclient.SimpleHttpConnectionManager] (Job-Executor-19:job-19 = [ 
> 561e963d-be42-418b-be73-dcb7abf98e08 ]) SimpleHttpConnectionManager being 
> used incorrectly.  Be sure that HttpMethod.releaseConnection() is always 
> called and that only one thread and/or method is using this connection 
> manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) 
> association response is   cookie="1379626356/ce72a30f-c52f-4772-a546-b2620243" response="yes"> 
>   assignedToDn="" association="none" availability="available" 
> availableMemory="65536" chassisId="1" checkPoint="discovered"  connPath="A" 
> connStatus="A" descr="" discovery="complete" dn="sys/chassis-1/blade-1" 
> fltAggr="0" fsmDescr="" fsmFlags="" fsmPrev="DisassociateSuccess" 
> fsmProgr="100" fsmRmtInvErrCode="none" fsmRmtInvErrDescr="" fsmRmtInvRslt="" 
> fsmStageDescr="" fsmStamp="2013-09-19T14:35:06.906" fsmStatus="nop" 
> fsmTry="0" intId="36071" lc="discovered" lcTs="1969-12-31T16:00:00.000" 
> lowVoltageMemory="low-voltage" managingInst="A" memorySpeed="1333" 
> mfgTime="2012-10-14T01:00:00.000" model="UCSB-B200-M3" name="" 
> numOfAdaptors="1" numOfCores="12" numOfCoresEnabled="12" numOfCpus="2" 
> numOfEthHostIfs="0" numOfFcHostIfs="0" numOfThreads="24" operPower="off" 
> operQualifier="" operState="unassociated" operability="operable" 
> originalUuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber="73-13217-08" 
> presence="equipped" revision="0"  serial="FCH16407N8A" serverId="1/1" 
> slotId="1"  totalMemory="65536" usrLbl="" 
> uuid="78eb1a7d-7665-4cdb-a995-e4953a63d1d7" vendor="Cisco Systems Inc" 
> vid="V03"/>  
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeCmd] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Exception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a profile 
> to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for 
> detailed error information
> at 
> com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsManagerImpl.java:351)
> at 
> com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(UcsManagerImpl.java:380)
> at 
> org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execute(AssociateUcsProfileToBladeCmd.java:58)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
> at 
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
> at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] 
> (Job-Executor-19:job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete 
> async job-19 = [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, 
> resultCode: 530, result: Error Code: 530 Error text: cannot associated a 
> profile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger 
> for detailed error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet