Return-Path: 
 <issues-return-29930-apmail-cloudstack-issues-archive=cloudstack.apache.org@cloudstack.apache.org>
X-Original-To: apmail-cloudstack-issues-archive@www.apache.org
Delivered-To: apmail-cloudstack-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3163210C0A
	for <apmail-cloudstack-issues-archive@www.apache.org>;
 Mon, 21 Oct 2013 18:04:52 +0000 (UTC)
Received: (qmail 73672 invoked by uid 500); 21 Oct 2013 18:04:49 -0000
Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org
Received: (qmail 73580 invoked by uid 500); 21 Oct 2013 18:04:49 -0000
Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cloudstack.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cloudstack.apache.org>
List-Post: <mailto:issues@cloudstack.apache.org>
List-Id: <issues.cloudstack.apache.org>
Reply-To: dev@cloudstack.apache.org
Delivered-To: mailing list issues@cloudstack.apache.org
Received: (qmail 73398 invoked by uid 500); 21 Oct 2013 18:04:47 -0000
Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org
Received: (qmail 73278 invoked by uid 99); 21 Oct 2013 18:04:44 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Oct 2013 18:04:44 +0000
Date: Mon, 21 Oct 2013 18:04:44 +0000 (UTC)
From: "frank zhang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12669563.1379627549613.98688.1382378684703@arcas>
In-Reply-To: <JIRA.12669563.1379627549613@arcas>
References: <JIRA.12669563.1379627549613@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-4711) UCS:API: Premature API response
 prevent CS from syncing association status
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4711?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

frank zhang resolved CLOUDSTACK-4711.
-------------------------------------

    Resolution: Fixed

> UCS:API: Premature API response prevent CS from syncing association statu=
s
> -------------------------------------------------------------------------=
-
>
>                 Key: CLOUDSTACK-4711
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-471=
1
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          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=3D"none"=20
> However UCS sometimes send this response prematurely in which case CS fai=
ls 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 s=
aying the "Object already exists"=20
> We need to device another strategy for this to work flawlessly.
> 2013-09-19 14:35:08,554 WARN  [commons.httpclient.SimpleHttpConnectionMan=
ager] (Job-Executor-19:job-19 =3D [ 561e963d-be42-418b-be73-dcb7abf98e08 ])=
 SimpleHttpConnectionManager being used incorrectly.  Be sure that HttpMeth=
od.releaseConnection() is always called and that only one thread and/or met=
hod is using this connection manager at a time.
> 2013-09-19 14:35:08,563 DEBUG [ucs.manager.UcsManagerImpl] (Job-Executor-=
19:job-19 =3D [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) association respons=
e is  <configResolveDn dn=3D"sys/chassis-1/blade-1" cookie=3D"1379626356/ce=
72a30f-c52f-4772-a546-b26202477773" response=3D"yes"> <outConfig> <computeB=
lade adminPower=3D"policy" adminState=3D"in-service" assignedToDn=3D"" asso=
ciation=3D"none" availability=3D"available" availableMemory=3D"65536" chass=
isId=3D"1" checkPoint=3D"discovered"  connPath=3D"A" connStatus=3D"A" descr=
=3D"" discovery=3D"complete" dn=3D"sys/chassis-1/blade-1" fltAggr=3D"0" fsm=
Descr=3D"" fsmFlags=3D"" fsmPrev=3D"DisassociateSuccess" fsmProgr=3D"100" f=
smRmtInvErrCode=3D"none" fsmRmtInvErrDescr=3D"" fsmRmtInvRslt=3D"" fsmStage=
Descr=3D"" fsmStamp=3D"2013-09-19T14:35:06.906" fsmStatus=3D"nop" fsmTry=3D=
"0" intId=3D"36071" lc=3D"discovered" lcTs=3D"1969-12-31T16:00:00.000" lowV=
oltageMemory=3D"low-voltage" managingInst=3D"A" memorySpeed=3D"1333" mfgTim=
e=3D"2012-10-14T01:00:00.000" model=3D"UCSB-B200-M3" name=3D"" numOfAdaptor=
s=3D"1" numOfCores=3D"12" numOfCoresEnabled=3D"12" numOfCpus=3D"2" numOfEth=
HostIfs=3D"0" numOfFcHostIfs=3D"0" numOfThreads=3D"24" operPower=3D"off" op=
erQualifier=3D"" operState=3D"unassociated" operability=3D"operable" origin=
alUuid=3D"78eb1a7d-7665-4cdb-a995-e4953a63d1d7" partNumber=3D"73-13217-08" =
presence=3D"equipped" revision=3D"0"  serial=3D"FCH16407N8A" serverId=3D"1/=
1" slotId=3D"1"  totalMemory=3D"65536" usrLbl=3D"" uuid=3D"78eb1a7d-7665-4c=
db-a995-e4953a63d1d7" vendor=3D"Cisco Systems Inc" vid=3D"V03"/> </outConfi=
g> </configResolveDn>
> 2013-09-19 14:35:08,563 WARN  [cloudstack.api.AssociateUcsProfileToBladeC=
md] (Job-Executor-19:job-19 =3D [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) E=
xception:
> com.cloud.utils.exception.CloudRuntimeException: cannot associated a prof=
ile to blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for =
detailed error information
>         at com.cloud.ucs.manager.UcsManagerImpl.isBladeAssociated(UcsMana=
gerImpl.java:351)
>         at com.cloud.ucs.manager.UcsManagerImpl.associateProfileToBlade(U=
csManagerImpl.java:380)
>         at org.apache.cloudstack.api.AssociateUcsProfileToBladeCmd.execut=
e(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(ThreadPoolEx=
ecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE=
xecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-09-19 14:35:08,565 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Exec=
utor-19:job-19 =3D [ 561e963d-be42-418b-be73-dcb7abf98e08 ]) Complete async=
 job-19 =3D [ 561e963d-be42-418b-be73-dcb7abf98e08 ], jobStatus: 2, resultC=
ode: 530, result: Error Code: 530 Error text: cannot associated a profile t=
o blade[dn:sys/chassis-1/blade-1]. please check your UCS manasger for detai=
led error information
> 2013-09-19 14:35:09,006 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:nul=
l) =3D=3D=3DSTART=3D=3D=3D  10.252.113.141 -- GET  command=3DqueryAsyncJobR=
esult&jobId=3D561e963d-be42-418b-be73-dcb7abf98e08&response=3Djson&sessionk=
ey=3DGGZcS%2BPeH9m%2FNW3vwCTc8p5UiBA%3D&_=3D1379626509100



--
This message was sent by Atlassian JIRA
(v6.1#6144)