You are absolutely right and though it is kind of unsettling I will
now formally change my vote to
+1 (binding)

On Thu, Dec 12, 2013 at 6:01 AM, Abhinandan Prateek
<abhinandan.prat...@citrix.com> wrote:
> Well Daan, you said "well, mine is a go, I have a symptom not a decease.²
> and voted +1 on first voting round with this exception :-)
>
> On 11/12/13 10:27 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote:
>
>>H,
>>
>>I carried on with my sanity tests and all succeed only a disconcerning
>>exception trace appears that I have not seen  before. After creating a
>>network and instance and then deleting it:
>>
>>WARN  [agent.manager.AgentManagerImpl] (AgentManager-Handler-2:) Caught:
>>java.lang.NumberFormatException: For input string:
>>"12498842-6143-41d6-adfc-05b1f070e618"
>>at java.lang.NumberFormatException.forInputString(Unknown Source)
>>at java.lang.Long.parseLong(Unknown Source)
>>at java.lang.Long.parseLong(Unknown Source)
>>at
>>com.cloud.consoleproxy.AgentHookBase.onConsoleAccessAuthentication(AgentHo
>>okBase.java:135)
>>at
>>com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(ConsoleP
>>roxyListener.java:61)
>>at
>>com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManager
>>Impl.java:347)
>>at
>>com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.java:
>>144)
>>at
>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(Agent
>>ManagerImpl.java:1260)
>>at
>>com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerI
>>mpl.java:1348)
>>at
>>com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.do
>>Task(ClusteredAgentManagerImpl.java:666)
>>at com.cloud.utils.nio.Task.run(Task.java:83)
>>at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>at java.lang.Thread.run(Unknown Source)
>>
>>Is there anybody out there that can explain this one?
>>
>>On Wed, Dec 11, 2013 at 5:56 PM, Daan Hoogland <daan.hoogl...@gmail.com>
>>wrote:
>>> Wei,
>>>
>>> Thanks for the smack in the face. The problem was in my funky test
>>> setup with a local ms (on windows).
>>>
>>> Though I'm out of principle not very appreciative for the 'extra'
>>> fixes form RC to RC, this one would not have affected me had I been a
>>> good boy.
>>>
>>>
>>> On Wed, Dec 11, 2013 at 1:14 PM, Daan Hoogland
>>><daan.hoogl...@gmail.com> wrote:
>>>> I might agree as my env is running from source on windows but this is
>>>> an upgrade scenario and the page you refer is about installing! Is
>>>> that covered somewhere? Or does the copy take place automatically?
>>>>
>>>> regards,
>>>> Daan
>>>>
>>>> On Wed, Dec 11, 2013 at 12:00 PM, Wei ZHOU <ustcweiz...@gmail.com>
>>>>wrote:
>>>>> It looks you did not follow the instruction.
>>>>>
>>>>>http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/In
>>>>>stallation_Guide/management-server-install-flow.html
>>>>>
>>>>> I think it is not a blocker or critical issue.
>>>>>
>>>>>
>>>>> 2013/12/11 Daan Hoogland <daan.hoogl...@gmail.com>
>>>>>
>>>>>> I can confirm that the folowing fixes the problem
>>>>>>
>>>>>> [root@mccdxen1 bin]# pwd
>>>>>> /opt/cloud/bin
>>>>>> [root@mccdxen1 bin]# ln -s /opt/xensource/bin/vhd-util .
>>>>>>
>>>>>> I don't think we should let this to the people doing a migration from
>>>>>> one version to another so
>>>>>>
>>>>>> -1 (binding) to this rc
>>>>>>
>>>>>> I want to set this link in code (on addHost??) so again you will hear
>>>>>> more on this from me
>>>>>>
>>>>>> regards,
>>>>>> Daan
>>>>>>
>>>>>> On Wed, Dec 11, 2013 at 10:38 AM, Daan Hoogland
>>>>>><daan.hoogl...@gmail.com>
>>>>>> wrote:
>>>>>> > On Wed, Dec 11, 2013 at 5:24 AM, David Nalley <da...@gnsa.us>
>>>>>>wrote:
>>>>>> >> Why, for a bug fix release would we do something like change the
>>>>>> >> expected location of vhd-util on a XS host?
>>>>>> >
>>>>>> > Or more specifically; What bug does this fix?
>>>>>> >
>>>>>> > And why is it not copied to the hypervisors as part of the zone
>>>>>> > configuration/addHost procudure?
>>>>>>
>

Reply via email to