gcf reports quota exceeded; cf works (and I'm not out of quota) about cli HOT 7 CLOSED

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: http://www.pivotaltracker.com/story/show/64387618

from cli.

It appears that /v2/apps?async=true endpoint returns the out of memory error if the instance and memory information are not included on the call. I guess the cf gem is not calling this same endpoint.

from cli.

Hey Andy.

I don't think it was a change in the cli that triggered this behavior. I think it was a change in default memory allocation on run.pivotal.io. v5 wouldn't have this problem because they don't use server defaults, instead asking for memory interactively.

run.pivotal.io's default memory allocation changed to 1G a couple weeks back. My guess would be that you have quota available, but not quite 1G of quota.

Can you push an app with 1G of memory from v5?

from cli.

Aha. OK. Well, I don't have 1G now, because I pushed a bunch more apps grin.

So, if I don't specify a memory limit using v6, what will it ask the CC for by default? I guess that default value is busting the amount I do/did have. Generally I've been pushing small test apps in the 128 or 256M range lately, I should be able to fit a bunch of those in the space I still have available. Either way, it was a surprise. I realise that the validation that v6 does up front will change things as compared to the way v5 behaved with the interactive prompts...

from cli.

The CLI won't ask the CC. It will let the CC figure that out using the CC's own defaults, which means that the behavior differs by environment.

If you look at the trace you sent us, we're not POSTing any memory value. The CC fills in the blanks, here; on run.pivotal.io, they decided to go with 1G. Which, in combination with the default quota, busts the limit very quickly.

When I'm testing on run.pivotal.io, I push from a folder containing a manifest to ameliorate this issue.

Manifest.yml:

---
  memory: 256M

This allows me to basically set my own default, and avoid having to -m every time.

from cli.

ah I get you - my bad. Thanks.

from cli.

Probably good to close then, assuming that this gets picked up in docs / community evangelism explanations.... :-)

from cli.