Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Virtual grains are not properly detected on Nutanix AHV #67180

Open
1 of 9 tasks
meaksh opened this issue Jan 20, 2025 · 0 comments · May be fixed by #67181
Open
1 of 9 tasks

[BUG] Virtual grains are not properly detected on Nutanix AHV #67180

meaksh opened this issue Jan 20, 2025 · 0 comments · May be fixed by #67181
Labels
Bug broken, incorrect, or confusing behavior needs-triage

Comments

@meaksh
Copy link
Contributor

meaksh commented Jan 20, 2025

Description
The virtual grains are not correctly detected on VMs running on Nutanix AHV:

# salt-call grains.items
[...]
virtual:
    physical

Setup
(Please provide relevant configs and/or SLS files (be sure to remove sensitive info. There is no general set-up of Salt.)

Please be as specific as possible and give set-up details.

  • on-prem machine
  • VM (Nutanix AHV)
  • VM running on a cloud service, please be explicit and add details
  • container (Kubernetes, Docker, containerd, etc. please specify)
  • or a combination, please be explicit
  • jails if it is FreeBSD
  • classic packaging
  • onedir packaging
  • used bootstrap to install

Steps to Reproduce the behavior
Execute:

# salt-call grains.items
[...]
virtual:
    physical

Expected behavior
A clear and concise description of what you expected to happen.

# salt-call grains.items
[...]
virtual:
    kvm
virtual_subtype:
    Nutanix AHV

Screenshots
N/A

Versions Report

salt --versions-report (Provided by running salt --versions-report. Please also mention any differences in master/minion versions.)
PASTE HERE

Additional context
Add any other context about the problem here.

@meaksh meaksh added Bug broken, incorrect, or confusing behavior needs-triage labels Jan 20, 2025
@meaksh meaksh linked a pull request Jan 20, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior needs-triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant