Bug 827014 - Randomly message on setting default gateway over a bond
Summary: Randomly message on setting default gateway over a bond
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Moti Asayag
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 12:37 UTC by Moti Asayag
Modified: 2016-02-10 19:53 UTC (History)
9 users (show)

Fixed In Version: si12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 20:04:57 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
blank error message (44.91 KB, image/png)
2012-05-31 12:37 UTC, Moti Asayag
no flags Details

Description Moti Asayag 2012-05-31 12:37:05 UTC
Created attachment 588069 [details]
blank error message

Description of problem:
When using SetupNetworks UI to configure a bond with a mamanagement network attached to it, and configuring the bond to with static boot protocol (including gateway), the action fails: The can-do-action message appears selectivly as expected and partially as blank message (see attachments).

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


How reproducible:
selectively

Steps to Reproduce:
1. Using SetupNetworks UI, configure a bond a mamanagement network attached to it
2. Configure the bond to with static boot protocol (including gateway)
3. Click 'ok'
4. Upon expected message error, click on 'close' and 'ok' again to re-send the action.
5. Repeat the scenario couple of time till recieving the blank message.
  
Actual results:
Partially, blank message (see attachment)

Expected results:
An error message describing the problem.

Additional info:

Engine.log has the following line which implies on wrong concatenation of can-do-action messages (due to unneeded leading comma):

2012-05-31 15:03:28,697 WARN  [org.ovirt.engine.core.bll.SetupNetworksCommand] (http--0.0.0.0-8080-1) [1ca14f3a] CanDoAction of action SetupNetworks failed. Reasons:,NETWORK_ATTACH_ILLEGAL_GATEWAY

Comment 1 Moti Asayag 2012-07-24 13:48:14 UTC
Suggested patch: http://gerrit.ovirt.org/#/c/6584/

Comment 2 Moti Asayag 2012-07-25 08:15:15 UTC
commit-id: 38fe5eb427fbc3db24911aabbfb76687612244cd

Comment 3 Martin Pavlik 2012-07-27 14:10:02 UTC
I tried to verify this bug, but there is no error message at all, action just goes through, is that intentional?

Comment 4 Moti Asayag 2012-07-28 12:41:12 UTC
Yes, it was another bug which was fixed that exposed the current.

I'm not sure there is a way to reproduce it from the webadmin, you can try to verify it via rest API and provide a gateway for non-management network (via setup network).

The root cause for both UI and rest-api are the same, as appeared in the log from the bug description:

2012-05-31 15:03:28,697 WARN  [org.ovirt.engine.core.bll.SetupNetworksCommand] (http--0.0.0.0-8080-1) [1ca14f3a] CanDoAction of action SetupNetworks failed. Reasons:,NETWORK_ATTACH_ILLEGAL_GATEWAY

In the Reasons, there was an extra comma (before or after the error message name).

In rest it was present as the message and unnecessary ,:
<details>Details of the error message,</details>

Comment 5 Martin Pavlik 2012-07-30 08:23:34 UTC
Tried with rest API, extra comma is gone 


2012-07-30 10:20:39,145 WARN  [org.ovirt.engine.core.bll.UpdateNetworkToVdsInterfaceCommand] (ajp-/127.0.0.1:8009-5) [3507ea94] CanDoAction of action UpdateNetworkToVdsInterface failed. Reasons:NETWORK_ATTACH_ILLEGAL_GATEWAY


Note You need to log in before you can comment on or make changes to this bug.