I am trying to run following shell script from jenkins pipeline but its giving error.
/bin/openstack image create Abhay_Centos_6_8_img_V7 --disk-format vhd --min-disk 40 --min-ram 1024 --volume "71c8532d-4fc0-42d4-a534-7b368e4804cb" --unprotected --property __os_type=Linux --property __platform=Linux --property __os_version="CentOS linux 6.8" --force
Error:
/bin/openstack image create Abhay_Centos_6_8_img_V7 --disk-format vhd --min-disk 40 --min-ram 1024 --volume 71c8532d-4fc0-42d4-a534-7b368e4804cb --unprotected --property __os_type=Linux --property __platform=Linux --property '__os_version=CentOS linux 6.8' --force
Uploading data and using container are not allowed at the same time
Build step 'Conditional step (single)' marked build as failure
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
Finished: FAILURE
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
But same script is running fine if I run shell script manually on server.
Very late answer but I just met the problem and solved it, so let's share a solution :
after inspecting Openstack code, it appears that 'openstack image create' checks tty status : it needs a tty (even if you create from a volume), that cron or jenkins may not provide. So you need to "fake" a tty to execute the command :
example in bash :
faketty() {
script -qefc "$(printf "%q " "$#")"
}
faketty openstack image create --volume ${VOLUME_NAME} ${IMAGE_NAME}
Enjoy
Related
While running the dataflow template in python using the following command
gcloud dataflow flex-template run "streaming-beam-`date +%Y%m%d-%H%M%S`" \
--template-file-gcs-location "$TEMPLATE_PATH" \
--region "$REGION"
The job gets triggered on the console but the DAG is not formed and the following error is reported after a couple of minutes
/usr/bin/docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused "exec: \"/opt/google/dataflow/python_template_launcher\": stat /opt/google/dataflow/python_template_launcher: no such file or directory": unknown.
Can someone figure out what the problem could be?
I have already checked the following
The template file is present in the location
The registry has the image
Not sure what the error means?
I'm using Gitlab self server community version ci/cd function, It has been running well, But suddenly one day,All the projects in the gitlab/cicd has failed, it mentions below errors:
Uploading artifacts for successful job
Uploading artifacts...
promotion-api/my-boot-module-system/target/*.jar: found 1 matching files and directories
WARNING: Uploading artifacts as "archive" to coordinator... failed id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
WARNING: Retrying... context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
WARNING: Retrying... context=artifacts-uploader error=invalid argument
WARNING: Uploading artifacts as "archive" to coordinator... failed id=1515 responseStatus=500 Internal Server Error status=500 token=xrDFnLeB
FATAL: invalid argument
ERROR: Job failed: exit code 1
Below is the code in .gitlab-ci.yml
deploy-java:
stage: deploy
dependencies:
- build-java
image:
name: docker/compose:latest
before_script:
- docker info
- docker-compose -v
script:
- cd promotion-api
- docker-compose build
- docker images
- docker ps -a
- docker-compose up -d
tags:
- promotion
2021-3-29:
I switched the runner from linux version to docker, seems all fine till now
You ran into a bug in GitLab itself. Instead of a rather obscure HTTP status 500 it should say what the issue is explicitly. It is likely not a problem in your repository or CI settings.
Follow these issues to find out more:
Artifact is stopped in the transfer, possibly because it takes longer than some timeout to upload: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/26869
Artifact is larger than 1 GB: https://gitlab.com/gitlab-org/gitlab/-/issues/267111
For me the problem was that gitlab had run out of disk-space.
After having deleted unnecessary artifacts and files everything was working correctly again.
You can check your system status (if you host your own gitlab) here: www.gitlab-url.com/admin/system_info
(Go to: Admin Area > Monitoring > System Info)
Hope it helps!
i try run my application on real hardware
but android studio return follow error
07:25 PM 'cmd package install-create -r -t -S 1676395' returns error 'Unknown failure: Exception occurred while executing:
android.os.ParcelableException: java.io.IOException: Requested internal only, but not enough space
at android.util.ExceptionUtils.wrap(ExceptionUtils.java:34)
at com.android.server.pm.PackageInstallerService.createSession(PackageInstallerService.java:596)
at com.android.server.pm.PackageManagerShellCommand.doCreateSession(PackageManagerShellCommand.java:1362)
at com.android.server.pm.PackageManagerShellCommand.runInstallCreate(PackageManagerShellCommand.java:282)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:118)
at android.os.ShellCommand.exec(ShellCommand.java:96)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:23614)
at android.os.Binder.shellCommand(Binder.java:574)
at android.os.Binder.onTransact(Binder.java:474)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager... (show balloon)
07:26 PM Session 'app': Error Installing APKs
Happens because of many things
First, Try Build -> Clean project then Build -> Rebuild project
Get some free storage in your phone
Disable instant-run
make sure that usb-debugging is enabled
See This, it may help.
I have a BitBake build process that runs on a Docker container (CentOS 7). The BitBake fails during recipe gcc-cross-i586-5.2.0-r0: task do_compile on each run that I try it in.
An example of bitbake's output:
NOTE: recipe gcc-cross-i586-5.2.0-r0: task do_compile: Started
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
ERROR: Worker process (367) exited unexpectedly (-9), shutting down...
NOTE: Tasks Summary: Attempted 1538 tasks of which 17 didn't need to be rerun and all succeeded.
Is this a problem with recipe gcc-cross-i586-5.2.0-r0: task do_compile? Perhaps an out-of-memory error? I don't know what the -9 refers to or how to find out more information about it.
Try:
$ bitbake -c cleansstate gcc-cross ; bitbake -k gcc-cross
How much you have memory of ram?
Report log error here.
This worked for me,
Edit conf/local.conf and decrease the number of working threads by adding the following to you conf/local.conf file (under the build directory):
BB_NUMBER_THREADS = "6"
Just a long shot, -9 in kernel land means EBADF (bad file number.) Is it possible you have done some operations as root and some files are not accessible during the build? Is the issue reproducible? ie. can you rm -rf tmp and does it happen again? Make sure you don't have any permissions issues in your project directory and associated file system(s).
In Linux server I have installed Jenkins and created new Job & Using Shell Command to execute the job. The shell command which I am using is bash run.bat. Where run.bat file contains following code java -cp ./lib/*:./bin org.testng.TestNG testng.xml. Whenever I am trying to build this project from Jenkins it gives following error message in console
[EmailableReporter] [ERROR] Unable to create output file
java.io.FileNotFoundException: test-output/emailable-report.html (Permission denied)
at java.io.FileOutputStream.open(Native Method)
How to fix this error...?
Below shows the Log file....
Building in workspace /home/probe7qa/probe7qa.svn/icoreemrtests/onc2014/170.314.a.9/src/eNotes
[eNotes] $ /bin/sh -xe /tmp/hudson1602450082114672082.sh
+ bash run.bat
[TestNG] Running:
/home/probe7qa/probe7qa.svn/icoreemrtests/onc2014/170.314.a.9/src/eNotes/testng.xml
===============================================
Suite
Total tests run: 12, Failures: 0, Skips: 12
Configuration Failures: 1, Skips: 1
===============================================
Build step 'Execute shell' marked build as failure
Finished: FAILURE