Description of problem: When adding a new host a Network provider subtab exist so you can configure it on the new host, but the moment host is added to the setup (after installation) there is no indication on GUI that the host was installed with network provider Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install a new host with external provider 2. Try to find on GUI if the host was installed with external provider (when try to know this fact or update some field) 3. Actual results: There is no way to know how host was installed Expected results: There should exist a field with such information Additional info:
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
We should enable the user to select if to install the agent on the host or not (on by default). The provider details should be used for better scheduling of VMs to select only the hosts that have the provider marked/installed.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
There should also be a checkbox (for the supported plugin types) which asks the user if he wants to install the agent on the host. When installing a new host, it should be checked by default (and agent fields enabled). When reinstalling, it should be unchecked by default (and agent fields disabled). When editing the host, only provider selection field should be visible and list whatever the user selects. Additionally, The VM scheduling mechanism should be adjusted to take into account only hosts that are marked with the provider that is providing the external network.
*** Bug 1151510 has been marked as a duplicate of this bug. ***
Having a network provider field to the host will allow also managing the agent details for the specific host on the 'Edit Host' dialog, in addition to the [re]install host dialog.
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant.
This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still an issue.