Bug 787618 - [webadmin] - Wrong message, when attempting to delete a LN that is being used by a Template[TEXT]
Summary: [webadmin] - Wrong message, when attempting to delete a LN that is being used...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 10:46 UTC by zvi
Modified: 2012-08-16 05:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 05:30:51 UTC
oVirt Team: ---


Attachments (Terms of Use)

Description zvi 2012-02-06 10:46:27 UTC
Description of problem:

Wrong message when attemting to delete a Cluster LN that is being used by a Template. 
or
Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Attemt to delete a Cluster LN that is being used by a Template
2.
3.
  
Actual results:

Message:	
	
Oops!
Error: Cannot ${action} ${type}. The Network is in use by a Template.<br/>Network definition cannot be detached unless all references to it are cleared. 

Expected results:
Message:
"Can't remove Network, it is being used by: (Template name)"



Additional info:
Engine log:

-001a4a169746 Type: VDS
2012-02-06 12:37:53,704 INFO  [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (pool-5-thread-50) Running command: HandleVdsVersionCommand internal: true. Entities affected :  ID: cf51fd24-50a7-11e1-a45a-001a4a169746 Type: VDS
2012-02-06 12:37:53,706 INFO  [org.ovirt.engine.core.vdsbroker.ActivateVdsVDSCommand] (pool-5-thread-50) FINISH, ActivateVdsVDSCommand, log id: 6124cf94
2012-02-06 12:38:06,809 WARN  [org.ovirt.engine.core.bll.DetachNetworkToVdsGroupCommand] (http--0.0.0.0-8080-6) CanDoAction of action DetachNetworkToVdsGroup failed. Reasons:NETWORK_CANNOT_REMOVE_NETWORK_IN_USE_BY_TEMPLATE

Comment 1 Einav Cohen 2012-02-06 11:43:40 UTC
backend doesn't send the relevant "action" and "type" messages within the CanDoActionMessages list returned in this case.

BTW, it seems that a similar problem happens for the "NETWORK_INTERFACE_IN_USE_BY_VM" message key, which translates to "Cannot ${action} ${type}. There is at least one running VM that uses this Network."

Comment 3 lpeer 2012-08-16 05:30:51 UTC
It is working with the upstream version now.


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