Bug 857462 - RFE: Disable 'Purge' button on destination level when no deployment is LIVE
Summary: RFE: Disable 'Purge' button on destination level when no deployment is LIVE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: RHQ 4.6
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-14 13:47 UTC by Libor Zoubek
Modified: 2015-11-02 00:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-31 10:16:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Libor Zoubek 2012-09-14 13:47:46 UTC
Description of problem: I have a bundle, that has been deployed to some destination and is already purged. So there is currently no LIVE deployment of this bundle. Then I navigate to my destination and click purge. I get meaningful error in message center.

It would be nice if purge button was disabled or not present at all when there's no LIVE deployment, because it would end in exception anyway.


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

How reproducible: always

Comment 1 Jirka Kremser 2012-10-08 13:13:35 UTC
fixed in master
http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=f4e6014

time:    Mon Oct 8 14:52:02 2012 +0200
commit:  f4e6014c04a1b6d7bb81c1392f49a372d4477f93
author:  Jirka Kremser - jkremser
message: [BZ 857462 - RFE: Disable 'Purge' button on destination level when no deployment is LIVE] If at least one deployment is LIVE the button is enabled, otherwise it is disabled. The call is made, when constructing the UI components.

Comment 2 Libor Zoubek 2013-04-02 09:32:23 UTC
verified on RHQ Version: 4.7.0-SNAPSHOT Build Number: bd0c492

Comment 3 Heiko W. Rupp 2013-08-31 10:16:51 UTC
Bulk close of old bugs in VERIFIED state.


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