Production SDK stuck at 1.9.48?

[Attila-Mihaly Balazs]

Hello,

I see the following in my logs: "app_engine_release=1.9.48". This is for a production Python application running in Appengine standard in the EU region. I'm wondering why it uses 1.9.48, when 1.9.50 came out more than a month ago?

Regards,
Attila

[George (Cloud Platform Support)]

What is the output of the gcloud info command? 

Have you run gcloud components update recently? 

Providing whole lines of logs might help us in identifying the proper context of the error. 

[Attila-Mihaly Balazs]

Please see the output of "gcloud info" in the attachment. I did not run "gcloud update" recently (I'm using the Google debian repositories to install / update gcloud as described here: https://cloud.google.com/sdk/downloads#apt-get). For what it's worth I'm still using "appcfg.py" from the Python GAE SDK to deploy (planning on migrating to gcloud in the next couple of weeks). The Python SDK is up-to-date as of now (1.9.50 - downloaded from here: https://storage.googleapis.com/appengine-sdks/featured/google_appengine_1.9.50.zip).

An example log line would be:

108.[edited] - - [01/Mar/2017:15:58:32 +0200] "GET /api/[edited] HTTP/1.1" 200 453 - "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36" "[edited]" ms=53 cpu_ms=21 cpm_usd=5.0626e-8 loading_request=0 instance=00c61b117c98f90c5b7f6192e3168f1cbc8f8a4795fa6f798b6156534b8588ce3c9cf5520a7a app_engine_release=1.9.48 trace_id=-

Regards,
Attila

[George (Cloud Platform Support)]

The preferred tooling for managing your App Engine applications in Python is now the Google Cloud SDK. If you choose to use the App Engine SDK for deployment instead, you need to take care it is up-to-date following recommended procedures. The "Download the SDK for App Engine" document details the usual install method.  

Is there a particular reason why you should find the Cloud SDK repugnant? Have you tried deploying with the help of the Cloud SDK? 

The discrepancy in app engine release numbers appears of little consequence to an outsider, seen that you plan to anyhow start using the Cloud SDK in a couple of weeks. Here I am referring to this bracketed statement by Mr. Attila-Mihaly Balazs: (planning on migrating to gcloud in the next couple of weeks).

[Peter K]

Hi George:

can you please expand what you mean by this that does not parse for me?

"The discrepancy in app engine release numbers appears of little consequence to an outsider, seen that you plan to anyhow start using the Cloud SDK in a couple of weeks."

wrt the Cloud SDK tool, a few months ago I posted a question in this list whether anybody had migrated from appcfg to gcloud SDK and received no answers. appcfg has been working really well for me, is integrated with all my testing and deployment automation. Furthermore, I already spent a lot of time in infrastructure recently migrating away from channels and the new new super expensive stackdriver based logging, and am reluctant to charter the unknowns again; at least before I hear some success stories and/or gotchas.

[Kaan Soral]

Just checked gcloud myself, compared to appcfg, I really really like the examples, as in the past, the GUI approach was spammy and insufficient, I like the new CLI based approach, and the documentations seem adequate too (Feedback: You seriously need to send emails when changes happen, new things are added, I'm ashamed that I didn't discover the gcloud CLI and the new documentations up to this point)

For some projects, I'm locked with old versions of appcfg, yet, for deployments and new projects, gcloud seems nice

I think the confusion arises from this: """ Does the method you deploy with, determine the version of appengine your app runs with?! """ - Because, as an outsider, the assumption is that, unless you explicitly set something, the apps should always run with the latest version

[PK]

Hi Kaan,

I am not sure what what is the GUI you refer to. I never used a GUI, I have always been using appcfg.py as a CLI tool.

PK 

www.gae123.com

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/0s1EHuF4qDs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/9355e066-ddde-4492-9632-35030e83bf14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kaan Soral]

I guess it was "AppEngine Launcher" back in the day, on OSX, it regularly popped up and wanted to update itself, there was no 2-second way to get rid of it either, it was pretty much behaved like the old adware's

I was afraid gcloud was going to be something like that, however, having a CLI system replace another CLI system isn't that bad

I think the main problem is the lack of information, one email, one document with simple: "You did this with appcfg, now do this with gcloud" document would be enough, as there seem to be 1:1 replacements to appcfg operations simply available

[Attila-Mihaly Balazs]

Sorry y'all, but getting back to the original topic: both of my applications (I have a "staging" and a "production" one) are stuck on 1.9.48, even though 1.9.51 is out!

Relevant logs:

- Staging:

<edited> - - [27/Mar/2017:10:49:55 +0300] "POST <edited> HTTP/1.1" 200 137 - "<edited>" "<edited>" ms=12 cpu_ms=6 cpm_usd=1.531e-8 loading_request=0 instance=00c61b117c3d531f29ab70f01f432a316cff3c620255897cf3b3016d31b95d3cff0023c4189f0e app_engine_release=1.9.48 trace_id=-

- Production:

<edited> - - [27/Mar/2017:10:49:21 +0300] "GET <edited> HTTP/1.1" 302 - - "<edited>" "<edited>" ms=661 cpu_ms=0 cpm_usd=0 loading_request=0 instance=- app_engine_release=1.9.48 trace_id=5da331cbc41493ef21734a0d6b83c920


I used the latest python SDK (1.9.51) to do the deploy. I will also try it with gcloud, however it takes a little while to update the deployment script (and I also want to use this opportunity to parralelize the deployment of our different modules/services to reduce the deploy time).

Attila

[pdknsk]

I'm on 1.9.48 and use gcloud. Might be a display bug.

[Attila-Mihaly Balazs]

I'm pretty sure it isn't a display bug since I used to also see "1.9.48" listed next to each instance on the "Instances" page (I no longer see it - perhaps they changed something and no longer display that column?)

Attila

[pdknsk]

gcloud prints the same.

$ gcloud app instances describe <instance> --service default --version <version>

appEngineRelease: 1.9.48

...

I doubt it makes a differences as there have been no significant updates in months, if not years.

[Attila-Mihaly Balazs]

AFAIK they update it every two months or so. The latest SDK version downloadable from the site is 1.9.51, so I'm guessing there are at least some bugfixes / improvements which could help my applications.

Attila

[Attila-Mihaly Balazs]

This is still happening so I created an issue: https://issuetracker.google.com/u/1/issues/62015795

[pdknsk]

As of a few hours ago, logs report the newest version. This is without redeployment, making the case more likely that this was just a display issue, I think. Instances weren't restarted either, as the first loading request was about 10 minutes after the instance already reported the newest version.

[Attila-Mihaly Balazs]

Thank you for posting the update.

Unfortunately I'm still seeing 1.9.48 on my instances. Hopefully this is some kind of rolling update which will get to my apps soon :-)

Attila

[pdknsk]

I incorrectly stated that it's the newest version. It's 1.9.54 which was released three months ago. Still, progress.

[pdknsk]

As I read the release notes, it occurred to me that this is definitely only a display bug.

https://cloud.google.com/appengine/docs/standard/python/release-notes

When 1.9.55 was released last month I swapped json for ujson and re-deployed, so the instance cannot be running either of the reported versions. (For some reason I missed the connection back then.) I double-checked in Stackdriver Debug that it's actually ujson.