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

Multicraft: IP not updated when daemon is changed

        Details

        • Type: Bug
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 4.7.0
        • Component/s: None
        • Labels:
          None

          Description

          The Multicraft module changes the daemon with a subsequent API request when a service is created, but Multicraft does not appear to adhere to it by updating the IP:Port to the new daemon as well. However, it used to do this in the past when we integrated CORE-1602.

          We should determine whether we can have Multicraft update the IP:Port when the daemon is changed. If the solution is to consolidate API requests into a single request, this is better done in CORE-1603.

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. CORE-1602 Multicraft: Notify Multicraft that it should reselect the IP:Port

            • Major - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. CORE-1603 Multicraft: Improve service creation to limit API calls

            • Major - Major loss of function.
            • Open

            Bug - A problem which impairs or prevents the functions of the product. CORE-3279 Multicraft: IP not updated when daemon is changed from a config option

            • Major - Major loss of function.
            • Closed

              Activity

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    12/Sep/19

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 4 hours, 54 minutes
                    4h 54m

                      Agile