Bug 1064397 - Empty properties panel for cluster policy None
Summary: Empty properties panel for cluster policy None
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.1
Assignee: Martin Sivák
QA Contact: bugs@ovirt.org
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-12 14:24 UTC by Eli Mesika
Modified: 2014-05-08 13:36 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-08 13:36:41 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
Screenshot (52.55 KB, image/png)
2014-02-12 14:25 UTC, Eli Mesika
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25087 0 None MERGED webadmin: Hide custom policy properties section if empty Never

Description Eli Mesika 2014-02-12 14:24:37 UTC
Description of problem:
Empty properties panel for cluster policy None

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


How reproducible:


Steps to Reproduce:
1.select 'configure' from webadmin
2.select 'cluster policies'
3.Double click on None cluster policy
4.Properties panel is empty 

Actual results:
Empty properties panel for cluster policy None


Expected results:
properties panel for cluster policy None should be hidden


Additional info:
screen-shot

Comment 1 Eli Mesika 2014-02-12 14:25:31 UTC
Created attachment 862327 [details]
Screenshot

Comment 2 Itamar Heim 2014-02-16 08:23:50 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 3 Sandro Bonazzola 2014-03-04 09:19:29 UTC
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 4 Sandro Bonazzola 2014-05-08 13:36:41 UTC
This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.


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