Project

General

Profile

Bug #46997

Fix lazy import to avoid double logging config

Added by Bug Clerk about 2 years ago. Updated almost 2 years ago.

Status:
Done
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Seen in:
Severity:
Low Medium
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

PR: https://github.com/freenas/freenas/pull/1803

freenasOS init will configure logging on its own if no handlers are
found. Lazy importing it will avoid that issue since at that point
middlewared logging will be configured already.

Associated revisions

Revision 15fe1554 (diff)
Added by William Grzybowski about 2 years ago

fix(middlewared): lazy import freenasOS to avoid double logging config freenasOS init will configure logging on its own if no handlers are found. Lazy importing it will avoid that issue since at that point middlewared logging will be configured already. Ticket: #46997

Revision 5cf01afd (diff)
Added by William Grzybowski about 2 years ago

fix(middlewared): lazy import freenasOS to avoid double logging config freenasOS init will configure logging on its own if no handlers are found. Lazy importing it will avoid that issue since at that point middlewared logging will be configured already. Ticket: #46997

History

#1 Updated by William Grzybowski about 2 years ago

  • Status changed from Unscreened to In Progress
  • Target version changed from Backlog to 11.2-RC1
  • Severity changed from New to Low Medium

#2 Updated by Bug Clerk about 2 years ago

  • Status changed from In Progress to Ready for Testing

#3 Updated by Dru Lavigne about 2 years ago

  • Subject changed from fix(middlewared): lazy import freenasOS to avoid double logging config to Fix lazy import to avoid double logging config
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#4 Updated by William Grzybowski almost 2 years ago

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

There isnt a feasible way for QA to test this.

Also available in: Atom PDF