Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1058024

Summary: There is no notification for failed sync action
Product: [Retired] oVirt Reporter: GenadiC <gcheresh>
Component: ovirt-engine-webadminAssignee: lpeer <lpeer>
Status: CLOSED WORKSFORME QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, ecohen, gcheresh, gklein, iheim, masayag, mgoldboi, myakove, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-19 08:19:30 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:
Embargoed:
Attachments:
Description Flags
engine and vdsm log none

Description GenadiC 2014-01-26 14:03:49 UTC
Description of problem:
There is no error in engine/GUI when trying to sync mtu of 9000 on the host that doesn't support this MTU

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create network with MTU of 9000 (or update an existing 1500 with 9000)
2. Attach this network to the Host that doesn't support such MTU
3. Try to sync the network on the Host

Actual results:
Though the action fails there is no notification that action failed

Expected results:
Notification of failed action should appear in GUI and engine log

Additional info:

Comment 1 Itamar Heim 2014-02-02 08:17:13 UTC
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.

Comment 2 GenadiC 2014-02-02 13:44:56 UTC
Created attachment 858244 [details]
engine and vdsm log

Comment 3 Moti Asayag 2014-02-18 16:22:04 UTC
Could you elaborate what how the action fails ? I might missed it from the logs, but where i looked at, it seems that vdsm was able to configure MTU 9000 on 'eth1':

