Yeah, I see there was a commit a3cec3802c4c56173c33ccc1e08af059547fe90e
that broke it again. I'll reverted that commit and ran the following to
sanity test and its seems to be working now
mvn -T 1.5C -DskipTests clean install
chmod +x
plugins/network-elements/juniper-contrail/test/resources/mysql_db_start.sh
plugins/network-elements/juniper-contrail/test/resources/mysql_db_start.sh
5000
sed s/3306/5000/g utils/conf/db.properties >
utils/conf/db.properties.override
mvn -P developer -pl developer -Ddeploydb
Make sure you run "mvn clean install" once after you update.
Darren
On Fri, Nov 1, 2013 at 6:34 PM, Pedro Roque Marques <
pedro.r.marq...@gmail.com> wrote:
> Darren,
>
> On Oct 31, 2013, at 9:27 AM, Darren Shepherd <darren.s.sheph...@gmail.com>
> wrote:
>
> > This is fixed now.
>
> Maybe i'm doing something really dumb... but i still see the problem.
> I do see the commit afaf637 in the branch history.
>
> Steps to reproduce:
> 1.
> plugins/network-elements/juniper-contrail/test/resources/mysql_db_start.sh
> 50000
> 2 copy utils/conf/db.properties to db.properties.override
> 3 modify
>
> # CloudStack database settings
> db.cloud.username=${USER}
> db.cloud.password=
> db.root.password=
> db.cloud.host=localhost
> db.cloud.port=50000
> db.cloud.name=cloud
>
> 4. mvn -P developer -pl developer -Ddeploydb
> ========> Initializing database=cloud with host=localhost port=3306
> username=cloud password=cloud
>
> It should display port=50000 and username=${USER)
>
>
> I'll dig into this further... most likely it is being caused by something
> really stupid i'm doing. But anyway i thought i would suggest a way to
> start a local mysql as a way to test. The contrail plugin test harness is
> allocating a random port and then trying to create a DB that is used for
> the test.
>
> Pedro.
