Guest

Preview Tool

Cisco Bug: CSCun28613 - Unable to delete Virtual Domain (sometimes) in PI 2.0

Last Modified

Feb 25, 2014

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

2.0(0.0.294)

Description (partial)

Symptom:
- Created a new virtual domain "only-tsim"
- Added primary controller to the virtual domain
- Tried to add a bunch of APs generated through TSIM.
- This operation took a long time (>30 mins and still not added fully).
- Associated a user to this VD (tsim)
- Logged out and logged in as the new user "tsim"
- Some APs were not getting displayed, so went back to check virtual domain config logging in as root.
- Realized that not all APs were added. Since it takes a long time, decided to delete the VD and start from scratch.
- Disassociated the APs and controllers from VD, removed the user from this VD, and tried deleting the VD.
- No errors were shown, but the VD did not get deleted as well.

Later, when this issue was shown to the DEs (dvsreddy), he changed the "Administration --> Logging" level to Informational. Then when we tried to delete the VD, it was working fine. Not sure why. After this, I tried about 2 times to recreate the problem with no luck. This is a tracking bug for this problem. Please feel free to move it to U for now, I will update it if I run into this problem again.

Conditions:
- Created a new virtual domain "only-tsim"
- Added primary controller to the virtual domain
- Tried to add a bunch of APs generated through TSIM.
- This operation took a long time (>30 mins and still not added fully).
- Associated a user to this VD (tsim)
- Logged out and logged in as the new user "tsim"
- Some APs were not getting displayed, so went back to check virtual domain config logging in as root.
- Realized that not all APs were added. Since it takes a long time, decided to delete the VD and start from scratch.
- Disassociated the APs and controllers from VD, removed the user from this VD, and tried deleting the VD.
- No errors were shown, but the VD did not get deleted as well.

Later, when this issue was shown to the DEs (dvsreddy), he changed the "Administration --> Logging" level to Informational. Then when we tried to delete the VD, it was working fine. Not sure why. After this, I tried about 2 times to recreate the problem with no luck. This is a tracking bug for this problem. Please feel free to move it to U for now, I will update it if I run into this problem again.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.