Comment 13 for bug 1371665

This begs me to ask why we are buffering the entire charm payload in memory.

On Mon, Sep 29, 2014 at 1:26 PM, Kevin W Monroe <email address hidden>
wrote:

> One other quick vagrant data point.. With --memory=1024 in Vagrantfile,
> 200MB charms succeed while 300MB charms fail.
>
> --
> You received this bug notification because you are subscribed to Juju
> Vagrant images.
> Matching subscriptions: vagrant-images
> https://bugs.launchpad.net/bugs/1371665
>
> Title:
> deploying large charms fail because vagrant needs more RAM
>
> Status in juju-core:
> Invalid
> Status in Juju Vagrant images:
> Triaged
>
> Bug description:
> Deploying a fat charm under Vagrant 1.6.5 on OSX 10.9.5 fails if the
> charm is large (around 600MB).
>
> $ juju version
> 1.20.7-trusty-amd64
>
> To reproduce, add some filler to ./files to get the charm over 600MB:
>
> $ cd ~/charms/precise/mycharm
> $ dd if=/dev/zero of=./files/foo bs=1M count=600
> $ du -sh
> 601M .
> $ juju deploy --repository ~/charms local:precise/mycharm --debug
> 2014-09-19 15:36:31 INFO juju.cmd supercommand.go:37 running juju
> [1.20.7-trusty-amd64 gc]
> 2014-09-19 15:36:31 DEBUG juju.conn api.go:187 trying cached API
> connection settings
> 2014-09-19 15:36:31 INFO juju.conn api.go:270 connecting to API
> addresses: [localhost:17070 10.0.3.1:17070 10.0.2.15:17070
> 172.16.250.15:17070]
> 2014-09-19 15:36:31 INFO juju.state.api apiclient.go:242 dialing
> "wss://localhost:17070/environment/aee94ed2-f800-4705-81ed-50921a2a1259/api"
> 2014-09-19 15:36:31 INFO juju.state.api apiclient.go:176 connection
> established to
> "wss://localhost:17070/environment/aee94ed2-f800-4705-81ed-50921a2a1259/api"
> 2014-09-19 15:36:46 INFO juju.utils http.go:66 hostname SSL verification
> disabled
> 2014-09-19 15:36:50 INFO juju.rpc server.go:334 error closing codec: EOF
> 2014-09-19 15:36:50 ERROR juju.cmd supercommand.go:323 cannot upload
> charm: Post https://localhost:17070/charms?series=precise: EOF
>
> Fwiw, I did a few rounds and found that a 575MB charm works, but 600MB
> does not. Note, this is not the same error that occurs when the
> filesystem fills up. That scenario fails (expectedly) like this:
>
> $ juju deploy --repository ~/charms local:precise/mycharm
> ERROR error uploading charm: cannot extract uploaded charm: cannot
> extract "files/foo": write
> /tmp/charm-download150588614/extracted/files/foo: no space left on device
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1371665/+subscriptions
>