ERROR (ClientException) nova image-list-阿里云开发者社区

开发者社区> cloud_ruiy> 正文

ERROR (ClientException) nova image-list

简介: nova image-listERROR (ClientException): The server has either erred or is incapable of performi9e-6cdca5eee7b2)   UNANSWERED Ask Yo...
+关注继续查看

nova image-list
ERROR (ClientException): The server has either erred or is incapable of performi9e-6cdca5eee7b2)

 

Ask Your Question
 
0
 

glance image-list is fine but, nova image-list error

asked Dec 14 '15

recital gravatar image

updated Dec 15 '15

I am installing liberty release on centos7 with one controller and one compute node. nova service-list and nova endpoints work fine. But, nova image-list returns the following error.

ERROR(ClientException) : Unexpected API Error. Please report this at http://bugs.launchpad.net/nova and attach the Nova API log if possible.
<class 'glanceclient.exc.HTTPInternalServerError'> (HTTP 500) (Request-ID: ...)

glance image-list works fine. Pls, help me out.

the nova-api.log is following.

2015-12-14 16:29:56.071 9986 INFO nova.osapi_compute.wsgi.server [req-496b5df0-e28f-486b-8386-96f704433daf 504f2af1b9044a3e97bc69e80daf5809 8de4c51458804564b79932efa364524b - - -] 192.168.219.11 "GET /v2/ HTTP/1.1" status: 200 len: 572 time: 0.0285130
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions [req-e65f8242-8d2c-43f1-af66-362f3161b655 504f2af1b9044a3e97bc69e80daf5809 8de4c51458804564b79932efa364524b - - -] Unexpected exception in API method
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions Traceback (most recent call last):
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 478, in wrapped
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     return f(*args, **kwargs)
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/images.py", line 145, in detail
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     **page_params)
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/nova/image/api.py", line 68, in get_all
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     return session.detail(context, **kwargs)
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/nova/image/glance.py", line 284, in detail
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     for image in images:
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 254, in list
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     for image in paginate(params, return_request_id):
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 238, in paginate
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     images, resp = self._list(url, "images")
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/glanceclient/v1/images.py", line 63, in _list
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     resp, body = self.client.get(url)
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 280, in get
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions     return self._request('GET', url, **kwargs)
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 272, in _request
2015-12-14 16:30:01.676 9986 ERROR nova.api.openstack.extensions ...
(more)
 

2 answers

Sort by » oldest newest most voted
 

 
0
 

answered Dec 15 '15

recital gravatar image

updated Dec 15 '15

I solved this problem. It's because keystone version is set as v2.0. You should change it as v3.

In "openstack endpoint list", it should be like this.

public & internal : http://controller:5000/v2.0 --> http://controller:5000/v3
admin : http://controller:5000/v2.0 --> http://controller:35357/v3

I refered to this site to change keystone db.

http://www.cloudkb.net/how-to-change-keystone-api-v2-v3/

You don't have to change "policy.json" file as instructed in the above site. After change the db, reboot your system. And all the CLI commands work well.

Thanks. recital.

link

Comments

I have the same problem and they same set up like you, but changing version didn't do the trick for me

still got the error after I rebooted the box, is this a bug and is there already a bug report?

