Inconsistency in accelerator information between session launcher and resource monitor
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 358
Description
### 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
- [Teams](https://teams.microsoft.com/l/message/19:14c484402d874dafb15806d093b95a82@thread.skype/1733124317299?tenantId=13c6a44d-9b52-4b9e-aa34-0513ee7131f2&groupId=74ae2c4d-ec4d-4fdf-b2c2-f5041d1e8631&parentMessageId=1733106308378&teamName=devops&channelName=Frontend&createdTime=1733124317299)
### To Reproduce
You can reproduce it in the Multinode resource group in dogbowl.
### Expected Behavior
_No response_
### Anything else?
_No response_
JIRA Issue: BA-28
Contributor guide
Assessment
This issue has not been assessed yet.