Other buckets seem to work fine. However, I need the bucket returned from AppIdentityServiceFactory.getAppIdentityService().getDefaultGcsBucketName(), otherwise my build and deploy process gets complicated.
I just created a new appid in the new console, -demo2, and uploaded my code. This did not create a GCS default bucket, which seems contrary to what I read here: https://cloud.google.com/appengine/kb/general#cloudintegration I went to the old console App Settings and clicked the "Enable Cloud Integration" button. That created the default bucket. But I'm back to the same problem with the previous appid - I can't upload to this bucket, not even from the console. AFAICT, there's no way to create a new appid and use the default bucket. It's just broken across the board. This means I can't create any new environments, and I'm starting to run into problems running client demos on my developer sandbox environment... Help, Jeff On Fri, Jul 10, 2015 at 1:36 PM, Patrice (Cloud Platform Support) < [email protected]> wrote: > Hmmm that is very peculiar. Is it something that is reproducible on OTHER > buckets in the same project? > > Because as you say, this bucket seems to be completely off. If you can > reproduce on another bucket in the same app, this might be something else. > > Cheers, and have a good weekend :) > > > On Friday, July 10, 2015 at 3:02:39 PM UTC-4, Jeff Schnitzer wrote: >> >> One more data point. >> >> Trying to upload a file via the Storage Browser gives me "Backend Error": >> >> http://monosnap.com/image/0pWxvlS0jXgGtGsryv5E3zgnMMpfm9.png >> >> This bucket seems to be broken somehow. How can I get it fixed? >> >> Thanks, >> Jeff >> >> On Thu, Jul 9, 2015 at 10:07 AM, Jeff Schnitzer <[email protected]> >> wrote: >> >>> Yep, [email protected] is listed in the >>> permissions with Can Edit. >>> >>> Comparing against the appids that work, however, I notice that the >>> working appid has a permission granted to >>> [email protected]. I tried adding that to >>> the new app but it is in "Invitation sent" state (and uploads still produce >>> 503). >>> >>> I'm stumped. >>> >>> Jeff >>> >>> >>> On Thu, Jul 9, 2015 at 7:19 AM, Patrice (Cloud Platform Support) < >>> [email protected]> wrote: >>> >>>> Jeff, I wasn't sure that the daily budget was the culprit here, but I >>>> can tell you that for certain APIs, your account is considered "free" if >>>> you don't have billing enabled AND a daily budget > 0. This is why I wanted >>>> to make sure your account was properly configured first. If this was the >>>> issue and you changed it, the change is immediate. >>>> >>>> Joseph has a very valid point here. Does the ACL of your application >>>> contains the service account of the other? >>>> >>>> >>>> >>>> >>>> On Wednesday, July 8, 2015 at 8:05:36 PM UTC-4, Jeff Schnitzer wrote: >>>>> >>>>> Billing is enabled with a valid card. There's also plenty of the >>>>> startup credit. With a little hunting I found the Daily Budget setting >>>>> which was 0, I upped that. Still getting 503 - should it recognize the >>>>> change immediately? >>>>> >>>>> This budget setting has not been necessary in the other two test >>>>> environments that I have deployed this code to, which are still working >>>>> fine. What changed? >>>>> >>>>> Thanks, >>>>> Jeff >>>>> >>>>> On Wed, Jul 8, 2015 at 1:41 PM, Patrice (Cloud Platform Support) < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi Jeff, >>>>>> >>>>>> Just doing the normal checks : Is billing enabled on the project? GCS >>>>>> needs billing, so it's possible you get 503 if it isn't (or if your daily >>>>>> budget is still at 0, the default value). >>>>>> >>>>>> Cheers >>>>>> >>>>>> >>>>>> On Wednesday, July 8, 2015 at 4:09:09 PM UTC-4, Jeff Schnitzer wrote: >>>>>>> >>>>>>> I'm setting up a demo environment on a new appid and running into >>>>>>> some problems with GCS. Unless otherwise mentioned, all of this is using >>>>>>> the new console. >>>>>>> >>>>>>> The first strange thing is that a default bucket was not created. >>>>>>> When making appids before, the default bucket was created automatically. >>>>>>> With a little digging I found a button in the old console App Settings >>>>>>> that >>>>>>> added a default GCS bucket, and that seemed to work. I have a default >>>>>>> bucket named gearlaunch-hub-demo.appspot.com. >>>>>>> >>>>>>> Now when I try to upload (using the same code that works on other >>>>>>> appids), I get a 503 error on the client. There's nothing in the logs >>>>>>> about >>>>>>> this error. >>>>>>> >>>>>>> Any idea what's up, or how I can get uploads working? >>>>>>> >>>>>>> My appid is gearlaunch-hub-demo. The options passed >>>>>>> to createUploadUrl are: >>>>>>> >>>>>>> >>>>>>> UploadOptions.Builder.withGoogleStorageBucketName(AppIdentityServiceFactory.getAppIdentityService().getDefaultGcsBucketName()) >>>>>>> >>>>>>> Thanks, >>>>>>> Jeff >>>>>>> >>>>>> >>>>> >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CADK-0uix5-pTmcK1%2BKF2h18RFd1x90eAN1-ddeA3%3DwFjeMgtWA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
