Closed faithman closed 5 years ago
Hi Ye
The pipeline seems to be working across multiple other projects. It seems like the issue might be directly related to your project specifically.
1) Can you try creating a new project and running using the pipelines API?
2) Can you try redoing the simple tutorial with the pipelines API in this new project as well?
3) Can you provide the full error message for the VM instance that is not starting from the activity page we looked over?
Thanks Russ
You can also enable -trace on Nextflow for pipelines using below:
Google Pipelines debugging information can be enabled using the -trace command line option as shown below:
nextflow -trace nextflow.cloud.google.pipelines run
Closing because there's any more feedback. Feel free to comment/re-open if the problem persists.
Bug report
The VMs can not be launched when I run a Nextflow pipeline using Google genomic API.
Expected behavior and actual behavior
I saw the first processes of Nextflow pipeline were successfully launched. However, the pipeline were idled at this state without exit or error. Then I checked the activity of google could platform, I saw it said failed to create VM with the error message of
Invalid argument (HTTP 400): INVALID_ARGUMENT
. Then, I checked the workdir of the launched processes, I saw.command.run
,.command.sh
, and.command.stub
were in the bucket, but no.command.begin
.I tried to run the example pipeline from google shell, my local Mac, and cluster. All of them give me the same issue. I also tried to run my pipeline. Still got the same issue.
So, it seems the VM not started, and Nextflow also not able to report this error.
Steps to reproduce the problem
I followed the guidances here. And used the example Nextflow pipeline.
I am pretty sure I have the permission to the bucket. I enabled the Genomic API, generated the credential for a server count which with the project owner role, add the .json file to
GOOGLE_APPLICATION_CREDENTIALS
.The project of GCP I used here is an old project at least created for 4 years, not sure if this is the problem. Cause other users with new project are not able to reproduce my issue.
I changed the nextflow.log to suit my google bucket path.
Program output
Here is the .nextflow.log
Environment