bug 6936: for some reason, we had a check on pod-wide or account specific vlan creation. This seems to be a left over from legacy code. Removing the same. I tested to make sure both zone wide vlan and account specific vlan creation for direct tagged case works fine

status 6936: resolved fixed
This commit is contained in:
abhishek 2010-11-19 17:52:58 -08:00
parent 2586214b21
commit ca162bca11
1 changed files with 4 additions and 4 deletions

View File

@ -1516,10 +1516,10 @@ public class ConfigurationManagerImpl implements ConfigurationManager, Configura
associateIpRangeToAccount = true;
}
} else if (vlanType.equals(VlanType.DirectAttached)) {
if (!((account != null && podId == null) ||
(account == null && podId != null))) {
throw new InvalidParameterValueException("Direct Attached IP ranges must either be pod-wide, or for one account.");
}
// if (!((account != null && podId == null) ||
// (account == null && podId != null))) {
// throw new InvalidParameterValueException("Direct Attached IP ranges must either be pod-wide, or for one account.");
// }
if (account != null) {
// VLANs for an account must be tagged