Sent from my iPhone
On Oct 8, 2012, at 11:37 AM, "sebgoa" wrote:
>
> On Oct 8, 2012, at 8:08 PM, Chip Childers wrote:
>
>> Was the resolution covered via the "Clean up environment" step in the
>> test procedure? (command steps below)
>>
>> rm -rf ~/.m2
>> ssh root@localhost -p 'cd /opt
On Oct 8, 2012, at 8:08 PM, Chip Childers wrote:
> Was the resolution covered via the "Clean up environment" step in the
> test procedure? (command steps below)
>
> rm -rf ~/.m2
> ssh root@localhost -p 'cd /opt/cloudstack/; rm -rf
> apache-tomcat-6.0.32; unzip apache-tomcat-6.0.32.zip; cd
>
Was the resolution covered via the "Clean up environment" step in the
test procedure? (command steps below)
rm -rf ~/.m2
ssh root@localhost -p 'cd /opt/cloudstack/; rm -rf
apache-tomcat-6.0.32; unzip apache-tomcat-6.0.32.zip; cd
incubator-cloudstack; git clean -f; git reset --hard; git pull
-
I cleaned up the tomcat dir on devcloud, re built and re-deployed and it worked.
-sebastien
On Oct 8, 2012, at 7:16 PM, Rohit Yadav wrote:
> I not sure if awsapi runs in developer mode and with the script you're using
> (cloudstack-aws-api-register). The script is assumed to be part of a releas
I not sure if awsapi runs in developer mode and with the script you're using
(cloudstack-aws-api-register). The script is assumed to be part of a release
where the awsapi package is installed in /usr/share/cloud/bridge.
Try to change the hardcoded path to the path where bridge is getting deployed
Definitely retest with the new build. That's the problem we've been tracking
down the whole weekend.
--Alex
> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Monday, October 08, 2012 9:37 AM
> To: cloudstack
> Subject: aws testing using 4.0 test procedure
>
> Hi,
>
