[rhos-list] novaclient issue

[Julie Pichon]

Hello,

"Lutz Christoph" <lchristoph at arago.de> wrote:
> > could you please explain a bit more, how you installed your OpenStack
> > deployment as well? ... is it a multi-node environment? SELinux enforcing?
> 
> Everything but nova is on a VM running on RHEL 6.4 and KVM (RHEV). I have one
> nova node that refers back to the "all the rest" VM running on hardware that
> supports KVM.

Could you confirm the versions for nova on your nova node, and nova client on your "all the rest" VM?
 
> > By any chance, is your Dashboard host able to connect to the nova host,
> > given by keystone catalog (Service compute)?
> 
> Dashboard is doing a login, authenticated by keystone. The request from the
> browser that fails is this:
> 
> GET /dashboard/admin/ HTTP/1.1
> Host: rhopenstack.example.com
> User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:21.0) Gecko/20100101
> Firefox/21.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language:
> en-us,en;q=0.8,de-de;q=0.5,de;q=0.3
> Accept-Encoding: gzip, deflate
> DNT: 1
> Referer: http://rhopenstack.example.com/dashboard
> Cookie: csrftoken=KdRnLZQvRfAtBcyHmGlQuHEmoxU1L2QO;
> sessionid=52e5ec63b1e720e255dd1791cfe9ec56
> Connection: keep-alive
> 
> That triggers an internal request to the nova API daemon:
> 
> GET
> /os-simple-tenant-usage?start=2013-06-01T00:00:00&end=2013-06-25T10:52:36.348852&detailed=1
> HTTP/1.1
> Host: 192.168.104.62:8774
> X-Auth-Project-Id: 4922a6443b9347d18f67c86bfb72022b
> Accept-Encoding: gzip, deflate, compress
> Content-Length: 0
> Accept: application/json
> User-Agent: python-novaclient
> X-Auth-Token: 28734c23bdf049d0b03b34a784c152b2
> 
> Nova answers with:
> 
> HTTP/1.1 300 Multiple Choices
> Content-Type: application/json
> Content-Length: 337
> Date: Tue, 25 Jun 2013 10:51:37 GMT
> 
> {\"choices\": [{\"status\": \"CURRENT\", \"media-types\": [{\"base\":
> \"application/xml\", \"type\":
> \"application/vnd.openstack.compute+xml;version=2\"}, {\"base\":
> \"application/json\", \"type\":
> \"application/vnd.openstack.compute+json;version=2\"}], \"id\": \"v2.0\",
> \"links\": [{\"href\":
> \"http://192.168.104.62:8774/v2/os-simple-tenant-usage\", \"rel\":
> \"self\"}]}]}

I think perhaps your nova endpoint is not configured properly. It should have the tenant id in it.

See the last comment in https://bugs.launchpad.net/horizon/+bug/967391:

    http://192.168.104.62:8774/v2.0

instead of:

    http://192.168.104.62:8774/v2/$(tenant_id)s
 
> > What about nova usage? Does that work for you? (Since the failing call
> > is hard-coded in novaclient) and I'm not aware of anybody else seeing
> > this issue.
> 
> I don't understand what you mean by "nova usage". I'm quite sure that the
> installation instructions from Red Hat are missing something, so far they
> proved not to be exact. Many copy-and-pastoes, etc. Very entertaining.
> Anyway, I have no idea *what* needs to be done to make the nova API daemon
> return the tenant_usage data. I can't use the dashboard to create any
> objects...

I think with "nova usage", Matthias meant to ask if this is working when using the command-line tools. If the above didn't help, could you try running "$ nova usage" and "$ nova usage-list" and see if it works or if the same problem occurs? Also running these commands with the --debug flag may give more information.

If you found deficiencies in the documentation, it would be really appreciated if you could file bugs about them! We'd love to fix it and help make the process smoother.

Thanks,

Julie