Activity log for bug #1338533

Date Who What changed Old value New value Message
2014-07-07 10:53:21 deepali verneya bug added bug
2014-07-07 10:54:00 deepali verneya 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 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
2014-07-07 18:11:51 Walt Boring cinder: assignee Angela Smith (aallen-m)
2014-07-07 18:12:15 Walt Boring cinder: importance Undecided Low
2014-07-28 17:08:23 Walt Boring cinder: status New Invalid