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

Stop Service Provision Attempts After x Failures

    Details

    • Type: New Feature
    • Status: In Review
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Sponsored, 5.11.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

      A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing

      • Never
      • 1
      • 2
      • ...
      • 30

      In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

      In addition, a new email template service_provision_halted should be created with the name Service Provisioning Halted and the subject Automatic Provisioning Halted for Service -

      {service.name}

      This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

      For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

        Issue Links

          Activity

          jonathan Jonathan Reissmueller created issue -
          Hide
          jonathan Jonathan Reissmueller added a comment -

          We also may want to do this sort of thing for suspension/unsuspension/cancellation and not just for service creation

          Show
          jonathan Jonathan Reissmueller added a comment - We also may want to do this sort of thing for suspension/unsuspension/cancellation and not just for service creation
          jonathan Jonathan Reissmueller made changes -
          Field Original Value New Value
          Link This issue relates to CORE-901 [ CORE-901 ]
          Hide
          jonathan Jonathan Reissmueller added a comment -

          If we do this task it would make at least part of CORE-901 unnecessary

          Show
          jonathan Jonathan Reissmueller added a comment - If we do this task it would make at least part of CORE-901 unnecessary
          jonathan Jonathan Reissmueller made changes -
          Story Points 5
          jonathan Jonathan Reissmueller made changes -
          Fix Version/s Sponsored [ 11113 ]
          Fix Version/s 4.7.1 [ 11126 ]
          jonathan Jonathan Reissmueller made changes -
          Description Sometimes services fail to provision, and will continue to do so until something is changed manually. To prevent attempts to provision these every 5 minutes until forever, we should add a setting "Stop Automatic Provisions After Attempts" or some such thing. Then we add a drop down of how many attempts to make before suspending automatic provisions for a service. Probably 1-30 or no limit.

          In order to do this we will either need to create a new log table or adapt the current log_services table to support service provision failures.

          We also need to make sure that users know that provisioning has been suspended. Maybe an email to the admin? Another log page? A notice message on the user profile?
          Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

          A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
          * Never
          * 1
          * 2
          * ...
          * 30

          In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

          In addition, a new email template service_provision_halted should be created with the name "Service Provisioning Halted" and the subject "Automatic Provisioning Halted for Service - {service.name}". This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

          For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

          jonathan Jonathan Reissmueller made changes -
          Description Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

          A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
          * Never
          * 1
          * 2
          * ...
          * 30

          In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

          In addition, a new email template service_provision_halted should be created with the name "Service Provisioning Halted" and the subject "Automatic Provisioning Halted for Service - {service.name}". This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

          For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

          Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

          A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
          * Never
          * 1
          * 2
          * ...
          * 30

          In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

          In addition, a new email template service_provision_halted should be created with the name Service Provisioning Halted and the subject Automatic Provisioning Halted for Service - {service.name}. This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

          For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

          jonathan Jonathan Reissmueller made changes -
          Description Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

          A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
          * Never
          * 1
          * 2
          * ...
          * 30

          In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

          In addition, a new email template service_provision_halted should be created with the name Service Provisioning Halted and the subject Automatic Provisioning Halted for Service - {service.name}. This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

          For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

          Currently services that fail provisioning may continue to attempt provisioning every time the cron runs, indefinitely.

          A setting should be added "Halt Automatic Provision After Attempts" which will stop provision attempts on a service after X attempts have failed. The setting should be a drop down containing
          * Never
          * 1
          * 2
          * ...
          * 30

          In order to track number of failed attempts we should add a new status to the log_services table called provision_failed. Make sure that adding this status does not mess up any of the current suspension/unsuspension behavior that depends on this log.

          In addition, a new email template service_provision_halted should be created with the name Service Provisioning Halted and the subject Automatic Provisioning Halted for Service - {service.name}
          This email should be sent to subscribed admins when provisioning is halted on a service. This email should appear under the "Email Subscription Notices" section on the My Info and Staff Group pages.

          For additional visibility, we may want to add a note to the clients dashboard, similar the the due invoices notice, that tells them which services, if any, have halted provisioning.

          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked lower
          Hide
          jonathan Jonathan Reissmueller added a comment -

          Instead of using log_services we should generalize service_invoices

          Show
          jonathan Jonathan Reissmueller added a comment - Instead of using log_services we should generalize service_invoices
          Hide
          admin Paul Phillips added a comment -

          This task will work similar to the service renewal queue. We'll rename Tools > Renewal Queue, so that it works for both new and renewing services, and we will show whether it's a new or renewing service in the queue.

          Show
          admin Paul Phillips added a comment - This task will work similar to the service renewal queue. We'll rename Tools > Renewal Queue, so that it works for both new and renewing services, and we will show whether it's a new or renewing service in the queue.
          admin Paul Phillips made changes -
          Fix Version/s 5.11.0-b1 [ 11908 ]
          admin Paul Phillips made changes -
          Rank Ranked higher
          admin Paul Phillips made changes -
          Rank Ranked lower
          jonathan Jonathan Reissmueller made changes -
          Sprint 5.11.0 Sprint 2 [ 196 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked lower
          jonathan Jonathan Reissmueller made changes -
          Assignee Jonathan Reissmueller [ jonathan ]
          jonathan Jonathan Reissmueller made changes -
          Sprint 5.11.0 Sprint 2 [ 196 ] 5.11.0 Sprint 3 [ 202 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked lower
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          abdy Abdy Franco made changes -
          Assignee Abdy Franco [ abdy ]
          abdy Abdy Franco made changes -
          Remaining Estimate 5 minutes [ 300 ] 0 minutes [ 0 ]
          Time Spent 4 hours, 3 minutes [ 14580 ]
          Worklog Id 17361 [ 17361 ]
          abdy Abdy Franco made changes -
          Time Spent 4 hours, 3 minutes [ 14580 ] 1 day, 3 hours, 56 minutes [ 42960 ]
          Worklog Id 17362 [ 17362 ]
          abdy Abdy Franco made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          abdy Abdy Franco made changes -
          Time Spent 1 day, 3 hours, 56 minutes [ 42960 ] 2 days, 3 hours, 40 minutes [ 70800 ]
          Worklog Id 17363 [ 17363 ]
          abdy Abdy Franco made changes -
          Time Spent 2 days, 3 hours, 40 minutes [ 70800 ] 3 days, 3 hours, 42 minutes [ 99720 ]
          Worklog Id 17364 [ 17364 ]
          abdy Abdy Franco made changes -
          Time Spent 3 days, 3 hours, 42 minutes [ 99720 ] 3 days, 5 hours, 40 minutes [ 106800 ]
          Worklog Id 17366 [ 17366 ]
          abdy Abdy Franco made changes -
          Time Spent 3 days, 5 hours, 40 minutes [ 106800 ] 4 days, 5 hours, 38 minutes [ 135480 ]
          Worklog Id 17374 [ 17374 ]
          abdy Abdy Franco made changes -
          Time Spent 4 days, 5 hours, 38 minutes [ 135480 ] 1 week, 5 hours, 42 minutes [ 164520 ]
          Worklog Id 17375 [ 17375 ]
          abdy Abdy Franco made changes -
          Time Spent 1 week, 5 hours, 42 minutes [ 164520 ] 1 week, 1 day, 5 hours, 44 minutes [ 193440 ]
          Worklog Id 17376 [ 17376 ]
          abdy Abdy Franco made changes -
          Time Spent 1 week, 1 day, 5 hours, 44 minutes [ 193440 ] 1 week, 2 days, 5 hours, 41 minutes [ 222060 ]
          Worklog Id 17377 [ 17377 ]
          abdy Abdy Franco made changes -
          Time Spent 1 week, 2 days, 5 hours, 41 minutes [ 222060 ] 1 week, 3 days, 5 hours, 42 minutes [ 250920 ]
          Worklog Id 17378 [ 17378 ]
          abdy Abdy Franco made changes -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          jonathan Jonathan Reissmueller made changes -
          Sprint 5.11.0 Sprint 3 [ 202 ] 5.11.0 Sprint 3, 5.11.0 Sprint 4 [ 202, 203 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Sprint 5.11.0 Sprint 3, 5.11.0 Sprint 4 [ 202, 203 ] 5.11.0 Sprint 3, 5.11.0 Sprint 4, 5.11.0 Sprint 5 [ 202, 203, 204 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher

            People

            • Assignee:
              abdy Abdy Franco
              Reporter:
              jonathan Jonathan Reissmueller
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 5 minutes
                5m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 week, 3 days, 5 hours, 42 minutes
                1w 3d 5h 42m

                  Agile