Shulou(Shulou.com)05/31 Report--

This article shows you how to solve the failure of creating a cloud disk in big data. The content is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

I. background

Log in to dashboard, click to create cloud disk failed, and directly report an error error after clicking.

Second, the process of settlement

Idea 1: the newly uploaded image image, is there a problem with the version of image

After inspection, it is found that the new image image is a new version of qcow2 format QEMU QCOW Image (v3)

# qemu-img info cloudera-quickstart-vm-5.7.0-0-kvm.qcow2 image: cloudera-quickstart-vm-5.7.0-0-kvm.qcow2file format: qcow2virtual size: 64G (68719476736 bytes) disk size: 8.3Gcluster_size: 65536Format specific information: compat: 1.1lazy refcounts: false

The compat of the old version of the mirror is 0.10

It is suspected that the version cannot be created due to a problem with the version. Try the version conversion.

# qemu-img amend-f qcow2-o compat=0.10 test.qcow2

As a result, the conversion also failed!

At the same time, I thought of trying to start the CVM directly from the image and found that the CVM started normally, so I denied the first idea.

Idea 2: failed to create a cloud disk from the image, check the log of cinder

At first, the id of the cloud disk was found in the log, but no useful information was found. Finally, a clue was found in the scheduler.log log.

# cd / var/log/cinder# view scheduler.log 2016-07-16 15 WARNING cinder.scheduler.host_manager 09VR 02.307 12684 WARNING cinder.scheduler.host_manager [req-42961a34-f2ae-4595-bb01-f4b862edfa49 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] volume service is down. (host: bdc212) 2016-07-16 15 WARNING cinder.scheduler.filter_scheduler 09VR 02.308 12684 WARNING cinder.scheduler.filter_scheduler [req-42961a34-f2ae-4595-bb01-f4b862edfa49 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] No weighed hosts found for volume with properties: {} 2016-07-16 15 WARNING cinder.scheduler.filter_scheduler 09V 09V 02.310 12684 ERROR cinder.scheduler.flows.create_volume [req-42961a34-f2ae-4595-bb01-f4b862edfa49 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid host was found. No weighed hosts available2016-07-16 15 457d-979b-c0a7f2e477f9 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 09 WARNING cinder.scheduler.host_manager [req-230ee887-c621-457d-979b-c0a7f2e477f9 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] volume service is down. (host: bdc212) 2016-07-16 15 WARNING cinder.scheduler.filter_scheduler 09 WARNING cinder.scheduler.filter_scheduler 30.888 12684 WARNING cinder.scheduler.filter_scheduler [req-230ee887-c621-457d-979b-c0a7f2e477f9 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] No weighed hosts found for volume with properties: {} 2016-07-16 15 WARNING cinder.scheduler.filter_scheduler 09VR 30.890 12684 ERROR cinder.scheduler.flows.create_volume [req-230ee887-c621-457d-979b-c0a7f2e477f9 3d8b93c202a94046be24e4eee5d16fb8 c05f2d7996144cb69921e64391db4512 -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid host was found. No weighed hosts available

Volume service is down in the log. (host: bdc212) explains the problem and examines the volume service on the bdc212 host

Bdc212

Warning keystonerc not sourced

= = Nova services = =

Openstack-nova-api: active

Openstack-nova-cert: active

Openstack-nova-compute: active

Openstack-nova-scheduler: active

Openstack-nova-conductor: active

= = Glance services = =

Openstack-glance-api: active

Openstack-glance-registry: active

= = Keystone service = =

= = Horizon service = =

Openstack-dashboard: active

= = neutron services = =

Neutron-server: active

Neutron-openvswitch-agent: active

= = Cinder services = =

Openstack-cinder-api: active

Openstack-cinder-scheduler: active

Openstack-cinder-volume: failed

= = Support services = =

Openvswitch: active

Dbus: active

Target: active

Rabbitmq-server: active

Memcached: active

= = Keystone users = =

The openstack-cinder-volume service status was found to be failed, so restart the openstack-cinder-volume service

