Fix bug in new UI that allowed duplicate LUNs
I managed to take down my little test cluster by not noticing that the lun number was defaulted to 0 always. This seems like something that the ui should protect a user from doing as it's a reasonable workflow to add a lun for a zfs snapshot.
#5 Updated by William Grzybowski about 2 years ago
- Category changed from GUI (new) to Middleware
- Assignee changed from Lola Yang to Waqar Ahmed
- Target version changed from 11.2-BETA3 to 11.2-BETA2
- Severity changed from New to Med High
We need to make sure middlewared does not accept same lun ID for target to extent. We also to allow null and use the next lun id available.