Hi Brian (or Riccardo),

It looks like I'm running into the same credential authorizing issue Brian 
was when I try to start my cluster using:
elasticluster start agbclust

I get the message:
WARNING UserWarning: Cannot access 
<$HOME>/.elasticluster/storage/...apps.googleusercontent.com.oauth.dat: No 
such file or directory

Followed by the error:
ERROR Error creating instance `<HttpError 403 when requesting 
https://compute.googleapis.com/compute/v1/projects/.../zones/us-east1-c/instances?alt=json
 
returned "Request had insufficient authentication scopes.". Details: 
"Request had insufficient authentication scopes.">`

I've attached my config file (with sensitive info redacted). For the 
"gce_client_id" and "gce_client_secret" config keys, I've generated them 
following the instructions provided here...
https://googlegenomics.readthedocs.io/en/latest/use_cases/setup_gridengine_cluster_on_compute_engine/index.html#index-obtaining-client-id-and-client-secrets
...with the exception of selecting "Desktop" for OAuth client ID type as 
opposed to "Other" as suggested because that option doesn't exist.

Could you please expand on the solution Brian provided? I'm not seeing how 
to setup "Application Default Credentials" or create the oauth.dat file. 
Any help you could provide would be greatly appreciated.

Thank you,
Seth
On Sunday, June 23, 2019 at 10:38:53 PM UTC-7 Brian Moroz wrote:

> There may be a bug in elasticluster credential verification, however, you 
> can bypass this process by setting application default credentials (
> https://cloud.google.com/docs/authentication/production). From what I 
> have read, some folks don't need to do this while others do.
>
>
> On Saturday, June 22, 2019 at 4:13:36 PM UTC-4, Brian Moroz wrote:
>>
>> Hi,
>>
>> I followed a tutorial to test out GCP for some high-throughput computing:
>>  https://cloud.google.com/solutions/running-r-at-scale 
>> <https://cloud.google.com/solutions/running-r-at-scale>
>>
>> The command to create the cluster "elasticluster start myslurmcluster" 
>> produces a warning "WARNING UserWarning: Cannot access 
>> <$HOME>.elasticluster/storage/...apps.googleusercontent.com.oauth.dat: 
>> No such file or directory" which then leads to an error "ERROR Could not 
>> start node ... <class httplib.ResponseNotReady>"
>>
>> Everything works as stated up to attempting to start the cluster. Looks 
>> like a credential authorization problem. Is this a known issue? I'm trying 
>> to determine if I missed something or did something wrong before I contact 
>> Google (assuming this is their tutorial). I haven't seen much on this just 
>> browsing around.
>>
>> Thanks.
>>
>> Google Cloud SDK on Ubuntu 18.04 VM
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticluster" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticluster/8e51a67c-280c-4b45-b8ff-03f026889368n%40googlegroups.com.

Attachment: config
Description: Binary data

Reply via email to