# systemctl status openstack-cinder-volume ● openstack-cinder-volume.service-OpenStack Cinder Volume Server Loaded: loaded (/ usr/lib/systemd/system/openstack-cinder-volume.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-07-13 08:18:36 CST 3 days ago Main PID: 1775 (code=exited, status=1/FAILURE) Jul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 Jul 1815 36.002 1775 TRACE cinder File "/ usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py", line 413, in create_engineJul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 Vera 1836.002 1775 TRACE cinder _ test_connection (engine, max_retries) Retry_interval) Jul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 TRACE cinder File 1815 36.002 1775 TRACE cinder File "/ usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/session.py", line 591, in _ test_connectionJul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 8 TRACE cinder File 18 36 1775 TRACE cinder six.reraise (type (de_ref)) De_ref) Jul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 TRACE cinder File 1815 36.002 1775 TRACE cinder File ", line 2, in reraiseJul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 8 18 TRACE cinder File 36.002 1775 TRACE cinder DBConnectionError: (_ mysql_exceptions.OperationalError) (2003) "Can't connect to MySQL server on '192.168.8.212' (111l) Jul 13 08:18:36 bdc212 cinder-volume [1775]: 2016-07-13 08 18 TRACE cinderJul 36.002 1775 TRACE cinderJul 13 08:18:36 bdc212 systemd [1]: openstack-cinder-volume.service: main process exited, code=exited Status=1/FAILUREJul 13 08:18:36 bdc212 systemd [1]: Unit openstack-cinder-volume.service entered failed state.Jul 13 08:18:36 bdc212 systemd [1]: openstack-cinder-volume.service failed. [root@bdc212 scripts] # systemctl restart openstack-cinder-volume [root@bdc212 scripts] # systemctl status openstack-cinder-volume ● openstack-cinder-volume.service-OpenStack Cinder Volume Server Loaded: loaded (/ usr/lib/systemd/system/openstack-cinder-volume.service) Enabled; vendor preset: disabled) Active: active (running) since Sat 2016-07-16 15:13:25 CST 1s ago Main PID: 552481 (cinder-volume) CGroup: / system.slice/openstack-cinder-volume.service ├─ 552481 / usr/bin/python2 / usr/bin/cinder-volume-config-file / usr/share/cinder/cinder-dist.conf-config-file / etc/cinder/cinder.conf-logfile / var/log/cinder/volume.log └─ 552488 / usr/bin/python2 / usr/bin/cinder-volume-config-file / Usr/share/cinder/cinder-dist.conf-config-file / etc/cinder/cinder.conf-logfile / var/log/cinder/volume.logJul 16 15:13:25 bdc212 systemd [1]: Started OpenStack Cinder Volume Server.Jul 16 15:13:25 bdc212 systemd [1]: Starting OpenStack Cinder Volume Server...Jul 16 15:13:25 bdc212 cinder-volume [552481]: / usr/lib/python2.7/site-packages/cinder/openstack/common/service.py:38: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_config instead.Jul 16 15:13:25 bdc212 cinder-volume [552481]: from oslo.config import cfgJul 16 15:13:25 bdc212 cinder-volume [552481]: No handlers could be found for logger "oslo_config.cfg" Jul 16 15:13:26 bdc212 cinder-volume [552481]: 2016-07-16 15 from oslo.config import cfgJul 13purl 26.162 552481 INFO cinder.volume.manager [req-8fa3b983-e73d-4ec8-9186-6cb0a9ca7c95 -] Determined volume DB was not empty at startup .Jul 16 15:13:26 bdc212 cinder-volume [552481]: 2016-07-16 15 6cb0a9ca7c95 13 6cb0a9ca7c95 13 req-8fa3b983-e73d-4ec8 26.223 552481 INFO cinder.openstack.common.service [req-8fa3b983-e73d-4ec8-9186-6cb0a9ca7c95 -] Starting 1 workersJul 16 15:13:26 bdc212 cinder-volume [552481]: 2016-07-16 15 15 req-8fa3b983-e73d-4ec8 13 req-8fa3b983-e73d-4ec8 26.228 552481 INFO cinder.openstack.common.service [req-8fa3b983-e73d-4ec8-9186-6cb0a9ca7c95 -] Started Child 552488Jul 16 15:13:26 bdc212 cinder-volume [552481]: 2016-07-16 15 INFO cinder.service 13 purl 26.229 552488 INFO cinder.service [-] Starting cinder-volume node (version 2015.1.2) Jul 16 15:13:26 bdc212 cinder-volume [552481]: 2016-07-16 15 INFO cinder.service 13 INFO cinder.service 26.232 552488 INFO cinder.volume.manager [req-ee43f1f7-7c1b-4cda-9583-b8f40b188a5f -] Starting volume driver RBDDriver (1.1.0)

Create a cloud disk again and find that it can be created successfully!

The above is the process of solving the failure of creating a cloud disk in big data. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.