Description of problem: While trying to configure Xtremio iscsi back end on OSP14 I hit this traceback: 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume [req-03352d2f-8c3c-4e46-a79c-0239637ff47a - - - - -] Volume service controller-0@xtremio failed to start.: ImportError: No module named emc.xtremio 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume Traceback (most recent call last): 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/cinder/cmd/volume.py", line 104, in _launch_service 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume cluster=cluster) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/cinder/service.py", line 392, in create 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume cluster=cluster, **kwargs) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/cinder/service.py", line 155, in __init__ 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume *args, **kwargs) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/cinder/volume/manager.py", line 246, in __init__ 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume active_backend_id=curr_active_backend_id) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/oslo_utils/importutils.py", line 44, in import_object 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume return import_class(import_str)(*args, **kwargs) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume File "/usr/lib/python2.7/site-packages/oslo_utils/importutils.py", line 30, in import_class 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume __import__(mod_str) 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume ImportError: No module named emc.xtremio 2018-08-02 00:01:50.019 1 ERROR cinder.cmd.volume 2018-08-02 00:01:50.022 1 ERROR cinder.cmd.volume [req-03352d2f-8c3c-4e46-a79c-0239637ff47a - - - - -] No volume service(s) started successfully, terminating. The driver name changed to cinder.volume.drivers.dell_emc.xtremio while back there was some mapping file that would handle old/new naming mapping, it looks as if Rocky release delete this mapping file. I'll let Alan explain/add more technical info as he figured it out. Version-Release number of selected component (if applicable): puppet-cinder-13.1.1-0.20180701110900.3522fa1.el7ost.noarch How reproducible: Everytime. Steps to Reproduce: 1. Configure xtremio iscsi 2. Cinder volume docker fails to start. 3. Actual results: Failed to configure Xio iscsi back end. Expected results: Should work without issues as did up till Rocky/OSP14. Additional info:
No doc update necessary because the issue was resolved before upstream Rocky was released.
Hi , I have a setup with rhos14 , i changed the driver name and restart the dockers (cinder) Looks like , cinder-service is up and running but unable to create a volume . (overcloud) [stack@undercloud-0 ~]$ cinder get-pools --detail +-----------------------------+------------------------------+ | Property | Value | +-----------------------------+------------------------------+ | QoS_support | False | | allocated_capacity_gb | 0 | | consistencygroup_support | True | | driver_version | 1.0.10 | | filter_function | None | | free_capacity_gb | 154440.0 | | goodness_function | None | | max_over_subscription_ratio | 40.0 | | multiattach | False | | name | controller-0@xtremio#xtremio | | provisioned_capacity_gb | 380743 | | reserved_percentage | 0 | | storage_protocol | iSCSI | | thick_provisioning_support | False | | thin_provisioning_support | True | | timestamp | 2018-08-14T09:03:09.638608 | | total_capacity_gb | 7801 | | vendor_name | Dell EMC | | volume_backend_name | xtremio | +-----------------------------+------------------------------+ But create volume fails due to : /var/log/containers/cinder/cinder-scheduler.log:20:2018-08-14 07:29:52.917 1 ERROR cinder.scheduler.flows.create_volume [req-e03804e0-9e02-43f6-81e2-27acddf73248 bc20736bde014adca7a77c46aa209ca0 2d511a49cffc450db1db8ef743df7c81 - default default] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available: NoValidBackend: No valid backend was found. No weighed backends available Please advise. Benny
Chances are good that the cinder-volume service is failing. I'd start by checking that ("cinder service-list") and then examine the logs for that service.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:0045