Hi Riccardo, Sorry for the late reply.
In my case I had the proper credentials in the config file but I did not have ADC set up yet (so no oauth.dat file). The comments in the code imply the if the oauth file does not exist then one is created. However, I don't see where the write occurs to create the file if the credentials return None. I see the storage.get() (gce.py line ~152), however if the credentials return None it just writes to the log. I don't see a storage.put() or something to create the oauth.dat file. In this case, the code then moves on to ADC. It would seem then that basically you need to have the oauth.dat file in place before starting elasticluster or you must have your environment set up correctly for ADC. ~Brian On Wednesday, June 26, 2019 at 4:31:25 AM UTC-4, Riccardo Murri wrote: > > Hello Brian, > > many thanks for taking the time to work around this issue and share > your findings here on the list. > > I would be interested in fixing this once and for all, so that other > people don't have to go through hoops to get ElastiCluster working. > If I read the code correctly, the ElastiCluster's Google Cloud code > should do the following: > > 1. If `gce_client_id` and `gce_client_secret` are given in the > configuration, try to use the credentials cached in the `oauth.dat` > file; > 2. If that fails, try to use "Application Default Credentials"; > 3. If that fails too, try to go through the OAuth auth process again. > > I understand this didn't work as expected in your case? > > Kind regards, > Riccardo > -- 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/a506c2f6-0ea8-492e-a6c6-d4177a4e86e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
