This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( 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 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 "", 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 2259674 - Updating VMware NIC type and Network options are disabled for host provisioned via the Red Hat Satellite 6
Summary: Updating VMware NIC type and Network options are disabled for host provisione...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
Depends On:
TreeView+ depends on / blocked
Reported: 2024-01-22 17:28 UTC by Sneha Arya
Modified: 2024-06-06 17:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2024-06-06 17:00:14 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-22622 0 None Migrated None 2024-06-06 17:00:12 UTC

Description Sneha Arya 2024-01-22 17:28:51 UTC
Created attachment 2009714 [details]
Attached the screenshot where VMware NIC and Network type is grayed out

Description of problem:
Updating VMware NIC type and Network options are disabled for host provisioned via the Red Hat Satellite 6

After the creation of a VMware host, Satellite can't perform the following operations:

- Adding an additional NIC
- Configuring an existing NIC
- Deleting an existing NIC

How reproducible:

Steps to Reproduce:
Steps to Reproduce:
1. Provision a VM on a subnet.
2. After provisioning from Satellite, go to the host and edit the interface tab, try changing VMware NIC type and Network options, they are grayed out or disabled.

Actual results:
Unable to change the VMware NIC type and Network setting from the provisioned host's interface tab.

Expected results:
Network and NIC Type should be changed on the provisioned host's interface.

Comment 2 Chris Roberts 2024-02-05 18:45:25 UTC
This is working as intended, the hypervisor host would only get created/show up with a run of virt-who, these are essential fake hosts to make the host/guest mapping work correctly for subscriptions. If you try to edit or do anything on that host in the UI it will fail because it's a fake object. 

Any type of host updates for an ESXi host, should be done either through vCenter or the ESXi webui, if not connected to a vCenter server.

Let's close this out.

Comment 3 Ron Lavi 2024-02-06 14:21:48 UTC
Closing based on Comment 2, this is working as intended

Comment 4 Sayan Das 2024-02-12 11:04:59 UTC
Hello Ron and Chris, 

I believe we are misinterpreting the reported issue in the description.

It's not about modifying any Hypervisor properties at all.

When we are using VMware compute resource\profile to deploy a VM on VMware infra, for the same VM, we cannot change the compute attributes related to the network e.g. VMware NIC type and Network options, etc afterwards, from satellite UI. 

The customer simply wants to make sure that, The way we were able to deploy the VM using compute resources and that allowed us to select and configure the network part, The same should be possible to update\modify\change after the VM deployment as well.. The same concern applies for any associated VMs. 

Please confirm if i should re-open the BZ ?

-- Sayan

Comment 5 Ron Lavi 2024-02-12 20:27:28 UTC
Thanks Sayan, from a quick chat with Chris he acknowledged and therefore I am opening this one, thanks!

Comment 6 Chris Roberts 2024-02-13 14:53:44 UTC
Yes, that is correct, sorry about the confusion.

We should be able to edit the hosts Nic when the VM is powered on since, in VMware you cannot change the Nic while a VM is powered on.

This is a valid bug

Comment 8 Eric Helms 2024-06-06 17:00:14 UTC
This BZ has been automatically migrated to the Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit for general account information.

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