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/772e4014-77b3-4dae-bc90-1925153c7a53%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
