Fixed
Details
Assignee
Antonio RussoAntonio RussoReporter
Jesse WhiteJesse WhiteSprint
NoneFix versions
Affects versions
Priority
Major
Details
Details
Assignee
Antonio Russo
Antonio RussoReporter
Jesse White
Jesse WhiteSprint
None
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created July 11, 2018 at 1:58 PM
Updated July 12, 2018 at 1:44 PM
Resolved July 12, 2018 at 1:44 PM
On a system running 23.0.0-SNAPSHOT, I found the following messages in output.log:
bft:nodeid:[539], bridgeport:[68], ifindex:[68], vlan:[null] macs:[00c0] bft:nodeid:[539], bridgeport:[7], ifindex:[7], vlan:[null] macs:[b41] bft:nodeid:[539], bridgeport:[9], ifindex:[9], vlan:[null] macs:[00e] bft:nodeid:[539], bridgeport:[14], ifindex:[14], vlan:[null] macs:[00c] bft:nodeid:[539], bridgeport:[22], ifindex:[22], vlan:[null] macs:[b41] bft:nodeid:[539], bridgeport:[23], ifindex:[23], vlan:[null] macs:[00c] bft:nodeid:[539], bridgeport:[55], ifindex:[55], vlan:[null] macs:[00c] bft:nodeid:[539], bridgeport:[24], ifindex:[24], vlan:[null] macs:[1cdf] bft:nodeid:[539], bridgeport:[56], ifindex:[56], vlan:[null] macs:[00c] bft:nodeid:[539], bridgeport:[57], ifindex:[57], vlan:[null] macs:[00c0]
These messages should be removed or logged via a logger rather than using stdout/stderr.