Ask Your Question
0

Cinder volume on SAN immediately removed

asked 2018-08-31 07:56:39 -0500

fattony666 gravatar image

updated 2018-08-31 07:57:08 -0500

Hi all,

We are running OpenStack Queens on Ubuntu 16.04 LTS and are using IBM DS4700 as external storage. To manage the storage, we have Brocade Network Advisor 14.3.1 and the Brocade Fibre Channel Zoning plugin setup and creating volumes on the external storage. That works.

However cinder-volume is not able to create the correct target-initiator zones, therefore the instances are not able to use created volumes.

The volume get created, the instances are getting created, but the zoning information is created and immediately removed by cinder again.

Please see below:

2018-08-31 14:39:23.620 4235 INFO cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Zone map to create: {'openstack_21000024ff0466a4500507680c111a9a': ['21:00:00:24:ff:04:66:a4', '50:05:07:68:0c:11:1a:9a'], 'openstack_21000024ff0466a4500507680c111a92': ['21:00:00:24:ff:04:66:a4', '50:05:07:68:0c:11:1a:92']}
2018-08-31 14:39:23.620 4235 INFO cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Zone map to update: {}
2018-08-31 14:39:29.776 4235 INFO cinder.zonemanager.fc_zone_manager [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Add connection: finished iterating over all target list
2018-08-31 14:39:29.947 4235 INFO cinder.volume.manager [req-6d52f55c-006d-43c0-b32e-59b9a32f0d2f 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] attachment_update completed successfully.
2018-08-31 14:39:41.092 4235 INFO cinder.volume.drivers.ibm.storwize_svc.storwize_svc_fc [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Need to remove FC Zone, building initiator target map.
2018-08-31 14:39:41.337 4235 INFO cinder.zonemanager.utils [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Using FC Zone Manager 1.0.2, Driver BrcdFCZoneDriver 1.5.
2018-08-31 14:39:41.338 4235 INFO cinder.zonemanager.fc_zone_manager [req-73c6e79a-fbdf-4718-b421-d2b3fd491655 8f6e2e71596f4e67bd02121a9f3ff3f5 3be8c468652748398997fd6b11188814 - default default] Delete connection target list: [u'500507680C211A92', u'50

Cinder creates the volume and the zoning information and then removes it immediately again with the message: "Need to remove FC Zone, building initiator target map."

We do not know why this message occures, any help appricated.

Thank you

edit retag flag offensive close merge delete

Comments

The message "Need to remove FC zone" is issued whenever a closed connection is cleaned up, i.e. it doesn't indicate what went wrong.

I don't know the interaction between Cinder drivers and FC arrays, but perhaps you get better information by enabling debug logging (debug = true in cinder.conf).

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-06 23:12:44 -0500 )edit

Use http://codesearch.openstack.org to find which code issues error messages. Even if your understanding of OpenStack internals and/or Python is limited, this is often useful.

Bernd Bausch gravatar imageBernd Bausch ( 2018-09-06 23:16:45 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
0

answered 2018-09-03 03:42:55 -0500

fattony666 gravatar image

updated 2018-09-05 07:25:11 -0500

Hi Vinoth, please see below our cinder.conf:

[DEFAULT]
rootwrap_config = /etc/cinder/rootwrap.conf
api_paste_confg = /etc/cinder/api-paste.ini
#iscsi_helper = tgtadm
volume_name_template = volume-%s
#volume_group = cinder-volumes
verbose = True
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/cinder/volumes
transport_url = rabbit://openstack:rabbitMQ@hrzgf01r01controller01
my_ip = 172.16.250.4
enabled_backends = hrzgf01svc01
glance_api_servers = http://hrzgf01r01controller01:9292
zoning_mode = fabric

[database]
connection = mysql+pymysql://cinder:rabbitMQ@hrzgf01r01controller01/cinder

[keystone_authtoken]
auth_uri = http://hrzgf01r01controller01:5000
auth_url = http://hrzgf01r01controller01:5000
memcached_servers = hrzgf01r01controller01:11211
auth_type = password
project_domain_id = default
user_domain_id = default
project_name = service
username = cinder
password = password

[oslo_concurrency]
lock_path = /var/lib/cinder/tmp

[hrzgf01svc01]
volume_driver = cinder.volume.drivers.ibm.storwize_svc.storwize_svc_fc.StorwizeSVCFCDriver
volume_backend_name = hrzgf01svc01
san_ip = 192.168.0.50
san_login = openstackadmin
san_password = password
storwize_svc_volpool_name = hrzgf01storagepool01
capabilities:storage_protocol='<in> FC'


[fc-zone-manager]

#
# From cinder
#

# South bound connector for zoning operation (string value)
brcd_sb_connector = HTTP

# Southbound connector for zoning operation (string value)
#cisco_sb_connector = cinder.zonemanager.drivers.cisco.cisco_fc_zone_client_cli.CiscoFCZoneClientCLI

# FC Zone Driver responsible for zone management (string value)
zone_driver = cinder.zonemanager.drivers.brocade.brcd_fc_zone_driver.BrcdFCZoneDriver

# Zoning policy configured by user; valid values include "initiator-target" or
# "initiator" (string value)
zoning_policy = initiator

# Comma separated list of Fibre Channel fabric names. This list of names is
# used to retrieve other SAN credentials for connecting to each SAN fabric
# (string value)
fc_fabric_names = fabric01,fabric02

# FC SAN Lookup Service (string value)
fc_san_lookup_service = cinder.zonemanager.drivers.brocade.brcd_fc_san_lookup_service.BrcdFCSanLookupService

# Set this to True when you want to allow an unsupported zone manager driver to
# start. Drivers that haven't maintained a working CI system and testing are
# marked as unsupported until CI is working again. This also marks a driver as
# deprecated and may be removed in the next release. (boolean value)
#enable_unsupported_driver = false


[fabric01]

# EMC switches

# From cinder
#

# South bound connector for the fabric. (string value)
# Possible values:
# SSH - <no description="" provided="">
# HTTP - <no description="" provided="">
# HTTPS - <no description="" provided="">
fc_southbound_protocol = HTTP

# Management IP of fabric. (string value)
fc_fabric_address = 192.168.0.30

# Fabric user ID. (string value)
fc_fabric_user = cinder

# Password for user. (string value)
fc_fabric_password = password

# Connecting port (port value)
# Minimum value: 0
# Maximum value: 65535
fc_fabric_port = 22

# Local SSH certificate Path. (string value)
#fc_fabric_ssh_cert_path =

# Overridden zoning policy. (string value)
zoning_policy = initiator-target

# Overridden zoning activation state. (boolean value)
zone_activate = true

# Overridden zone name prefix. (string value)
zone_name_prefix = openstack_

# Virtual Fabric ID. (string value)
#fc_virtual_fabric_id = <none>


[fabric02]

# Brocade switches

# From cinder
#

# South bound connector for the fabric. (string value)
# Possible values:
# SSH - <no description="" provided="">
# HTTP - <no description="" provided="">
# HTTPS - <no description="" provided="">
fc_southbound_protocol = HTTP

# Management IP of fabric. (string value)
fc_fabric_address = 192.168.0.28

# Fabric user ID. (string value)
fc_fabric_user = cinder

# Password for user. (string value)
fc_fabric_password = password

# Connecting port (port value)
# Minimum value: 0
# Maximum value: 65535
fc_fabric_port = 22

# Local SSH certificate Path. (string value)
#fc_fabric_ssh_cert_path =

# Overridden zoning policy. (string value)
zoning_policy = initiator-target

# Overridden zoning activation state. (boolean value)
zone_activate = true

# Overridden zone name prefix. (string value)
zone_name_prefix = openstack_

# Virtual Fabric ID. (string value)
#fc_virtual_fabric_id = <none>

// EDIT: As we are using a IBM storage system, it looks like the ... (more)

edit flag offensive delete link more
0

answered 2018-08-31 09:26:45 -0500

vinothkumar gravatar image

can you share me the cinder.conf file. So that I can help you.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2018-08-31 07:56:39 -0500

Seen: 37 times

Last updated: Sep 05