I tested 4.2.1 with our custom vpc gateway on nvp patch basic usage in
a adnvanced zone with niciranvp or with vlans work That means creating
an standalone network or a vpc with a tier and in all cases with an
instance being able to ping the outside world. I encountered one
strange exception:
WARN [agent.manager.AgentManagerImpl] (AgentManager-Handler-6:) Caught:
java.lang.NumberFormatException: For input string:
"63424ecc-ee5c-49a0-b880-d1f879593822"
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(AgentHookBase.java:135)
at
com.cloud.consoleproxy.ConsoleProxyListener.processControlCommand(ConsoleProxyListener.java:61)
at
com.cloud.agent.manager.AgentManagerImpl.handleControlCommand(AgentManagerImpl.java:347)
at
com.cloud.agent.manager.AgentManagerImpl.access$200(AgentManagerImpl.java:144)
at
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.processRequest(AgentManagerImpl.java:1260)
at
com.cloud.agent.manager.AgentManagerImpl$AgentHandler.doTask(AgentManagerImpl.java:1348)
at
com.cloud.agent.manager.ClusteredAgentManagerImpl$ClusteredAgentHandler.doTask(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)
I will now test to rule out the patch for this though it is in
untouched code. I will enter a ticket or hold my peace forever after.
btw, this is a pre-vote thread for these kinds of reports is it?
regards,
Daan
On Wed, Nov 13, 2013 at 2:57 AM, Abhinandan Prateek
<abhinandan.prat...@citrix.com> wrote:
>
> On 13/11/13 4:11 am, "Chip Childers" <chipchild...@apache.org> wrote:
>
>>On Tue, Nov 12, 2013 at 10:31:47PM +0000, Animesh Chaturvedi wrote:
>>>
>>> The format of apache-cloudstack-4.2.1-src.tar.bz2.md5 doesn't match the
>>>gpg output.
>>>
>>> See this:
>>>
>>> localhost :: /tmp/cloudstack >gpg --print-md MD5
>>>apache-cloudstack-4.2.1-src.tar.bz2
>>> apache-cloudstack-4.2.1-src.tar.bz2: AE BF B5 B5 91 24 8B 6D 27 6F 9D
>>>35 C0 C3
>>> DD D5 localhost :: /tmp/cloudstack
>>>>cat apache-cloudstack-4.2.1-src.tar.bz2.md5
>>> apache-cloudstack-4.2.1-src.tar.bz2: AE BF B5
>>> B5 91 24
>>> 8B 6D 27
>>> 6F 9D 35
>>> C0 C3 DD
>>> D5
>>>
>>> There are extra line breaks in the .md5 file [1]. Although I'd
>>>actually prefer to get the process to switch to the md5sum tool's format
>>>anyway, can you correct this formatting before we continue with the
>>>release voting?
>>>
>>> -chip
>>>
>>> [1]
>>>https://dist.apache.org/repos/dist/dev/cloudstack/4.2.1/apache-cloudstack
>>>-4.2.1-src.tar.bz2.md5
>>>
>>> Animesh> Chip, Abhi is in a different time zone so will see this in
>>>morning, the SHA and MD5 are generated by build_asf.sh script so if
>>>this is an issue, should have been for prior releases also. Are you
>>>suggesting to update the build_asf.sh to file to fix the formatting?
>>>
>>>
>>
>>This must be an issue with local gpg output formatting. Weird.
>>
>>Let's go forward with the vote. Manual inspection shows it as matching.
>>For 4.3, we should change the build script to use native md5sum and
>>sha256sum (with a script fix to get around the mac installations that
>>may have the commands pre-pended with a "g").
>>
>>I'll finish my testing and move forward with voting shortly.
>>
> I followed the release procedure and then did validation on signature etc
> using the Release test procedure wiki.
> Let me know if there are any further issues will be around to rectify.
>
> -abhi
>>
>
