You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating allocations for a server if you add the allocation, then make as primary, and remove the previous allocation, seems to keep the previous allocation_id in the server. And an inconsistent state is shown in the UI (showing the previous allocation rather than the new one).
Expected Behavior
Allocations should have an easier form of updating within the UI + keep database state consistent to user actions.
Steps to Reproduce
Have a server with an allocation (alloc A)
Create a new allocation (aloc B)
Assign the new allocation to the server (B)
Make allocation primary
Verify UI result vs database stored allocation.
Panel Version
Version: 1.0.0-beta17
Wings Version
1.0.0-beta9 (Latest: 1.0.0-beta9)
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
I have searched the existing issues before opening this issue.
I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
The text was updated successfully, but these errors were encountered:
Current Behavior
When updating allocations for a server if you add the allocation, then make as primary, and remove the previous allocation, seems to keep the previous
allocation_id
in the server. And an inconsistent state is shown in the UI (showing the previous allocation rather than the new one).Expected Behavior
Allocations should have an easier form of updating within the UI + keep database state consistent to user actions.
Steps to Reproduce
Panel Version
Version: 1.0.0-beta17
Wings Version
1.0.0-beta9 (Latest: 1.0.0-beta9)
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: