Hi: At these days, i setup new environments and am building new starlingx image. When running build-pkgs, one source code repo called restapt-doc can't be normally build. At previous, I ever build successfully restapt-doc package. Compare previous version and current version, I found some new commits. I don't know whether these new commit cause building fails. I also check $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/root.log, everythings seem normal. But $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/build.log, it show some error, and I can't understand these error cause. The following shows log file and new commits. . Thanks Dehao ==================== $MY_WORKSPACE/std/results/dehao-starlingx-tis-r5-pike-std/restapi-doc-1.9.1-27.tis/root.log mvn clean generate-sources -o -Dmaven.repo.local=./mvn.repo/ [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Build Order: [INFO] [INFO] parent-pom [INFO] Titanium Cloud API Complete Reference [INFO] Titanium REST API Reference Guide [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building parent-pom 1.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ parent-pom --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] parent-pom ........................................ FAILURE [0.065s] [INFO] Titanium Cloud API Complete Reference ............. SKIPPED [INFO] Titanium REST API Reference Guide ................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.160s [INFO] Finished at: Fri Sep 07 06:37:11 UTC 2018 [INFO] Final Memory: 14M/964M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on project parent-pom: Execution default-clean of goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean failed: Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to collect dependencies for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1 (): Failed to read artifact descriptor for org.apache.maven:maven-plugin-api:jar:2.0.6: The repository system is offline but the artifact org.apache.maven:maven-parent:pom:5 is not available in the local repository. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException BUILDSTDERR: make: *** [build] Error 1 RPM build errors: BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.cFbbrh (%build) BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.cFbbrh (%build) Child return code was: 1 EXCEPTION: [Error()] Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/mockbuild/trace_decorator.py", line 96, in trace result = func(*args, **kw) File "/usr/lib/python2.7/site-packages/mockbuild/util.py", line 634, in do raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode) Error: Command failed: # bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/restapi-doc.spec ======================= commit 7b86cd14dfed473780befe2e5f7d2e4749751037 Author: Andreas Jaeger <aj@suse.com> Date: Wed Sep 5 20:33:52 2018 +0200 Add explicit noop gate job This repo defines jobs in check queue, so we can remove the noop-jobs template usage from project-config. To allow that, add a noop job to gate queue. Change-Id: Ie204c40291c17365887793bb5f114652fa24b360 commit 73c7dbc0aec99563d42fee2432e5ad5c33377157 Merge: 8e60299 a98bf51 Author: Zuul <zuul@review.openstack.org> Date: Wed Sep 5 15:38:58 2018 +0000 Merge "Remove OCF script code to monitor I/F status" commit a98bf512c4907e05c62188bdff8fbf6510f4656c Author: Bin Qian <bin.qian@windriver.com> Date: Tue Sep 4 13:44:27 2018 -0400 Remove OCF script code to monitor I/F status Remove OCF script code to monitor I/F status and fail the service when the I/F is down. On the other change, the monitor work is done by SM, to perform swact based on healthy state of both controllers. Depends: Ifa7453136f34768b99e2bcd741d1065e69ef452e Story: 2003577 Task: 24900 Change-Id: Ie3da54940054ef5c1880dae718272be1663026d8 Signed-off-by: Bin Qian <bin.qian@windriver.com>