thrawn gravatar imagethrawn (Dec 24 '15)

okay found my problem. Password was not the same in glance-registry.conf and glance-api.conf https://bugs.launchpad.net/nova/+bug/1514480 (https://bugs.launchpad.net/nova/+bug/...)

thrawn gravatar imagethrawn (Dec 24 '15)

 
0
 

answered Dec 14 '15

Prateek K gravatar image

You might have missed this configuration in nova.conf

[glance] api_servers = http:://<controllerip>:9292

link

Comments

I inserted "api_servers=http://controller:9292" in glance section on the controller node. After that, "su -s /bin/sh -c "nova-manage db sync" nova" and restart all the nova services. But, same problem happens when executing "nova image-list" on the controller node.

recital gravatar imagerecital (Dec 14 '15)

OK ... try this and see if it works now:---

[glance] host = controller

Prateek K gravatar imagePrateek K (Dec 14 '15)

I used the configuration at the first time. It didn't work...

recital gravatar imagerecital (Dec 14 '15)

ok... now it is becoming interesting... can you run the following command and paste the output here :-

nova --debug image-list

Prateek K gravatar imagePrateek K (Dec 14 '15)

I posted the logs for "nova --debug image-list" on the above.

recital gravatar imagerecital (Dec 14 '15)
 
 
 
How to change keystone API V2 to V3
Posted on November 26, 2014 by Gopalakrishnan S    0 Comments

The Keystone Identity Service allows clients to obtain tokens that can be used to access OpenStack cloud services. This document is intended for software developers interested in developing applications that utilize the Keystone Identity Service API for authentication. The OpenStack Identity API is implemented using a RESTful web service interface. All requests to authenticate and operate against the OpenStack Identity API should be performed using SSL over HTTP (HTTPS) on TCP port 443.
keystone V3 Advantages

1) Authentication is totally pluggable. You can write our own custom auth method. Beause of this extensible auth method, now keystone supports oauth1, federation ( federation is not fully done)

2) Authorization : V2 is either “admin” or none. In v3 you can control who can call each method. ( Provided you define your own policy file )

3) Separate drivers for assignments and identity

4) Rich set of APIs. There are lot more API available than v2.0. Also there are no vendor specic extension. If you check v2.0, most of the role apis are Rackspace extensions
Before proceed to migrate keystone v2 to v3, you must check previous services are working fine. Use the following commands to verify the list of services works.

How to change keystone API V2 to V3?

[root@localhost ~(keystone_admin)]# keystone user-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+———————————-+————+———+———————-+
| id | name | enabled | email |
+———————————-+————+———+———————-+
| ed03407c56054729bee58be7f7710786 | admin | True | root@localhost |
| 3b52f88a70f149a791e295b1859ae8f4 | ceilometer | True | ceilometer@localhost |

 

[root@localhost ~(keystone_admin)]# nova service-list
+——————+———–+———-+———+——-+—————————-+—————–+
| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
+——————+———–+———-+———+——-+—————————-+—————–+
| nova-consoleauth | packstack | internal | enabled | up | 2014-12-13T10:45:52.000000 | – |
| nova-scheduler | packstack | internal | enabled | up | 2014-12-13T10:45:50.000000 | – |
| nova-conductor | packstack | internal | enabled | up | 2014-12-13T10:45:54.000000 | – |
| nova-compute | packstack | nova | enabled | up | 2014-12-13T10:45:51.000000 | – |
| nova-cert | packstack | internal | enabled | up | 2014-12-13T10:45:52.000000 | – |
| nova-console | packstack | internal | enabled | up | 2014-12-13T10:45:51.000000 | – |
+——————+———–+———-+———+——-+—————————-+—————–+
[root@localhost ~(keystone_admin)]# glance image-list
+————————————–+——–+————-+——————+———-+——–+
| ID | Name | Disk Format | Container Format | Size | Status |
+————————————–+——–+————-+——————+———-+——–+
| f4c137ca-8dd8-47f3-be70-106eac2f241f | cirros | qcow2 | bare | 13147648 | active |
+————————————–+——–+————-+——————+———-+——–+

If all the services are working fine then proceed to migrate endpoint urls to V3 in your keystone databases.  Login your mysql server and change endpoint URLs.
mysql> use keystone;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed

mysql> select interface, url from endpoint e, service s where s.id=e.service_id and s.type=”identity”;
+———–+———————————-+
| interface | url |
+———–+———————————-+
| admin | http://192.168.1.133:35357/v2.0 |
| internal | http://192.168.1.133:5000/v2.0 |
| public | http://192.168.1.133:5000/v2.0 |
+———–+———————————-+
3 rows in set (0.01 sec)

Get the identity service ID

mysql> select id from service where type=”identity”;
+———————————-+
| id |
+———————————-+
| e32101fdfe4145d1a6a22351b41d88e5 |
+———————————-+
1 row in set (0.00 sec)
Use this query to replace URLs as per service id where 5000 ports
mysql> update endpoint set url=”http://192.168.1.196:5000/v3″ where url=”http://192.168.1.196:5000/v2.0″ and service_id=”76e23f322c2a48d18293db89dbca9e70″;
Query OK, 2 rows affected (0.00 sec)
Rows matched: 2 Changed: 2 Warnings: 0

Use this query to replace 35357 ports

mysql> update endpoint set url=”http://192.168.1.196:35357/v3″ where url=”http://192.168.1.196:35357/v2.0″ and service_id=”76e23f322c2a48d18293db89dbca9e70″;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

Thats all, you can verify the changed URLs.

mysql> select interface, url from endpoint e, service s where s.id=e.service_id and s.type=”identity”;
+———–+——————————–+
| interface | url |
+———–+——————————–+
| admin | http://192.168.1.133:35357/v3 |
| internal | http://192.168.1.133:5000/v3 |
| public | http://192.168.1.133:5000/v3 |
+———–+——————————–+
3 rows in set (0.00 sec)

mysql>

 
upgrade Keystone Policy File

Policy is just a set of rules combined by or/and logic. It should become more readable in future releases, The Openstack Identity v3 API, provided by Keystone, offers features that were lacking in the previous version. Among these features, it introduces the concept of domains, allowing isolation of projects and users. For instance, an administrator allowed to create projects and users in a given domain, may not have any right in another one. While these features look very exciting, some configuration needs to be done to have a working identity v3 service with domains properly set.

 
Download policy.v3cloudsample.json file

wget https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.json
mv /etc/keystone/policy.json /etc/keystone/policy.json.V2

mv policy.v3cloudsample.json /etc/keystone/policy.json

chown keystone.keystone policy.json

Update Keystone Endpoint Environment.

export OS_USERNAME=admin
export OS_TENANT_NAME=admin
export OS_PASSWORD=<password>
export OS_AUTH_URL=http://192.168.1.133:5000/v3
export SERVICE_ENDPOINT=http://192.168.1.133:35357/v3

export SERVICE_TOKEN=c50f58a02dde43f286517af102786be0

Restart OpenStack Services

/etc/init.d/openstack-keystone restart
Troubleshooting

If you received “horizon unauthorized (http 401)” errors, you can revert back policy.json v2 file and try to restart services.

 
How to Enable Multi Domains on openstack horizon

Horizon supports multi domains as well. You need to add only a few changes to local_setting. Apply the correct policy.json file for keystone.
vi /etc/openstack-dashboard/local_settings

uncommand the following settings.

OPENSTACK_API_VERSIONS = {
“identity”: 3
}
OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = True
OPENSTACK_KEYSTONE_URL = “http://192.168.1.133:5000/v3”
Save local_settings and restart openstack-dashboard.

/etc/init.d/httpd restart

 

 

版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

相关文章
阿里云服务器怎么设置密码?怎么停机?怎么重启服务器?
如果在创建实例时没有设置密码,或者密码丢失,您可以在控制台上重新设置实例的登录密码。本文仅描述如何在 ECS 管理控制台上修改实例登录密码。
9477 0
使用SSH远程登录阿里云ECS服务器
远程连接服务器以及配置环境
2462 0
windows server 2008阿里云ECS服务器安全设置
最近我们Sinesafe安全公司在为客户使用阿里云ecs服务器做安全的过程中,发现服务器基础安全性都没有做。为了为站长们提供更加有效的安全基础解决方案,我们Sinesafe将对阿里云服务器win2008 系统进行基础安全部署实战过程! 比较重要的几部分 1.
9047 0
阿里云服务器如何登录?阿里云服务器的三种登录方法
购买阿里云ECS云服务器后如何登录?场景不同,阿里云优惠总结大概有三种登录方式: 登录到ECS云服务器控制台 在ECS云服务器控制台用户可以更改密码、更换系.
13159 0
阿里云服务器如何登录?阿里云服务器的三种登录方法
购买阿里云ECS云服务器后如何登录?场景不同,云吞铺子总结大概有三种登录方式: 登录到ECS云服务器控制台 在ECS云服务器控制台用户可以更改密码、更换系统盘、创建快照、配置安全组等操作如何登录ECS云服务器控制台? 1、先登录到阿里云ECS服务器控制台 2、点击顶部的“控制台” 3、通过左侧栏,切换到“云服务器ECS”即可,如下图所示 通过ECS控制台的远程连接来登录到云服务器 阿里云ECS云服务器自带远程连接功能,使用该功能可以登录到云服务器,简单且方便,如下图:点击“远程连接”,第一次连接会自动生成6位数字密码,输入密码即可登录到云服务器上。
21885 0
阿里云服务器ECS登录用户名是什么?系统不同默认账号也不同
阿里云服务器Windows系统默认用户名administrator,Linux镜像服务器用户名root
4005 0
阿里云ECS云服务器初始化设置教程方法
阿里云ECS云服务器初始化是指将云服务器系统恢复到最初状态的过程,阿里云的服务器初始化是通过更换系统盘来实现的,是免费的,阿里云百科网分享服务器初始化教程: 服务器初始化教程方法 本文的服务器初始化是指将ECS云服务器系统恢复到最初状态,服务器中的数据也会被清空,所以初始化之前一定要先备份好。
6883 0
+关注
cloud_ruiy
爱技术,爱开源,爱linux! 在技术成长道路上,能拉一把就拉一把,不藏着不掖着! 我由衷希望能和有理想敢吃苦的it人一起共同进步,共同成长! 虽然我现在没有大牛的能力,但是我有大牛的心态. 技术领域:shell编程,C编程,嵌入式开发.hadoop大数据,桉树,onenebul
1715
文章
1
问答
文章排行榜
最热
最新
相关电子书
更多
《2021云上架构与运维峰会演讲合集》
立即下载
《零基础CSS入门教程》
立即下载
《零基础HTML入门教程》
立即下载