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
What Operating System(s) are you seeing this problem on?
Linux (x86-64)
Backend.AI version
24.09.2rc1
Describe the bug
Issue Summary
Inconsistency in accelerator information between session launcher and resource monitor can cause user confusion.
Description
The session launcher uses the /func/config/resource-slots/details?sgroup=multinode API, which only shows detailed information for the supported resources in the group. As a result, if an accelerator is not supported, it is not included in the response.
On the other hand, the resource monitor uses the Check-preset API, which includes accelerators in the response even if they are not supported by the resource group, as long as they have been reported to the manager at least once. In such cases, the total value is set to 0 to indicate that the accelerator is not supported.
What Operating System(s) are you seeing this problem on?
Linux (x86-64)
Backend.AI version
24.09.2rc1
Describe the bug
Issue Summary
Inconsistency in accelerator information between session launcher and resource monitor can cause user confusion.
Description
The session launcher uses the
/func/config/resource-slots/details?sgroup=multinode
API, which only shows detailed information for the supported resources in the group. As a result, if an accelerator is not supported, it is not included in the response.On the other hand, the resource monitor uses the Check-preset API, which includes accelerators in the response even if they are not supported by the resource group, as long as they have been reported to the manager at least once. In such cases, the total value is set to 0 to indicate that the accelerator is not supported.
This inconsistency can lead to user confusion.
Additional Information
To Reproduce
You can reproduce it in the Multinode resource group in dogbowl.
Expected Behavior
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: