Unable to deploy an application module.

68 views
Skip to first unread message

Rüdiger Jungbeck

unread,
Jun 12, 2015, 4:34:06 AM6/12/15
to google-a...@googlegroups.com

I am unable to deploy an application module.

 appcfg.py update --oauth2 app.yaml producer.yaml

Error 409: --- begin server output ---
Another transaction by user rue1401 is already in progress for app:     s~lpsng2, version: 4. That user can undo the transaction with "appcfg rollback".
--- end server output ---

Doing an

appcfg.py rollback . --oauth2 app.yaml producer.yaml

indicates no error, but does not solve the problem.

Deploying the default modules (for the same application) works.

Deploying the same module to a different application works.

Posting this a production issue or asking on stackoverflow does not lead to any response for several days now.


What should I do?

Ryan (Cloud Platform Support)

unread,
Jun 12, 2015, 9:07:09 AM6/12/15
to google-a...@googlegroups.com, rue...@gmail.com
Salutations,

If you are still having this issue run the rollback on each module separately. 

Rüdiger Jungbeck

unread,
Jun 15, 2015, 5:01:47 AM6/15/15
to google-a...@googlegroups.com, rue...@gmail.com
Hello Ryan,

rolling back the default module in addition to the module showing the error does not solve my problem.

The module still shows the same error during deployment.

Any other ideas (like creating a new version)?

Ruediger

Ryan (Cloud Platform Support)

unread,
Jun 15, 2015, 9:42:09 AM6/15/15
to google-a...@googlegroups.com, rue...@gmail.com
Deploy each module separately. Start with the producer.yaml. If that fails then you should try another version. 

Rüdiger Jungbeck

unread,
Jun 15, 2015, 4:50:52 PM6/15/15
to google-a...@googlegroups.com, rue...@gmail.com

Hello Ryan,

thanks for your response.

Deploying producer.yaml first did not help.

Incrementing the version and deploying both modules finally solved the problem.

Ruediger

Ryan (Cloud Platform Support)

unread,
Jun 16, 2015, 9:47:14 AM6/16/15
to google-a...@googlegroups.com, rue...@gmail.com
I'm glad that worked for you!
Reply all
Reply to author
Forward
0 new messages