Skip to content

LTE-2878 : Selfheal functions are not running in XLE#261

Open
aj970-crypto wants to merge 3 commits intodevelopfrom
selfheal_cron_change
Open

LTE-2878 : Selfheal functions are not running in XLE#261
aj970-crypto wants to merge 3 commits intodevelopfrom
selfheal_cron_change

Conversation

@aj970-crypto
Copy link
Contributor

LTE-2878 : Selfheal functions are not running in XLE

Reason for change: Selfheal aggressive is not running in XLE and Sky devices, so removed the cron entry of it in those devices
Test Procedure: Check whether selfheal aggressive selfheal entry is removed from crontab in XLE and Sky devices.
Risks: Low
Priority: P0

Signed-off-by: aj970 <akshaya_j@comcast.com>
@aj970-crypto aj970-crypto requested review from a team as code owners March 12, 2026 14:29
Copilot AI review requested due to automatic review settings March 12, 2026 14:29
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the cron initialization script to avoid scheduling the selfheal_aggressive.sh cron job on specific device types where it is reported not to run (XLE/Sky), while keeping the rest of the SelfHeal cron jobs unchanged.

Changes:

  • Adds a BOX_TYPE gate to skip writing the selfheal_aggressive.sh cron entry for selected devices.
  • Keeps existing SelfHeal cron scheduling (e.g., resource_monitor.sh, connectivity test) as-is when SelfHeal cron is enabled.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment on lines +174 to +176
if [ "$BOX_TYPE" != "WNXL11BWL" ] && [ "$BOX_TYPE" != "HUB4" ] && [ "$BOX_TYPE" != "SR213" ]; then
# Monitor selfheal_aggressive.sh based on syscfg value
AGGRESSIVE_INTERVAL=$(syscfg get AggressiveInterval)
Copy link

Copilot AI Mar 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new BOX_TYPE exclusion list for the selfheal_aggressive cron only covers WNXL11BWL, HUB4, and SR213, but this same script treats SR300 and SE501 as Sky devices elsewhere (e.g., the /etc/sky cron additions later in the file). If the intent (per PR description) is to remove the selfheal_aggressive cron entry from all Sky devices, SR300/SE501 likely need to be included in this exclusion list (or the PR description updated to match the narrower scope).

Copilot uses AI. Check for mistakes.
AGGRESSIVE_INTERVAL=$(syscfg get AggressiveInterval)
if [ -z "$AGGRESSIVE_INTERVAL" ]; then
AGGRESSIVE_INTERVAL=5
if [ "$BOX_TYPE" != "WNXL11BWL" ] && [ "$BOX_TYPE" != "HUB4" ] && [ "$BOX_TYPE" != "SR213" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently how it is restricted running aggressive selfheal in these platforms? is it based on box type check ?

Copilot AI review requested due to automatic review settings March 13, 2026 11:28
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment on lines +174 to +181
if [ "$BOX_TYPE" != "WNXL11BWL" ] || [ "$BOX_TYPE" != "HUB4" ] || [ "$BOX_TYPE" != "SR213" ]; then
# Monitor selfheal_aggressive.sh based on syscfg value
AGGRESSIVE_INTERVAL=$(syscfg get AggressiveInterval)
if [ -z "$AGGRESSIVE_INTERVAL" ]; then
AGGRESSIVE_INTERVAL=5
fi
#Write cron rule
echo "*/$AGGRESSIVE_INTERVAL * * * * /usr/ccsp/tad/selfheal_aggressive.sh" >> $CRONTAB_FILE
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants