<div dir="ltr">I would think that the intent of the tests would be to use the /opt partition that was attached to the instance. I would think that we should be able to configure the resources to use /opt instead. or hack /var to be inside /opt.<div>
<br></div><div>Either way, growing the root volume would likely be the most painful route we could take. </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 4:35 AM, Kenichi Oomichi <span dir="ltr"><<a href="mailto:oomichi@mxs.nes.nec.co.jp" target="_blank">oomichi@mxs.nes.nec.co.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
I am investigating a gate failure(#1).<br>
On some sample(#2), "create server" continued to fail due to "No space left on device".<br>
Is it possible to extend the root partition?<br>
<br>
On the above sample, the fisrt IOError happened when writing a tempfile under /var/cache/nova directory:<br>
File "/opt/stack/new/python-keystoneclient/keystoneclient/middleware/auth_token.py", line 1337, in token_revocation_list<br>
f.write(value)<br>
IOError: [Errno 28] No space left on device<br>
<br>
According to some df.txt.gz's of successful samples[#3], the root partition seems small:<br>
Filesystem Size Used Avail Use% Mounted on<br>
/dev/vda1 9.9G 8.4G 1.1G 90% /<br>
udev 3.9G 12K 3.9G 1% /dev<br>
tmpfs 1.6G 384K 1.6G 1% /run<br>
none 5.0M 0 5.0M 0% /run/lock<br>
none 3.9G 4.0K 3.9G 1% /run/shm<br>
/dev/vdb2 219G 8.1G 200G 4% /opt<br>
cgroup 3.9G 0 3.9G 0% /sys/fs/cgroup<br>
/dev/loop0 6.0G 68M 6.0G 2% /opt/stack/data/swift/drives/sdb1<br>
<br>
I am not familiar with the gate test environment,<br>
so I'd like to know whether the above approach is right or not.<br>
<br>
<br>
Thanks<br>
Ken'ichi Ohmichi<br>
<br>
---<br>
#1: <a href="https://bugs.launchpad.net/tempest/+bug/1257641" target="_blank">https://bugs.launchpad.net/tempest/+bug/1257641</a><br>
#2: <a href="http://logs.openstack.org/18/62118/7/check/check-tempest-dsvm-full/3bfd6ec/logs/
#3" target="_blank">http://logs.openstack.org/18/62118/7/check/check-tempest-dsvm-full/3bfd6ec/logs/<br>
#3</a>: <a href="http://logs.openstack.org/26/68026/4/check/check-tempest-dsvm-full/aae25e0/logs/df.txt.gz" target="_blank">http://logs.openstack.org/26/68026/4/check/check-tempest-dsvm-full/aae25e0/logs/df.txt.gz</a><br>
<a href="http://logs.openstack.org/35/65635/5/check/check-tempest-dsvm-full/8e38e3e/logs/df.txt.gz" target="_blank">http://logs.openstack.org/35/65635/5/check/check-tempest-dsvm-full/8e38e3e/logs/df.txt.gz</a><br>
<a href="http://logs.openstack.org/75/67575/6/check/check-tempest-dsvm-full/0c62c6b/logs/df.txt.gz" target="_blank">http://logs.openstack.org/75/67575/6/check/check-tempest-dsvm-full/0c62c6b/logs/df.txt.gz</a><br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>If google has done it, Google did it right!
</div>