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

Bug 906313

Summary: [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel"
Product: [Retired] oVirt Reporter: Mike Kolesnik <mkolesni>
Component: ovirt-engine-webadminAssignee: Lior Vernia <lvernia>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.2CC: acathrow, bazulay, ecohen, gcheresh, iheim, masayag, mgoldboi, myakove
Target Milestone: ---Keywords: Triaged
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: ovirt-3.4.0-alpha1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:33:21 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
screenshot none

Description Mike Kolesnik 2013-01-31 12:53:01 UTC
Created attachment 690871 [details]
screenshot

Description of problem:
Getting the message:
No valid Operation for test_mtu_5000 and Unassigned Logical Networks panel

When trying to attach network to a host's NIC.


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


How reproducible:
90% - Sometimes it's fine, but usually this message appears


Steps to Reproduce:
1. Create a network in the DC & attach to a cluster
2. Open setup networks on the host
3. Try to drag the network to an unassigned NIC
  
Actual results:
The error is displayed, and network can't be set on the nic.


Expected results:
The error shouldn't be displayed.


Additional info:
If hovering over the nic panel itsel it doesn't happen, only when hovering over the "Unassigned" panel.
This also happens on networks main tab

Comment 1 Sandro Bonazzola 2013-11-28 15:34:30 UTC
Re-targeting to 3.3.3 since the bug is not resolved in 3.3.2 beta and is not blocking 3.3.2 release tracker (bug #1027349)

Comment 2 Sandro Bonazzola 2014-01-13 13:57:17 UTC
oVirt 3.4.0 alpha has been released including the fix for this issue.

Comment 3 GenadiC 2014-02-17 11:32:04 UTC
Verified in ovirt-engine-3.4.0-0.7.beta2.el6.noarch

Comment 4 Sandro Bonazzola 2014-03-31 12:33:21 UTC
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released