Guest

Preview Tool

Cisco Bug: CSCuq73746 - Validations are not proper in 'File name' text box in Collect Logs.

Last Modified

Sep 23, 2014

Products (2)

  • Cisco Prime Collaboration
  • Cisco Prime Collaboration 10.6

Known Affected Releases

10.6

Description (partial)

Symptom:
Validations are not proper in 'File name' text box in Collect Logs.

Conditions:
Steps:

Actual Behavior:
1.	Navigate to Operate --> LCC
2.	Select a device from devices table, and click on collect logs button.
3.	Collect logs window will open and  don't give any file name leave the text field blank, and click on  run, we will get an error message which says ?Please enter file name?, which is fine.
4.	Now give some file name in the text box, let's say file name 'a' and click on run button, we will get an error message which says ?File should only be in .Zip format?, which is also fine.
5.	Now type only 'zip' in text box and click on run button. So no validation happen at this point as we didn't give any '.zip' file name, and log collection job is processing and collecting log file. And when job is complete, we are not able to open the file as it is not in any format or not in proper zip format, as we didn't give '.Zip'

Expected Behavior:
1.	Navigate to Operate --> LCC
2.	Select a device from devices table, and click on collect logs button.
3.	Collect logs window will open and  don't give any file name leave the text field blank, and click on  run, we will get an error message which says ?Please enter file name?, which is fine.
4.	Now give some file name in the text box, let's say file name 'a' and click on run button, we will get an error message which says ?File should only be in .Zip format?, which is also fine.
5.	Now type only 'zip' in text box and click on run button.  At this point validation should happen for .Zip and we should get some error message as we got in step 4. And once proper  file extension is given then only we should be able to proceed for log collection after clicking run. And as the proper file extension is not given, log collection job should not start and log collection should not happen.
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.