** Changed in: nova
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
Title:
nova and python-novaclient disagree on volumes API URLs
To
** Changed in: nova (Ubuntu)
Status: Confirmed = Invalid
** Changed in: python-novaclient (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
We cannot solve the issue you reported without more information. Could
you please provide the requested information ?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
Title:
nova
Apologies for the delay in replying. We recently completed our migration
to Keystone, and now nova volume-list works as expected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
it should be getting the url from keystone anyway, so I don't imagine
that the nova url is a problem. I think it is far more likely that you
have an older version of novaclient that is overiding the one from
precise. Perhaps you have pip installed novaclient or done a setup.py
install?
--
You
This Openstack installation is using deprecated auth, though, not
keystone. The following flags are in nova.conf:
--use_deprecated_auth
--auth_strategy=deprecated
I've only used Ubuntu packages on this machine — no devstack, no pip, no
setup.py.
--
You received this bug notification because
** Changed in: nova
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
Title:
nova and python-novaclient disagree on volumes API URLs
To manage
it looks like precise has an older version of novaclient? this was
changed around e-3 timeframe when we gave the volume api its own
endpoint.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
We are shipping the final version of 2012.1 for precise. in the archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
Title:
nova and python-novaclient disagree on volumes
I am not able to reproduce this on current precise 12.04 novaclient
packages running against an installation of the 12.04 packaged version
of essex.
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/
Looking at William's trace, I see some differences with the traces I
get. Not posting a full one in the first place was foolish of me. Here
it is now.
$ nova --debug volume-list
connect: (XXX.XXX.XXX.XXX, 8774)
send: 'GET /v1.1 HTTP/1.1\r\nHost: XXX.XXX.XXX.XXX:8774\r\nx-auth-project-id:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/996233
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: python-novaclient (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
13 matches
Mail list logo
