Bug P2
Status Update
No update yet.
Comments
ji...@gmail.com
Just encountered a situation where an old version was used over 10 minutes after a deployment of new code ... well after all instances of the old version were completed ... gae is creating a new instance of an old version after a deployment ...
ma...@google.com
di...@gmail.com
Any news about this issue?
I'm experiencing this with every deploy I do on different applications.
It lasts hours before the problem resolves.. And my clients don't understand why a previous version of their website is sometimes still visible.
I do (still) use SDK version 1.5.5.
I'm experiencing this with every deploy I do on different applications.
It lasts hours before the problem resolves.. And my clients don't understand why a previous version of their website is sometimes still visible.
I do (still) use SDK version 1.5.5.
ja...@gmail.com
I am also being affected by this bug. Even after nuking all instances of the previous version, App Engine still spun one up after that version was no longer the default version.
ma...@google.com
ad...@firstdollar.com
I am also experiencing issues where old versions of deployments are still kept around, even though they are serving 0% of traffic. This is an intermittent issue, as usually the old version goes away when I redeploy. The worst part about this is that we are still charged for the old versions - I found out about this because a billing alert went off. I'm guessing this is a dupe of another issue because I've seen conversations about it going back years, for example:
runtime: nodejs
env: flex
network:
instance_tag: yada-yada-instance
name: yada-yada-name
subnetwork_name: yada-yada-subnetwork
# bare minimum resources below for testing
resources:
cpu: 1
memory_gb: 0.5
disk_size_gb: 10
automatic_scaling:
min_num_instances: 1
max_num_instances: 20
cool_down_period_sec: 60
cpu_utilization:
target_utilization: 0.80
env_variables:
NODE_ENV: "dev"
I've also attached a screenshot of the console showing old versions sticking around. Just deploying using gcloud app deploy app.dev.yaml.
Description
After an upgrade I am having a problem when new and old versions of the code are executed in different instances. Old instances are even dispatched after a deployment of a new version. I would think a new version should not be deployed until all prior version instances have terminated. This seems like a update deployment defect to me.
Tia