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

Pterodactyl: Service fields may get duplicated

    Details

    • Type: Bug
    • Status: In Review
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.12.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      When provisioning a server using the Pterodactyl module, under some circumstances service fields may get duplicated, throwing a duplicated key error from the database.

        Activity

        abdy Abdy Franco created issue -
        abdy Abdy Franco made changes -
        Field Original Value New Value
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 2 hours, 12 minutes [ 7920 ]
        Worklog Id 17698 [ 17698 ]
        abdy Abdy Franco made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        abdy Abdy Franco made changes -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        abdy Abdy Franco made changes -
        Time Spent 2 hours, 12 minutes [ 7920 ] 2 hours, 28 minutes [ 8880 ]
        Worklog Id 17701 [ 17701 ]
        abdy Abdy Franco made changes -
        Time Spent 2 hours, 28 minutes [ 8880 ] 3 hours, 18 minutes [ 11880 ]
        Worklog Id 17702 [ 17702 ]
        admin Paul Phillips made changes -
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.12.0 Sprint 5 [ 215 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked lower
        jonathan Jonathan Reissmueller made changes -
        Fix Version/s 5.12.0-b1 [ 12000 ]
        jonathan Jonathan Reissmueller made changes -
        Sprint 5.12.0 Sprint 5 [ 215 ] 5.12.0 Sprint 5, 5.13.0 Sprint 1 [ 215, 216 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked higher

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            abdy Abdy Franco
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

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

                Agile