Bug 615872

Summary: unicode error deleting a cluster
Product: Red Hat Enterprise Linux 6 Reporter: Fabio Massimo Di Nitto <fdinitto>
Component: luciAssignee: Ryan McCabe <rmccabe>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: bbrock, cluster-maint
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:57 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 Fabio Massimo Di Nitto 2010-07-19 07:30:51 UTC
deleting a whole cluster from luci shows this error in the logs (nothing critical as the cluster seems to be removed correctly):

09:27:09,476 ERROR [luci.lib.db_helpers] Unable to communicate with ricci on any nodes in cluster fabbione
/usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received non-unicode bind param value 'fabbione'
  param.append(processors[key](compiled_params[key]))

Comment 2 RHEL Program Management 2010-07-19 07:58:01 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Fabio Massimo Di Nitto 2010-07-19 08:18:08 UTC
forgot to mention, this is using the latest code from luci.git

Comment 8 releng-rhel@redhat.com 2010-11-10 22:11:57 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.