Bug 1210683

Summary: Sync luci with recent changes in the schema for RHEL 6.7
Product: Red Hat Enterprise Linux 6 Reporter: Jan Pokorný [poki] <jpokorny>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.5CC: adshaikh, agk, ccaulfie, cfeist, cluster-maint, cluster-qe, dvossel, fdinitto, jpokorny, mspqa-list, prajnoha, rmccabe, rsteiger
Target Milestone: beta   
Target Release: 6.6   
Hardware: All   
OS: Linux   
Fixed In Version: luci-0.26.0-69.el6 Doc Type: Enhancement
Doc Text:
Feature: Support for configuring fence_emerson and fence_mpath has been added to luci. Reason: New fence agents, fence_emerson, and fence_mpath were added to the fence-agents package for RHEL 6.7. Result: Luci can be used to view and edit configuration for these fence devices.
Story Points: ---
Clone Of: 1210679 Environment:
Last Closed: 2015-07-22 07:33:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1118008, 1210679    
Bug Blocks:    

Description Jan Pokorný [poki] 2015-04-10 11:13:54 UTC
+++ This bug was initially created as a clone of Bug #1210679 +++

New release, same old story once again...

As a starter:

- fence agents: new fence_mpath agent [bug 1118008]

Comment 2 Jan Pokorný [poki] 2015-04-10 13:21:00 UTC
- fence agents: new fence_emerson agent [bug 1171734]

Comment 3 Stephen Gilson 2015-04-13 19:02:21 UTC
This issue needs to be described in the Release Notes for RHEL 6.7

Content Services needs your input to make that happen. 

Please complete the Doc Text text field for this bug by April 20 using the Cause, Consequence, Workaround, and Result model, as follows:

Cause — Actions or circumstances that cause this bug to occur on a customer's system

Consequence — What happens to the customer's system or application when the bug occurs?

Workaround (if any) — If a workaround for the issue exists, describe in detail. If more than one workaround is available, describe each one.

Result — Describe what happens when a workaround is applied. If the issue is completely circumvented by the workaround, state so. Any side effects caused by the workaround should also be noted here. If no reliable workaround exists, try to describe some preventive measures that help to avoid the bug scenario.

Comment 4 Jan Pokorný [poki] 2015-04-17 19:28:31 UTC
See also [bug 1210679 comment 11] for elaborated view on the changes
in fence agents.

Comment 8 errata-xmlrpc 2015-07-22 07:33:16 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.