Bug 2259674

Summary: Updating VMware NIC type and Network options are disabled for host provisioned via the Red Hat Satellite 6
Product: Red Hat Satellite Reporter: Sneha Arya <snarya>
Component: Compute Resources - VMWareAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: ahumbe, chrobert, lstejska, mhulan, nalfassi, rlavi, saydas, sshtein
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:00:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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 issues.redhat.com 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 https://issues.redhat.com/issues/?jql= 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 https://access.redhat.com/articles/7032570 for general account information.