-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Labels
Description
Bug description
When choosing Technology as Group By
my list is showing VM & Containers.
All my setup is pure VM except 2 nodes that is bare metal.
So some filtering is off here.
most of my nodes are vmware
as type and some bare metal
Expected behavior
Listed as "Bare metal" and "VM".
Steps to reproduce
- just group buy.
Screenshots
Error Logs
No response
Desktop
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Browser Version [e.g. 22]
Additional context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
hugovalente-pm commentedon Feb 8, 2024
thanks for the report @zyxep one important detail that you showed us was that if you clicked on the nodes and opened the Node Inspector (right-hand bar that opens) you would see the correct values of Bare metal and VM under `Type:´

zyxep commentedon Feb 8, 2024
yup, that is correct.
hugovalente-pm commentedon Apr 12, 2024
@zyxep this should be fixed, can you confirm from your end?
zyxep commentedon Apr 19, 2024
Yes, @hugovalente-pm the type is now correct.
Though, VM vs. Container seems still weird to me :)
hugovalente-pm commentedon Apr 19, 2024
could this be some containers running on you VM and where Nedata is deployed? we calculate this field based on some attribute the agent collects from the environment it is running
zyxep commentedon Apr 19, 2024
nope, there are only ~20 ish vm's running docker.
the rest are just regular VM's
hugovalente-pm commentedon Apr 23, 2024
adding some examples that were shared that show some issues:
Examples:
VM
but is aBare Metal
- FE shows as VM but correctly identified on Node info, attribute"technology": "VM"
"technology": "VM"
"technology": "Container"
"technology": "Container"
1. node, listed as `VM` but is a `Bare Metal`
2. VM within VMware
3. VM in Vmware, running ubuntu with Docker on
4. VM, ubuntu. running OpenSearch