Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2254694 - VmWare - API doesn't show same info about VM as in UI
Summary: VmWare - API doesn't show same info about VM as in UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.15.0
Assignee: Girija Soni
QA Contact: sganar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-12-15 08:09 UTC by Girija Soni
Modified: 2024-08-22 04:25 UTC (History)
6 users (show)

Fixed In Version: foreman-3.9.1.6-1,rubygem-hammer_cli_foreman-3.9.0.1-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-04-23 17:16:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35248 0 Normal New VmWare - API doesn't show same info about VM as in UI 2023-12-15 08:09:20 UTC
Github theforeman hammer-cli-foreman pull 624 0 None Merged Refs #36991 - Show mac address in VmWare info 2024-01-31 17:45:21 UTC
Red Hat Issue Tracker SAT-21954 0 None None None 2023-12-15 08:13:26 UTC
Red Hat Product Errata RHSA-2024:2010 0 None None None 2024-04-23 17:16:23 UTC

Comment 1 Girija Soni 2023-12-15 08:09:24 UTC
Created from redmine issue https://projects.theforeman.org/issues/35248

Comment 2 Girija Soni 2023-12-15 08:09:26 UTC
Upstream bug assigned to None

Comment 3 Girija Soni 2023-12-15 08:21:27 UTC
Description of problem:

When trying to get a virtual machine's info from hammer or API, mac address is not being displayed. Mac address is only displayed in the UI.


How reproducible:

Always.


Steps to Reproduce:
1. Run hammer compute-resource virtual-machine info --id CR_ID --vm-id WM_VM_ID


Actual results:

Mac address is not being displayed.


Expected results:

Mac address shall be displayed and not be empty.

Comment 4 Girija Soni 2023-12-15 08:21:49 UTC
Description of problem:

When trying to get a virtual machine's info from hammer or API, mac address is not being displayed. Mac address is only displayed in the UI.


How reproducible:

Always.


Steps to Reproduce:
1. Run hammer compute-resource virtual-machine info --id CR_ID --vm-id WM_VM_ID


Actual results:

Mac address is not being displayed.


Expected results:

Mac address shall be displayed and not be empty.

Comment 5 Bryan Kearney 2023-12-18 12:02:58 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/35248 has been resolved.

Comment 6 sganar 2024-01-31 13:41:47 UTC
Failed QA.

Tested on Satellite 6.15.0 Snap 8.0

Steps followed: 
1. Create a VMware compute resource
2. Run hammer compute-resource virtual-machine info --id CR_ID --vm-id VM_ID

Observation:
I don't see any info about Mac Address 
# hammer compute-resource virtual-machine info --id CR_ID --vm-id VM_ID
Id:               503ydaf-67ee-79we-cr65-912r524b9ce67
Name:             joel-olsby.vowryxlkng.foo
CPUs:             1
Memory:           6000
Power Status:     poweredOn
Host Name:        abcd.efgh.foo
Hardware Version: vmx-14
Path:             /Path/..
Operating System: Red Hat Enterprise Linux 8 (64-bit)
Boot order:       network, disk

Additional Info:
Looks like the fix(https://github.com/theforeman/foreman/pull/9957/files) isn't present in the 6.15 snap 8

Comment 11 sganar 2024-02-06 16:42:13 UTC
Verified

Tested on Satellite 6.15.0 Snap 9.0

Steps followed: 
1. Create a VMware compute resource
2. Run hammer compute-resource virtual-machine info --id CR_ID --vm-id VM_ID

Observation:
Mac address is beed displayed now.
# hammer compute-resource virtual-machine info --id CR_ID --vm-id VM_ID
Id:               503ydaf-67ee-79we-cr65-912r524b9ce67
Name:             joel-olsby.vowryxlkng.foo
CPUs:             1
Memory:           6000
Power Status:     poweredOn
Host Name:        abcd.efgh.foo
Hardware Version: vmx-14
Path:             /Path/..
Operating System: Red Hat Enterprise Linux 8 (64-bit)
Mac:              00:2j:19:35:c9:45
Boot order:       network, disk

Comment 14 errata-xmlrpc 2024-04-23 17:16:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010

Comment 15 Red Hat Bugzilla 2024-08-22 04:25:21 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.