Bug 156976

Summary: traceback when drag and dropping onto valid nodes
Product: [Retired] Red Hat Cluster Suite Reporter: Corey Marthaler <cmarthal>
Component: redhat-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED NEXTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-26 20:28:32 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 Corey Marthaler 2005-05-05 20:14:46 UTC
Description of problem:
I think this was because I drag and dropped a service onto the node it was
already thought to be running on, but I can't be for sure because I only was
able to reproduce this a few times.

Traceback (most recent call last):
  File "/usr/share/system-config-cluster/MgmtTab.py", line 318, in
source_drag_data_get
    selection_data.set(selection_data.target, 0, s_name)
UnboundLocalError: local variable 's_name' referenced before assignment


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

Comment 1 Jim Parsons 2005-05-17 13:04:27 UTC
Doh. Fixed in 0.9.53-1.0

Comment 2 Corey Marthaler 2005-05-26 20:28:32 UTC
fix verified.