Multiple zones getting created with same initiator and target pair with Brocade Zone Manager enabled and pre-zoning

Bug #1338533 reported by deepali verneya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Low
Angela Smith

Bug Description

BUG Description :

Step to reproduce:
1. Disable auto-zoning
2. Clear all configurations from switch .(use cfgclear and thn cfgsave)
3. Create zone with one initiator and one target and save the configuration.
4. Do Volume attach
5. Enable autozoning using BCZM/Configure Brocade zone manager.
6. Create 3PAR FC volume
7. Attach volume to instance

Observation:
After the autozoning is enabled, new zone is getting created with a different name even though the initiator and the target is the same.

Expected Behavior:
Brocade zone manager should not create a different zone, if zone already exist with same initiator and target pair in switch – be it manually created or created by zone manager

Switch Output-

SVSCDLSAN07:FID128:admin> cfgshow

Defined configuration:
 cfg: OpenStack_Cfg
 zone1_9c; zone2_9c
                openstack5001438021e39b9e20010002ac004f45;
                openstack5001438021e39b9e21010002ac004f45;
                openstack5001438021e39b9c20010002ac004f45;
                openstack5001438021e39b9c21010002ac004f45
 zone: openstack5001438021e39b9c20010002ac004f45
                50:01:43:80:21:e3:9b:9c; 20:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9c21010002ac004f45
                50:01:43:80:21:e3:9b:9c; 21:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9e20010002ac004f45
                50:01:43:80:21:e3:9b:9e; 20:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9e21010002ac004f45
                50:01:43:80:21:e3:9b:9e; 21:01:00:02:ac:00:4f:45
zone: zone1_9c
 50:01:43:80:21:e3:9b:9c; 20:01:00:02:ac:00:4f:45
zone: zone2_9c
 50:01:43:80:21:e3:9b:9c; 21:01:00:02:ac:00:4f:45

Effective configuration:
 cfg: OpenStack_Cfg
 zone: openstack5001438021e39b9c20010002ac004f45
                50:01:43:80:21:e3:9b:9c
                20:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9c21010002ac004f45
                50:01:43:80:21:e3:9b:9c
                21:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9e20010002ac004f45
                50:01:43:80:21:e3:9b:9e
                20:01:00:02:ac:00:4f:45
 zone: openstack5001438021e39b9e21010002ac004f45
                50:01:43:80:21:e3:9b:9e
                21:01:00:02:ac:00:4f:45
zone: zone1_9c
        50:01:43:80:21:e3:9b:9c
               20:01:00:02:ac:00:4f:45
zone: zone2_9c
       50:01:43:80:21:e3:9b:9c
              21:01:00:02:ac:00:4f:45

NOTE: 1-Manually created zone- zone1_9c , zone2_9c
       2-Zones created after enabling autozoining
                openstack5001438021e39b9e20010002ac004f45
                openstack5001438021e39b9e21010002ac004f45
                openstack5001438021e39b9c20010002ac004f45
                openstack5001438021e39b9c21010002ac004f45

Tags: zonemanager
description: updated
Changed in cinder:
assignee: nobody → Angela Smith (aallen-m)
importance: Undecided → Low
Changed in cinder:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.