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

Update failed service changes to include errors in cron log

        Details

        • Type: Improvement
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: None
        • Fix Version/s: Short Term
        • Component/s: None
        • Labels:
          None

          Description

          When a service change is provisioned via cron, it can fail for various reasons (e.g. unable to process the change, the service is no longer valid, the input data is no longer valid, etc.). The cron task only logs the result (i.e. status) of the service change, but does not say why it failed. It would be useful if ServiceChanges::process set the Input errors on failure for the log as well

            Activity

            Ascending order - Click to sort in descending order
            tyson Tyson Phillips (Inactive) created issue -
            tyson Tyson Phillips (Inactive) made changes -
            Field Original Value New Value
            Story Points 2
            tyson Tyson Phillips (Inactive) made changes -
            Rank Ranked higher

              People

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

                Dates

                • Created:
                  Updated: