Cloud Endpoints Not Updated After Deployment
107 views
Skip to first unread message
Phua Khai Fong
Dec 7, 2015, 7:45:14 PM12/7/15
to Google App Engine
This started yesterday for me from 7th Dec 2015.
After successful deployment of an app, the cloud endpoints part is not updated.
Checking from the admin console logs, both /_ah/spi/BackendService.logMessages and /_ah/spi/BackendService.getApiConfigs return status 200
If I use api explorer on the https://version-dot-appid.appspot.com/_ah/api/explorer, I can see the updated endpoints.
But using api explorer on the default version does not show the changes.
I am using "gcloud preview app deploy app.yaml --promote" to deploy, it was working fine previously.
What can I do to fix this? I need the updates to the cloud endpoints badly.
Phua Khai Fong
Dec 8, 2015, 12:33:25 AM12/8/15
to Google App Engine
Update:
If I use appcfg.py to deploy, the cloud endpoints gets updated.
Only when using gcloud it does not get updated.
Nick (Cloud Platform Support)
Dec 8, 2015, 7:21:22 PM12/8/15
to Google App Engine
Can you attempt to run the gcloud command with --verbosity DEBUG, and as well, can you check to be sure that "promote" is working properly? If you were pushing to another version than default, that would explain why visiting the default through the API explorer showed no updates.
Nick (Cloud Platform Support)
Dec 14, 2015, 4:58:15 PM12/14/15
to Google App Engine
Hey Phua,
You should consider posting threads like this, asking for specific-issue one-on-one technical support, to StackOverflow, or getting a Support Package from Google Cloud Platform Support. We monitor relevant tags on Stack Overflow and Server Fault, etc., and there are much larger communities there anyways. This forum is meant for more high-level discussion about the platform and services, so a thread like this is somewhat off-topic. When you post there, be sure to include the output I mentioned, along with any other information you think might be useful to someone attempting to debug the issue from the other side of the world, with no access to your system.
Best of luck!
You should consider posting threads like this, asking for specific-issue one-on-one technical support, to StackOverflow, or getting a Support Package from Google Cloud Platform Support. We monitor relevant tags on Stack Overflow and Server Fault, etc., and there are much larger communities there anyways. This forum is meant for more high-level discussion about the platform and services, so a thread like this is somewhat off-topic. When you post there, be sure to include the output I mentioned, along with any other information you think might be useful to someone attempting to debug the issue from the other side of the world, with no access to your system.
Best of luck!
Ben Plowman
Dec 14, 2015, 5:28:53 PM12/14/15
to Google App Engine
Hi Nick,
Phua's request is pointing out a widespread issue with Google App Engine, which my company is also experiencing, and not a request for one-on-one technical support. As he points out, the command previously worked fine but has stopped working, so it's not like he is a beginner asking for simple help. It is a bug with GAE, so please treat it as such.
Phua's request is pointing out a widespread issue with Google App Engine, which my company is also experiencing, and not a request for one-on-one technical support. As he points out, the command previously worked fine but has stopped working, so it's not like he is a beginner asking for simple help. It is a bug with GAE, so please treat it as such.
Nick (Cloud Platform Support)
Dec 14, 2015, 5:45:56 PM12/14/15
to Google App Engine
Hey Ben,
If you or anyone at your company have an issue to report during normal use, rather than a specific issue for which you'd like one-on-one technical support, you should post to the Public Issue Tracker for the relevant product, such as App Engine, Cloud SQL, the gcloud SDK tool, or the Cloud Platform generally - this is the proper way to treat an issue with GAE. As explained above and in many threads in this forum, this forum isn't the right place to report issues, but is meant for high-level discussion.
While people do nonetheless make threads in this forum when experiencing an issue, the vast majority of the time they're the only one experiencing the issue, and it traces back to their own actions (incorrectly following a tutorial, misusing a certain pattern, failing to read and understand error output, etc). Rarely, though it does happen, they're posting (as here) about an issue which affects multiple users (perhaps unbeknownst to them at the time of posting). In such a case, it's regardless better to post in the Public Issue Tracker for the appropriate product, since this allows us to properly tag the thread for response by engineering who work on the issue, and keep this forum freed up for what it should be for, general and high-level discussion, instead of issue tracking.
So, feel free to create a PIT thread for this issue if you can't find one already to star or comment on. From a quick search of my own, it seems nobody has reported this issue properly yet. Including verbose logs output and as much information as possible about the issue and your system are going to make sure that it's processed as quickly as possible.
If you or anyone at your company have an issue to report during normal use, rather than a specific issue for which you'd like one-on-one technical support, you should post to the Public Issue Tracker for the relevant product, such as App Engine, Cloud SQL, the gcloud SDK tool, or the Cloud Platform generally - this is the proper way to treat an issue with GAE. As explained above and in many threads in this forum, this forum isn't the right place to report issues, but is meant for high-level discussion.
While people do nonetheless make threads in this forum when experiencing an issue, the vast majority of the time they're the only one experiencing the issue, and it traces back to their own actions (incorrectly following a tutorial, misusing a certain pattern, failing to read and understand error output, etc). Rarely, though it does happen, they're posting (as here) about an issue which affects multiple users (perhaps unbeknownst to them at the time of posting). In such a case, it's regardless better to post in the Public Issue Tracker for the appropriate product, since this allows us to properly tag the thread for response by engineering who work on the issue, and keep this forum freed up for what it should be for, general and high-level discussion, instead of issue tracking.
So, feel free to create a PIT thread for this issue if you can't find one already to star or comment on. From a quick search of my own, it seems nobody has reported this issue properly yet. Including verbose logs output and as much information as possible about the issue and your system are going to make sure that it's processed as quickly as possible.
Phua Khai Fong
Dec 17, 2015, 6:22:27 PM12/17/15
to Google App Engine
Hi Nick,
Sorry I couldn't reply earlier.
I did not try to make gcloud deployments work as appcfg.py is working well.
As with all google cloud platform services, there are times when things are down and they come back up automatically after a while.
Hence, I did not try to debug further as it might also be my own mistake and an isolated problem.
I will take note to post in StackOverflow for more technical stuff.
Nick (Cloud Platform Support)
Dec 17, 2015, 7:40:27 PM12/17/15
to Google App Engine
Hey Phua and Ben,
If this issue is still occurring for either of you, or anybody reading this post, I'd like to reiterate that the best thing to do is make a post to the Public Issue Tracker. From the way Phua describes it, and from the lack of activity in the thread, I'm guessing this is transient, however.
If this issue is still occurring for either of you, or anybody reading this post, I'd like to reiterate that the best thing to do is make a post to the Public Issue Tracker. From the way Phua describes it, and from the lack of activity in the thread, I'm guessing this is transient, however.
Reply all
Reply to author
Forward
0 new messages