Bug 615096

Summary:	Traceback when unchecking "Prioritized" in Failover Domains
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Feist <cfeist>
Component:	luci	Assignee:	Chris Feist <cfeist>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Cluster QE <mspqa-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	bbrock, cluster-maint, fdinitto, rmccabe
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	luci-0.22.2-9.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-10 22:11:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Feist 2010-07-15 22:42:19 UTC

Description of problem:
In a failover domain if you set the checkbox "No Failback" and no other checkboxes and then hit "Update Properties" you get a traceback:

AttributeError: FailoverDomain instance has no attribute 'clear_member_nodeis'

Comment 1 Chris Feist 2010-07-15 22:45:05 UTC

Looks like this happens if you set "Prioritized" hit "Update Properties" and the try to unset "Prioritized" and hit "Update Priorities".

Comment 2 Chris Feist 2010-07-16 19:58:41 UTC

Looks like a mis-spelled variable causes this traceback.  Fixed in 3614120e4b3d0b326404ce141a84a1223312e6f4

Comment 3 Fabio Massimo Di Nitto 2010-07-22 08:47:30 UTC

tested a bunch of combinations with No Failback , Prioritized on/off and it seems to working just fine.

Comment 6 releng-rhel@redhat.com 2010-11-10 22:11:54 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.