Ciab 2.0 failures during deploy

[ESWAR RAO]

Hi All,

Can some one help me in resolving below error:

# ssh corddev 'cd /cord/build; ./gradlew -PdeployConfig=/cord/build//config/cord_in_a_box.yml deploy --stacktrace'

Tuesday 21 March 2017  11:19:27 +0000 (0:00:00.865)       0:19:47.432 ********* 

=============================================================================== 

maas : WARNING - We think MAAS install has hung. You may want to abort the install, re-image the head node, and start again. - 900.12s

maas : Wait for MAAS to Intialize (start) ------------------------------ 60.11s

maas : Wait for MAAS to Intialize (start) ------------------------------ 60.09s

maas : MAAS ------------------------------------------------------------ 31.87s

maas : Remove Automation Containers ------------------------------------- 9.68s

maas : Start Automation ------------------------------------------------- 8.92s

maas : Restart MAAS Services -------------------------------------------- 8.60s

maas : Restart MAAS Services -------------------------------------------- 8.37s

maas : Custom MAAS Configuration Template ------------------------------- 6.42s

compute-node : Ensure Utility Scripts ----------------------------------- 6.11s

setup ------------------------------------------------------------------- 4.00s

maas : Install Python Prerequisites ------------------------------------- 3.92s

maas : Stop Containers -------------------------------------------------- 3.71s

head-node : Copy CORD Utility Scripts ----------------------------------- 3.71s

maas : Kill Automation Containers --------------------------------------- 2.51s

compute-node : Ensure Docker Ansible Support ---------------------------- 2.49s

maas : Ensure Prerequisites --------------------------------------------- 2.19s

maas : Ensure PIP ------------------------------------------------------- 2.00s

head-node : Ensure Ansible Roles ---------------------------------------- 1.98s

maas : Verify MAAS Accepting API Requests ------------------------------- 1.67s

:onos-apps:deploy

PLAY [all] *********************************************************************

TASK [setup] *******************************************************************

ok: [10.100.198.201]

TASK [mavenrepo : Install compose for mavenrepo] *******************************

ok: [10.100.198.201] => (item=mavenrepo.yml)

TASK [mavenrepo : Ensure mavenrepo Running] ************************************

changed: [10.100.198.201] => (item=mavenrepo.yml)

PLAY RECAP *********************************************************************

10.100.198.201             : ok=3    changed=1    unreachable=0    failed=0   

:writeInventory

FAILURE: Build failed with an exception.

* What went wrong:

Timeout waiting to lock task history cache (/cord/build/.gradle/2.13/taskArtifacts). It is currently in use by another Gradle instance.

Owner PID: 3610

Our PID: 3990

Owner Operation: Load task history

Our operation: Load task history

Lock file: /cord/build/.gradle/2.13/taskArtifacts/cache.properties.lock

* Try:

Run with --info or --debug option to get more log output.

* Exception is:

org.gradle.cache.internal.LockTimeoutException: Timeout waiting to lock task history cache (/cord/build/.gradle/2.13/taskArtifacts). It is currently in use by another Gradle instance.

Owner PID: 3610

Our PID: 3990

Owner Operation: Load task history

Our operation: Load task history

Lock file: /cord/build/.gradle/2.13/taskArtifacts/cache.properties.lock

        at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.lock(DefaultFileLockManager.java:258)

        at org.gradle.cache.internal.DefaultFileLockManager$DefaultFileLock.<init>(DefaultFileLockManager.java:127)

        at org.gradle.cache.internal.DefaultFileLockManager.lock(DefaultFileLockManager.java:80)

        at org.gradle.cache.internal.DefaultCacheAccess.onStartWork(DefaultCacheAccess.java:349)

        at org.gradle.cache.internal.DefaultCacheAccess.useCache(DefaultCacheAccess.java:187)

I tried to remove lock files like:

vagrant@corddev:~$ find ~/.gradle -type f -name "*.lock" | while read f; do rm $f; done

I re-ran but still the problem persists.

Thanks

Eswar Rao

[Luca Prete]

Have you try to simply re-execute it again?

--
You received this message because you are subscribed to the Google Groups "CORD Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cord-discuss...@opencord.org.
To post to this group, send email to cord-d...@opencord.org.
Visit this group at https://groups.google.com/a/opencord.org/group/cord-discuss/.
To view this discussion on the web visit https://groups.google.com/a/opencord.org/d/msgid/cord-discuss/78f96471-4376-44f0-8f41-f247c85e0824%40opencord.org.
For more options, visit https://groups.google.com/a/opencord.org/d/optout.

[Jonathan Hart]

Looks like there is another process holding the lock - try to kill all gradle processes (in particular make sure these PIDs are dead) then run again.

 

To view this discussion on the web visit https://groups.google.com/a/opencord.org/d/msgid/cord-discuss/CAEL_9NNuhWAOfVxMDx3NQLvUJfC0yVCo0tnCfJFLX-1%3DT0JJVQ%40mail.gmail.com.

[ESWAR RAO]

Thanks for the help.

After I did below steps, the build proceeded further.

vagrant@corddev:/cord/build$ cd .gradle/2.13/taskArtifacts/

vagrant@corddev:/cord/build/.gradle/2.13/taskArtifacts$ rm -rf cache.properties.lock

vagrant@corddev:~$ find ~/.gradle -type f -name "*.lock" | while read f; do rm $f; done

vagrant@corddev:~$

vagrant@corddev:~$ find ~/.gradle -type f -name "*.lock"

vagrant@corddev:~$

vagrant@corddev:~$ ps -aef|grep gradle

vagrant  10169 10108  0 15:54 pts/1    00:00:00 grep --color=auto gradle

vagrant@corddev:~$

vagrant@corddev:~$ cd .gradle/caches/

vagrant@corddev:~/.gradle/caches$ ls

2.13  modules-2

vagrant@corddev:~/.gradle/caches$ ls -a

.  ..  2.13  modules-2

vagrant@corddev:~/.gradle/caches$ rm -rf *

Thanks

Eswar