Project

General

Profile

Bug #55887

Remove cachetool.py from freenas-debug

Added by Caleb St. John 9 months ago. Updated 8 months ago.

Status:
Done
Priority:
No priority
Assignee:
Caleb St. John
Category:
Middleware
Target version:
Seen in:
TrueNAS - TrueNAS-11.1-U6.1
Severity:
Low
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

After conversation with Andrew, there is no real good reason to run cachetool.py dump when capturing a freenas-debug.

This specific script can take 10's of minutes or longer to produce output depending on the size of the AD/LDAP environment.

The output we gather in the other sections provide more than enough data.


Related issues

Copied to FreeNAS - Bug #60408: Remove cachetool.py from freenas-debugDone

History

#1 Updated by Caleb St. John 9 months ago

  • Status changed from Screened to In Progress

#2 Updated by Caleb St. John 9 months ago

PR's approved and merged.

Test case:

1. run freenas-debug from webUI
2. verify that there is no "cache" directory

#3 Updated by Caleb St. John 9 months ago

  • Status changed from In Progress to Ready for Testing

#4 Updated by Dru Lavigne 9 months ago

This will also appear in the U7 Release Notes.

#5 Updated by Dru Lavigne 9 months ago

  • Subject changed from remove cachetool.py from freenas-debug to Remove cachetool.py from freenas-debug
  • Target version changed from TrueNAS 11.1-U6.2 to 11.2-RC2
  • Needs Merging changed from Yes to No

#6 Updated by Bonnie Follweiler 8 months ago

  • Status changed from Ready for Testing to Passed Testing
  • Needs QA changed from Yes to No

Test Passed in FreeNAS-11.2-INTERNAL39

#7 Updated by Dru Lavigne 8 months ago

  • Status changed from Passed Testing to Done

#8 Updated by Dru Lavigne 8 months ago

  • Copied to Bug #60408: Remove cachetool.py from freenas-debug added

Also available in: Atom PDF