<div dir="ltr"><div id="yui_3_10_3_1_1380738345357_1120" class=""><p>Hello,</p>
<p>I am a Folsom user, I have been using the "nova list" command for a while until couple weeks ago.<br>
That command use to work just fine and one day it just stopped working.<br>
I can run the command but nothing will show up.</p>
<p>Here is the output of my command:</p>
<p>nova --debug list</p>
<p>REQ: curl -i <a rel="nofollow" href="http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail">http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail</a>
 -X GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" 
-H "Accept: application/json" -H "X-Auth-Token: f03bbc13f258473ab53399e3541a8e70"</p>
<p>connect: (127.0.0.1, 8774)<br>
send: u'GET /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail HTTP/1.1\r\nHost: <a href="http://127.0.0.1:8774">127.0.0.1:8774</a>\r\nx-auth-project-id: main\r\nx-auth-token: f03bbc13f258473ab53399e3541a8e70\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n'<br>


reply: 'HTTP/1.1 200 OK\r\n'<br>
header: X-Compute-Request-Id: req-002a752b-2f47-4cda-8f91-b9a822ef754b<br>
header: Content-Type: application/json<br>
header: Content-Length: 15<br>
header: Date: Thu, 26 Sep 2013 18:07:05 GMT<br>
RESP:{'status': '200', 'content-length': '15', 'content-location': u'<a rel="nofollow" href="http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail%27">http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail'</a>, 'x-compute-request-id': 'req-002a752b-2f47-4cda-8f91-b9a822ef754b', 'date': 'Thu, 26 Sep 2013 18:07:05 GMT', 'content-type': 'application/json'} {"servers": []}</p>

<p>I also tried with the option "all-tenant":</p>nova --debug list --all-tenants<br><br>REQ: curl -i <a href="http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1">http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1</a> -X GET -H "X-Auth-Project-Id: main" -H "User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token: 9b7d9b07f5b14793b1d24c5ca42bedd2"<br>

connect: (127.0.0.1, 8774)<br>send: u'GET /v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1 HTTP/1.1\r\nHost: <a href="http://127.0.0.1:8774">127.0.0.1:8774</a>\r\nx-auth-project-id: main\r\nx-auth-token: 9b7d9b07f5b14793b1d24c5ca42bedd2\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-novaclient\r\n\r\n'<br>

reply: 'HTTP/1.1 200 OK\r\n'<br>header: X-Compute-Request-Id: req-50e187e8-74b0-4342-a400-b364a61748e1<br>header: Content-Type: application/json<br>header: Content-Length: 15<br>header: Date: Wed, 02 Oct 2013 18:32:44 GMT<br>

RESP:{'status': '200', 'content-length': '15', 'content-location': u'<a href="http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1">http://127.0.0.1:8774/v2/ebdee2cb697449c9a374c006a8c2701f/servers/detail?all_tenants=1</a>', 'x-compute-request-id': 'req-50e187e8-74b0-4342-a400-b364a61748e1', 'date': 'Wed, 02 Oct 2013 18:32:44 GMT', 'content-type': 'application/json'} {"servers": []}
<p>Same thing with euca2ools:</p>
<p>euca-describe-instances --debug</p>
<p>2013-09-26 11:07:14,205 euca2ools [DEBUG]:Method: POST<br>
2013-09-26 11:07:14,205 euca2ools [DEBUG]:Path: /services/Cloud/<br>
2013-09-26 11:07:14,205 euca2ools [DEBUG]:Data:<br>
2013-09-26 11:07:14,205 euca2ools [DEBUG]:Headers: {}<br>
2013-09-26 11:07:14,205 euca2ools [DEBUG]:Host: <a href="http://127.0.0.1:8773">127.0.0.1:8773</a><br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:establishing HTTP connection: kwargs={}<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:Token: None<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:using _calc_signature_2<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:query string: AWSAccessKeyId=fbae4dab6bc045469c1f9f843d5d99b0&Action=DescribeInstances&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-09-26T18%3A07%3A14Z&Version=2010-08-31<br>


2013-09-26 11:07:14,206 euca2ools [DEBUG]:string_to_sign: POST<br>
<a href="http://127.0.0.1:8773">127.0.0.1:8773</a><br>
/services/Cloud/<br>
AWSAccessKeyId=fbae4dab6bc045469c1f9f843d5d99b0&Action=DescribeInstances&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-09-26T18%3A07%3A14Z&Version=2010-08-31<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:len(b64)=44<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:base64 encoded digest: aoAKyibiBwFSbMMiUiEivQCvF6o/Cf5E4yM82LN3LfI=<br>
2013-09-26 11:07:14,206 euca2ools [DEBUG]:query_string: AWSAccessKeyId=fbae4dab6bc045469c1f9f843d5d99b0&Action=DescribeInstances&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-09-26T18%3A07%3A14Z&Version=2010-08-31 Signature: aoAKyibiBwFSbMMiUiEivQCvF6o/Cf5E4yM82LN3LfI=<br>


send: 'POST /services/Cloud/ HTTP/1.1\r\nHost: <a href="http://127.0.0.1:8773">127.0.0.1:8773</a>\r\nAccept-Encoding: identity\r\nContent-Length: 231\r\nContent-Type: application/x-www-form-urlencoded; charset=UTF-8\r\nUser-Agent: Boto/2.2.2 (linux2)\r\n\r\nAWSAccessKeyId=fbae4dab6bc045469c1f9f843d5d99b0&Action=DescribeInstances&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2013-09-26T18%3A07%3A14Z&Version=2010-08-31&Signature=aoAKyibiBwFSbMMiUiEivQCvF6o%2FCf5E4yM82LN3LfI%3D'<br>


reply: 'HTTP/1.1 200 OK\r\n'<br>
header: Content-Type: text/xml<br>
header: Content-Length: 206<br>
header: Date: Thu, 26 Sep 2013 18:07:14 GMT<br>
2013-09-26 11:07:14,264 euca2ools [DEBUG]:<?xml version="1.0" ?><DescribeInstancesResponse xmlns="<a rel="nofollow" href="http://ec2.amazonaws.com/doc/2010-08-31/">http://ec2.amazonaws.com/doc/2010-08-31/</a>"><requestId>req-53dfca36-14fc-497d-a37d-220e6072e903</requestId><reservationSet/></DescribeInstancesResponse></p>


<p>I am getting a 200 from Keystone, so it's not an auth problem...<br>
Do you have any clues about that one?</p>Thanks a lot!<br>Clément</div>
</div>