Bug 1012009 - [RHEVM][webadmin] rephrase error message on adding profile to nonVM network
Summary: [RHEVM][webadmin] rephrase error message on adding profile to nonVM network
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: 3.3.0
Assignee: Moti Asayag
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On:
Blocks: 1019461 3.3snap2
TreeView+ depends on / blocked
 
Reported: 2013-09-25 14:37 UTC by Martin Pavlik
Modified: 2016-02-10 19:47 UTC (History)
8 users (show)

Fixed In Version: is21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-31 07:06:19 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 20474 0 None None None Never
oVirt gerrit 20486 0 None None None Never

Description Martin Pavlik 2013-09-25 14:37:33 UTC 
Description of problem:

When user tries to create network profile for non VM network, following error message appears:
	
Error while executing action: Cannot add VM network interface profile. VM network interface profiles can be added to a VM network only.

I had to read the message several times before I understood what is wrong.

Maybe a little extension could help

Error while executing action: Cannot add VM network interface profile to *nonVM* network. VM network interface profiles can be added to a VM network only.


Additional info:
2013-09-25 16:20:37,807 WARN  [org.ovirt.engine.core.bll.network.vm.AddVnicProfileCommand] (ajp-/127.0.0.1:8702-13) [6d71c64] CanDoAction of action AddVnicProfile failed. Reasons:VAR__TYPE__VNIC_PROFILE,VAR__ACTION__ADD,ACTION_TYPE_FAILED_CANNOT_ADD_VNIC_PROFILE_TO_NON_VM_NETWORK
Comment 1 Martin Pavlik 2013-09-25 14:42:22 UTC 
Steps to reproduce:
1) create nonVM network
2) Networks -> your network -> edit
3) Profiles -> fill in profile name -> OK
Note You need to log in before you can comment on or make changes to this bug.