The setup network request: 
Thread-184044::DEBUG::2014-02-02 11:17:24,047::BindingXMLRPC::970::vds::(wrapper) client [10.35.163.132]::call setupNetworks with ({'sw1': {'nic': 'eth1', 'STP': 'no', 'bridged': 'true', 'mtu': '9000'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}) {} flowID [369866c7]
...
Thread-184044::DEBUG::2014-02-02 11:17:27,756::BindingXMLRPC::977::vds::(wrapper) return setupNetworks with {'status': {'message': 'Done', 'code': 0}}

The following getVdsCaps:
Thread-184056::DEBUG::2014-02-02 11:17:28,225::BindingXMLRPC::970::vds::(wrapper) client [10.35.163.132]::call getCapabilities with () {} flowID [369866c7]
...
Thread-184056::DEBUG::2014-02-02 11:17:28,297::BindingXMLRPC::977::vds::(wrapper) return getCapabilities with {'status': {'message': 'Done', 'code': 0}, 'info': {'HBAInventory': {'iSCSI': [{'InitiatorName': 'iqn.1994-05.com.redhat:pink-vds3'}], 'FC': []}, 'packages2': {'kernel': {'release': '431.el6.x86_64', 'buildtime': 1384114794.0, 'version': '2.6.32'}, 'spice-server': {'release': '6.el6', 'buildtime': 1381834773L, 'version': '0.12.4'}, 'vdsm': {'release': '2.el6', 'buildtime': 1390309864L, 'version': '4.14.1'}, 'qemu-kvm': {'release': '2.415.el6_5.3', 'buildtime': 1384256088L, 'version': '0.12.1.2'}, 'libvirt': {'release': '29.el6_5.2', 'buildtime': 1386770011L, 'version': '0.10.2'}, 'qemu-img': {'release': '2.415.el6_5.3', 'buildtime': 1384256088L, 'version': '0.12.1.2'}, 'mom': {'release': '20140110.git17d037b.el6', 'buildtime': 1389385791L, 'version': '0.3.2'}}, 'cpuModel': 'Intel(R) Xeon(R) CPU            3040  @ 1.86GHz', 'hooks': {}, 'cpuSockets': '1', 'vmTypes': ['kvm'], 'supportedProtocols': ['2.2', '2.3'], 'networks': {'ovirtmgmt': {'iface': 'ovirtmgmt', 'addr': '10.35.128.39', 'cfg': {'DEFROUTE': 'yes', 'IPADDR': '10.35.128.39', 'GATEWAY': '10.35.128.254', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'NETMASK': '255.255.255.0', 'BOOTPROTO': 'none', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge', 'ONBOOT': 'yes'}, 'ipv6addrs': ['fe80::92e2:baff:fe0d:ca7e/64'], 'gateway': '10.35.128.254', 'netmask': '255.255.255.0', 'stp': 'off', 'bridged': True, 'mtu': '1500', 'ipv6gateway': '::', 'ports': ['eth0']}, 'sw1': {'iface': 'sw1', 'addr': '', 'cfg': {'MTU': '9000', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'STP': 'no', 'DEVICE': 'sw1', 'TYPE': 'Bridge', 'ONBOOT': 'yes'}, 'ipv6addrs': ['fe80::92e2:baff:fe0d:ca7f/64'], 'gateway': '', 'netmask': '', 'stp': 'off', 'bridged': True, 'mtu': '9000', 'ipv6gateway': '::', 'ports': ['eth1']}}, 'bridges': {'ovirtmgmt': {'addr': '10.35.128.39', 'cfg': {'DEFROUTE': 'yes', 'IPADDR': '10.35.128.39', 'GATEWAY': '10.35.128.254', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'NETMASK': '255.255.255.0', 'BOOTPROTO': 'none', 'DEVICE': 'ovirtmgmt', 'TYPE': 'Bridge', 'ONBOOT': 'yes'}, 'ipv6addrs': ['fe80::92e2:baff:fe0d:ca7e/64'], 'mtu': '1500', 'netmask': '255.255.255.0', 'stp': 'off', 'ipv6gateway': '::', 'gateway': '10.35.128.254', 'ports': ['eth0']}, ';vdsmdummy;': {'addr': '', 'cfg': {}, 'ipv6addrs': [], 'mtu': '1500', 'netmask': '', 'stp': 'off', 'ipv6gateway': '::', 'gateway': '', 'ports': []}, 'sw1': {'addr': '', 'cfg': {'MTU': '9000', 'DELAY': '0', 'NM_CONTROLLED': 'no', 'STP': 'no', 'DEVICE': 'sw1', 'TYPE': 'Bridge', 'ONBOOT': 'yes'}, 'ipv6addrs': ['fe80::92e2:baff:fe0d:ca7f/64'], 'mtu': '9000', 'netmask': '', 'stp': 'off', 'ipv6gateway': '::', 'gateway': '', 'ports': ['eth1']}}, 'uuid': '387D3C42-6B67-3000-8914-EFFAB218B576', 'lastClientIface': 'ovirtmgmt', 'nics': {'int-br-eth1': {'netmask': '', 'addr': '', 'hwaddr': '3e:ca:19:f6:2e:e0', 'cfg': {}, 'ipv6addrs': [], 'speed': 0, 'mtu': '1500'}, 'phy-br-eth1': {'netmask': '', 'addr': '', 'hwaddr': '7e:8f:45:29:51:da', 'cfg': {}, 'ipv6addrs': [], 'speed': 0, 'mtu': '1500'}, 'eth3': {'netmask': '', 'addr': '', 'hwaddr': '00:14:5e:6b:15:34', 'cfg': {'UUID': '00080159-693d-40d8-ab00-10de9ea73d70', 'DHCP_HOSTNAME': 'pink-vds3.qa.lab.tlv.redhat.com', 'NM_CONTROLLED': 'yes', 'HWADDR': '00:14:5E:6B:15:34', 'BOOTPROTO': 'none', 'DEVICE': 'eth3', 'TYPE': 'Ethernet', 'ONBOOT': 'no'}, 'ipv6addrs': [], 'speed': 0, 'mtu': '1500'}, 'eth2': {'netmask': '', 'addr': '', 'hwaddr': '00:14:5e:6b:15:33', 'cfg': {'DEVICE': 'eth2', 'HWADDR': '00:14:5e:6b:15:33', 'ONBOOT': 'yes', 'MTU': '1500'}, 'ipv6addrs': ['fe80::214:5eff:fe6b:1533/64'], 'speed': 1000, 'mtu': '1500'}, 'eth1': {'netmask': '', 'addr': '', 'hwaddr': '90:e2:ba:0d:ca:7f', 'cfg': {'BRIDGE': 'sw1', 'NM_CONTROLLED': 'no', 'MTU': '9000', 'HWADDR': '90:e2:ba:0d:ca:7f', 'STP': 'no', 'DEVICE': 'eth1', 'ONBOOT': 'yes'}, 'ipv6addrs': [], 'speed': 0, 'mtu': '9000'}, 'eth0': {'netmask': '', 'addr': '', 'hwaddr': '90:e2:ba:0d:ca:7e', 'cfg': {'DEVICE': 'eth0', 'HWADDR': '90:e2:ba:0d:ca:7e', 'ONBOOT': 'yes', 'NM_CONTROLLED': 'no',

Comment 4 Moti Asayag 2014-02-19 08:19:30 UTC
Testing the same scenario on the reporter's environment has ended with the following message in the events log:

"Host pink-vds3.qa.lab.tlv.redhat.com's following network(s) are not synchronized with their Logical Network configuration: netfor31."