Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-901

Add service action backoff after failure

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Sponsored
    • Component/s: None
    • Labels:
      None

      Description

      If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure (This doesn't happen, there is no such email to staff).

      So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again. (Question: Where should this setting go?)

      Allow time intervals for waiting to attempt the action again:
      15 min, 30 min, 1 hour, ... 24 hours

      Edit: 2019/01/04

      In addition to this backoff feature, we should add:

      • A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
      • A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt. (Or maybe a new tab under Tools > Logs called "Service Action")
      • A setting for the maximum number of retries before it's no longer attempted.

        Issue Links

          Activity

          tyson Tyson Phillips (Inactive) created issue -
          admin Paul Phillips made changes -
          Field Original Value New Value
          Fix Version/s 3.3.0 [ 10100 ]
          Fix Version/s 3.2.0 [ 10002 ]
          admin Paul Phillips made changes -
          Security Private [ 10000 ]
          admin Paul Phillips made changes -
          Fix Version/s 3.4.0 [ 10400 ]
          Fix Version/s 3.3.0 [ 10100 ]
          admin Paul Phillips made changes -
          Fix Version/s 3.4.0 [ 10400 ]
          admin Paul Phillips made changes -
          Fix Version/s Sponsored [ 11113 ]
          admin Paul Phillips made changes -
          Description If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours
          If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backup feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          admin Paul Phillips made changes -
          Description If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backup feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backup feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          * A setting for the maximum number of retries before it's no longer attempted.
          admin Paul Phillips made changes -
          Description If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backup feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          * A setting for the maximum number of retries before it's no longer attempted.
          If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backoff feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          * A setting for the maximum number of retries before it's no longer attempted.
          admin Paul Phillips made changes -
          Description If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and would send an email to staff each time regarding the failure.

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again.

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backoff feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt.
          * A setting for the maximum number of retries before it's no longer attempted.
          If a service fails to provision, suspend, unsuspend, or cancel, it may be attempted as often as every 5 minutes, and -would send an email to staff each time regarding the failure- (This doesn't happen, there is no such email to staff).

          So we propose to create a setting that sets a service action backoff on failure, and sets a time interval for which not to attempt the action again. (*Question: Where should this setting go?*)

          Allow time intervals for waiting to attempt the action again:
          15 min, 30 min, 1 hour, ... 24 hours

          Edit: 2019/01/04

          In addition to this backoff feature, we should add:

          * A new email subscription notice under My Info for staff (including ACL to enable the option) that will email staff on a failure
          * A new page under Tools that lists services that have failed to provision, suspend, unsuspend, cancel, or module renew at least once and information about the service, when it will next be attempted, with an option to clear any delay so the next cron will re-attempt. (Or maybe a new tab under Tools > Logs called "Service Action")
          * A setting for the maximum number of retries before it's no longer attempted.
          tyson Tyson Phillips (Inactive) made changes -
          Issue Type Task [ 3 ] New Feature [ 2 ]
          tyson Tyson Phillips (Inactive) made changes -
          Story Points 8
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          admin Paul Phillips made changes -
          Assignee Cody Phillips [ cody ]
          jonathan Jonathan Reissmueller made changes -
          Link This issue relates to CORE-3274 [ CORE-3274 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          admin Paul Phillips made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Won't Fix [ 2 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              tyson Tyson Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: