Description of problem:
In the RHEV 3.0 environment, STP was enabled on the host NIC devices. After upgrading to RHEV 3.1, the option to enable/disable STP was removed from the Admin Portal. Now, the only way to disable STP is to manually edit the ifcfg files on the host (not recommended).
Version-Release number of selected component (if applicable):
3.1.0-50
Steps to Reproduce:
1. Install RHEV 3.0
2. Enable STP on at least 1 NIC device on a host and save the configuration
3. Upgrade to RHEV 3.1.z
4. Launch "Setup host networks" screen and attempt to disable STP or try to save the configuration again
Actual results:
STP is always enabled/re-enabled on the host even if STP is manually removed from the ifcfg file
Expected results:
STP should no longer be enabled on the hosts if it is not exposed in the GUI
Additional info:
If this is expected behavior, we should offer customers a way to disable STP across all of their hosts without having to manually edit the rhevm/engine database.
(In reply to Itamar Heim from comment #2)
> livnat - is this disabled in ui only or in API as well?
The STP property on network level was removed only from the UI and can be modified via the API (on add/update network using network.stp).
- name: /api/networks/{network:id}|rel=update
request:
body:
parameterType: Network
signatures:
- mandatoryArguments: {}
optionalArguments: {network.name: 'xs:string', network.description: 'xs:string', network.comment: 'xs:string', network.vlan.id: 'xs:string',
network.ip.address: 'xs:string', network.ip.gateway: 'xs:string', network.ip.netmask: 'xs:string',
network.display: 'xs:boolean', network.stp: 'xs:boolean', network.mtu: 'xs:int'}