PowerScale: SyncIQ shows state of 'Needs Attention'
Summary: This KB article explains the reasons a SyncIQ policy may display a 'Needs Attention' state and provides steps to identify and resolve the issue.
Instructions
When a SyncIQ policy fails, a report is logged with the reason for the failure. Once the failed job completes successfully, the state of the SyncIQ policy shows as needs_attention state:
SIQ1-1# isi sync reports list
Policy Name Job ID Start Time End Time Action State
--------------------------------------------------------------------------------------------------------
Sync_Test1 2 2022-12-15T19:37:50 2022-12-15T19:39:54 run finished
Sync_Test3 2 2022-12-15T19:29:50 2022-12-15T19:31:39 run finished
Sync_Test2 1 2022-12-15T19:04:22 2022-12-15T19:06:20 run finished
test 1 2022-12-12T17:07:56 2022-12-12T17:12:53 run needs_attention
--------------------------------------------------------------------------------------------------------
Total: 4
This is expected behavior. The needs_attention status indicates that a previous job failed and may require review and investigation.
To determine the cause of the failure, identify the job ID in the needs_attention state by reviewing the affected policy reports.
In this example below the SyncIQ policy test shows Job ID 1 as state=needs_attention.
SIQ1-1# isi sync reports list --policy-name=test --state=needs_attention
Policy Name Job ID Start Time End Time Action State
-----------------------------------------------------------------------------------------------------------
test 1 2022-12-12T17:07:56 2022-12-12T17:12:53 run needs_attention
-----------------------------------------------------------------------------------------------------------
Total: 1
Once the Job ID has been identified, view the report to find the sub-reports logged under the main Job ID which is listed at the end of the output.
SIQ1-1# isi sync reports view --policy=test --job-id=1
Policy Name: test
Job ID: 1
Start Time: 2022-12-12T17:07:56
End Time: 2022-12-12T17:12:53
Action: run
State: needs_attention
ID: 1-test
Policy ID: f3b3c720a82ecc7ac700d6ad0f0de923
Sync Type: initial
Duration: 17s
Errors: (policy name: test target: 10.237.0.122) SyncIQ policy failed to establish an encrypted connection with target. Attempting to run an unencrypted sync while the global required flag is set., (policy name: test target: 10.237.0.122) SyncIQ detected a problem with policy configuration. Job has no valid root path: No such file or directory
Encrypted: No
Phases
Phase: STF_PHASE_TW
Start Time: 2022-12-12T17:12:41
End Time: 2022-12-12T17:12:48
Subreports:
Policy Name Job ID Subreport ID Start Time End Time Action State
------------------------------------------------------------------------------------------------------------------------
test 1 1 2022-12-12T17:07:56 2022-12-12T17:07:57 run failed
test 1 2 2022-12-12T17:09:28 2022-12-12T17:09:29 run failed
test 1 3 2022-12-12T17:12:38 2022-12-12T17:12:53 run finished
------------------------------------------------------------------------------------------------------------------------
Total: 3
Each sub-report has a start time and end time, including the sub-report where the job could complete successfully.
Once the list of sub-reports for the failing job is available, specify the sub-report to view to identify the reason for failure.
Example:
SIQ1-1# isi sync reports subreports view --policy=test --job-id=1 --subreport-id=1
Policy Name: test
Job ID: 1
Subreport ID: 1
Start Time: 2022-12-12T17:07:56
End Time: 2022-12-12T17:07:57
Action: run
State: failed
Policy ID: f3b3c720a82ecc7ac700d6ad0f0de923
Sync Type: invalid
Duration: 1s
Errors: (policy name: test target: 10.237.0.122) SyncIQ detected a problem with policy configuration. Job has no valid root path: No such file or directory
SIQ1-1# isi sync reports subreports view --policy=test --job-id=1 --subreport-id=2
Policy Name: test
Job ID: 1
Subreport ID: 2
Start Time: 2022-12-12T17:09:28
End Time: 2022-12-12T17:09:29
Action: run
State: failed
Policy ID: f3b3c720a82ecc7ac700d6ad0f0de923
Sync Type: invalid
Duration: 1s
Errors: (policy name: test target: 10.237.0.122) SyncIQ policy failed to establish an encrypted connection with target. Attempting to run an unencrypted sync while the global required flag is set.
If the original issue has been resolved but the SyncIQ job continues to fail, each sub-report will contain different reasons for the failure. It is recommended to view the latest sub-report for the recent failure prior to success.
When the SyncIQ policy runs again and completes without any failures, the status changes from needs_attention to Finished. If failures persist, they should be investigated to determine the appropriate corrective action.