Description of problem: The actions (buttons) of the host interfaces sub-tab doesn't change according to the host version once the host is moved between DCs of different versions: When moving the Host to DC 3.1, there should be SetupNetwork buttons. However, the same buttons for 3.0 DC 'Host Network interfaces' sub tab remain. (Same for moving the host from DC 3.1 to DC 3.0) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Go to hosts tab 2. Select for a host the 'Network Interfaces' sub-tab (the buttons appear according to the DC version) 3. Edit the host and update its version to other version (if originally 3.0, move to 3.1, or the opposite) Actual results: The buttons weren't updated: for 3.0 DC host there are buttons for SetupNetworks. Expected results: The buttons should be updated according to the DC version. Additional info:
why is this DC level and not host level? what are the DC considerations for using the net host level api?
To be more exact - the cluster level is used to determine the supported actiosn for that cluster. The supported cluster version for SetupNetwork is 3.1: The SetupNetworks is being verified to be run on minimal cluster version of 3.1 (defined on action_version_map). So defining it by host level will cause SetupNetworks commands from 3.0 cluster will fail. The current behaviour of 'Edit' host, when moving the host between cluster levels, the menu for the network interfaces remains the same. Once you move to other sub-tab and return to the 'Network Interfaces' sub-tab, the buttons are updated to match the DC level (regardless host compatibility).
If changing the dc of the host from a dc with 3.1 version to another dc with 3.1 and the trying to open setupnetworks (without refreshing the subtab)- there is a NPE.
upstream commit 98b4f7c4d09bb406b1e0908321f76006e849f553
upstream commit 4592e824cb323dadb7ba193fcf9d91d2e1db1221
Verified in SI16