Multiple zones getting created with same initiator and target pair with Brocade Zone Manager enabled and pre-zoning
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:
Defined configuration:
cfg: OpenStack_Cfg
zone1_9c; zone2_9c
zone: openstack500143
zone: openstack500143
zone: openstack500143
zone: openstack500143
zone: zone1_9c
50:01:
zone: zone2_9c
50:01:
Effective configuration:
cfg: OpenStack_Cfg
zone: openstack500143
zone: openstack500143
zone: openstack500143
zone: openstack500143
zone: zone1_9c
zone: zone2_9c
NOTE: 1-Manually created zone- zone1_9c , zone2_9c
2-Zones created after enabling autozoining
description: | updated |
Changed in cinder: | |
assignee: | nobody → Angela Smith (aallen-m) |
importance: | Undecided → Low |
Changed in cinder: | |
status: | New → Invalid |