Expected response to be successful, got 422

[cappelaere]

I am trying to release a docker slug to heroku

> heroku docker:release
...
Successfully built b240d9d7bf11
extracting slug from container...
creating remote slug...
language-pack: heroku-docker (ojobot_conda)
remote process types: { web: 'cd /app/user && node server.js' }
uploading slug [====================] 100% of 578 MB, 0.0s
releasing slug...
 !    Error: Expected response to be successful, got 422

Not sure what to do next at this point. Any help is welcome.
Thanks,
Pat.

[ransombriggs]

@cappelaere export HEROKU_DEBUG=1 and then run again. It will dump the JSON body which should have a better error message. The fact it does not print this error message is a bug, but having this JSON will help us debug your problem further.

[jdx]

Closing due to inactivity. Reply if you are still experiencing this issue.

[jfloff]

I'm having a similar issue, but I've tracked it down to the add-ons I'm choosing. I can deploy with only heroku-postgresql but as soon as I add some of my other addons (logentries, newrelic, rollbar, scheduler, sendgrid) it returns a 422.

Here's the log with HEROKU_DEBUG=1:

heroku-cli/5.2.24-4b7e305 (darwin-amd64) go1.6.2 /Users/jfloff/.local/share/heroku/cli/bin/heroku cmd: version
heroku-cli/5.2.24-4b7e305 (darwin-amd64) go1.6.2 /Users/jfloff/.local/share/heroku/cli/bin/heroku cmd: commands
heroku-cli/5.2.24-4b7e305 (darwin-amd64) go1.6.2 /Users/jfloff/.local/share/heroku/cli/bin/heroku cmd: container:release
Remote addons: heroku-postgresql (1)
Local addons: heroku-postgresql:hobby-dev, logentries:le_tryit, newrelic:wayne, rollbar:free, scheduler:standard, sendgrid:starter (6)
Missing addons: logentries:le_tryit, newrelic:wayne, rollbar:free, scheduler:standard, sendgrid:starter (5)
Provisioning logentries:le_tryit...
Provisioning newrelic:wayne...
Provisioning rollbar:free...
Provisioning scheduler:standard...
Provisioning sendgrid:starter...

[jdx]

@jfloff can you post this to the https://github.com/heroku/heroku-container-registry repo instead? A different team manages that project.

[jfloff]

Done. Thank you.