Incorrect Alert reporting
Description
created
duplicates
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity
Basil Hendroff June 25, 2021 at 4:35 AM
Cheers!
Ken Moore June 24, 2021 at 5:35 PM
: I created a separate ticket () specifically for tracking down the SMR disk info "de-sync" so it does not get lost in a comment thread. Feel free to follow up on that ticket with more information, but we are still looking into this at the present time.
Basil Hendroff June 24, 2021 at 9:15 AM(edited)
TC 2 nightly 20210623 - Issue still present.
It's curious that TC still has a memory of the disks that were replaced.
Basil Hendroff June 22, 2021 at 6:12 PM(edited)
On the two servers where SMR disks were replaced, this is what I did. From TC, I reconnected each server to generate the SMR alert. Even after the SMR disks were replaced, I still get the messages you see in image tc73.
On server truenas-b1, TC still thinks ada4 is an SMR drive. The SMR drive that was replaced was a model WD60EFAX.
On server truenas-l2, TC still thinks that ada2 and ada3 are SMR drives. The SMR drives that were replaced were (smaller) model WD60EFAX.
Ken Moore June 22, 2021 at 3:40 PM
Could you please double--check the model numbers on the disks that it flagged?
The SMR model regexes that we are using are:
None of those should match your WD60EFZX disk.
In particular, you can run this command from the CLI on the NAS to return only the disk ID and model numbers that TC is getting:
Details
Details
Assignee
Ken MooreReporter
Basil HendroffComponents
Fix versions
Affects versions
Priority
LowestMore fields
Time tracking
More fields
Time trackingKatalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
More info in this forum post https://www.truenas.com/community/threads/truecommand-2-0-issues.93712/post-648490
Having deleted all alerts in TC 1.3.2 and TC 2.0, TC 1.3.2 refreshes alerts quickly. Drilling down into a particular system on TC 1.3.2 shows there are three alerts with one of the alerts indicating there is an SMR drive present.
On the other hand, for the same system, TC 2.0 (after waiting what seems like hours for the counters to clear) incorrectly reports there are four alerts. The Alerts tile is empty.
Linked to JIRA ticket .
EDIT: After 24 hours the system tile counter is at 20 and now matches the number of recorded alerts. The majority of alerts seem to have been triggered from the Storage Pool Expansion Soon alert rule. The SMR disk still hasn't been redetected so it appears the SMR Disk Detection alert rule hasn't run.
EDIT 2: After 48 hours, the SMR Disk Detection alert rule still hasn't kicked in.
The SMR alert kicked in overnight.