Bug 845932 - Guide Me: It is possible to choose NON_VM network for NIC on VM
Summary: Guide Me: It is possible to choose NON_VM network for NIC on VM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Alona Kaplan
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-06 07:28 UTC by GenadiC
Modified: 2016-02-10 19:56 UTC (History)
7 users (show)

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


Attachments (Terms of Use)
attachment with NON VM Network on VM (214.56 KB, image/png)
2012-08-06 07:28 UTC, GenadiC
no flags Details

Description GenadiC 2012-08-06 07:28:34 UTC
Created attachment 602451 [details]
attachment with NON VM Network on VM

Description of problem:
Guide Me: Creating new VM and adding it new NIC allows you to choose NON_VM Network for that NIC

How reproducible:
Always

Steps to Reproduce:
1. Configure Non VM Network on the Cluster and attach it to host
2. Create the new VM
3. With the Guide Me tool Configure Network Interfaces and choose Network
3.
  
Actual results:
The opened list will display the Non VM Network as well and you can choose for VM

Expected results:
The opened list should contain only VM Networks

Additional info:
Creating new NIC on already created VM will allow you to choose only VM Networks (the correct behaviour)

Comment 1 Alona Kaplan 2012-08-06 09:49:06 UTC
same problem for tepmlate-> add/edit vnic

both problems fiixed in commit 30e48e8977ffce343a344bdcb5a8f1765f2f5b29

Comment 2 GenadiC 2012-08-16 09:05:28 UTC
Verified in SI14


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