Ticket 6795 - Change the loglevel for federation siblings not synced yet
Summary: Change the loglevel for federation siblings not synced yet
Status: RESOLVED FIXED
Alias: None
Product: Slurm
Classification: Unclassified
Component: Scheduling (show other tickets)
Version: 19.05.x
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Alejandro Sanchez
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2019-04-02 16:12 MDT by Jason Booth
Modified: 2019-04-05 03:28 MDT (History)
1 user (show)

See Also:
Site: NOAA
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ORNL
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed: 18.08.7 19.05.0pre4
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Jason Booth 2019-04-02 16:12:41 MDT 
[2019-03-31T19:05:24.891] debug:  sched: schedule() returning, federation siblings not synced yet

Since the production loglevel recommendation is (IIRC) info, most users would never see this.  Please consider moving the debug() statements to a more serious loglevel.
Comment 2 Alejandro Sanchez 2019-04-05 03:28:31 MDT 
Matt, this has been changed in

commit 46ef8ff7a3598c5b81af26185f3b201c37c6b6e1 (HEAD -> slurm-18.08, origin/slurm-18.08)
Author:     Alejandro Sanchez <alex@schedmd.com>
AuthorDate: Fri Apr 5 11:26:39 2019 +0200
Commit:     Alejandro Sanchez <alex@schedmd.com>
CommitDate: Fri Apr 5 11:26:39 2019 +0200

    Promote federation unsynced siblings log message from debug to info.
    
    Bug 6791.