RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 886576 - "Remove this instance" button has no effect
Summary: "Remove this instance" button has no effect
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-12 15:24 UTC by Radek Steiger
Modified: 2013-11-21 11:00 UTC (History)
5 users (show)

Fixed In Version: luci-0.26.0-39.el6
Doc Type: Bug Fix
Doc Text:
(Ryan to review) Cause: "Remove this instance" button at the fence device instance creation form is superfluous/without a use. Consequence: Misleading button cluttering the user interface. Fix: The button is removed. Result: No misleading/futile button at the mentioned form.
Clone Of:
Environment:
Last Closed: 2013-11-21 11:00:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1603 0 normal SHIPPED_LIVE Moderate: luci security, bug fix, and enhancement update 2013-11-21 00:39:24 UTC

Description Radek Steiger 2012-12-12 15:24:05 UTC
Description of problem:
In the Edit Fence Instance form there's a button named "Remove this instance", that should supposedly initial a removal action of the respective fencing instance. This button however does not react in any way


Version-Release number of selected component (if applicable):
luci-0.26.0-35.el6


How reproducible:
Always


Steps to Reproduce:
1. Add a fence instance to any cluster node
2. Open the instance form again
3. Click the "Remove this instance"
  

Actual results:
Nothing happens.


Expected results:
Something happens.


Additional info:
The button might be considered for removal as there's an "X" button for removing the instance directly on the parental node page.

Comment 2 RHEL Program Management 2012-12-16 06:49:26 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 11 errata-xmlrpc 2013-11-21 11:00:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-1603.html


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