Bug 1002534

Summary:	Pegasus badly handles null characters
Product:	Red Hat Enterprise Linux 7	Reporter:	Petr Sklenar <psklenar>
Component:	tog-pegasus	Assignee:	Vitezslav Crhonek <vcrhonek>
Status:	CLOSED DUPLICATE	QA Contact:	qe-baseos-daemons
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.0	CC:	psklenar, rhack, rrakus
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-16 11:13:37 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:
Bug Blocks:	922084

Description Petr Sklenar 2013-08-29 12:05:23 UTC

Description of problem:
Account provider: create user with null char

Version-Release number of selected component (if applicable):
openlmi-account-0.1.1-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
code:

cs = self.conn.root.cimv2.Linux_ComputerSystem.first_instance()
lams = self.conn.root.cimv2.LMI_AccountManagementService.first_instance()
user = lams.CreateAccount(Name=chr(0), System=cs)

Actual results:
it doesn't do anything

Expected results:
there is an error and it doesn't stack

Additional info:

Comment 2 Roman Rakus 2013-08-30 08:17:39 UTC

Does it make the same output if you pass an empty string? (Name='')

Comment 3 Petr Sklenar 2013-08-30 08:55:21 UTC

(In reply to Roman Rakus from comment #2)
> Does it make the same output if you pass an empty string? (Name='')
Actually its not about empty string but null string:

>>> account2a = account2.CreateAccount(Name='', System=cs)
>>> account2a
LMIReturnValue(rval=-1, rparams={}, errorstr=u"CIM_ERR_FAILED: Error creating group: unknown error\n: 'CreateAccount'")
>>> account2a = account2.CreateAccount(Name=chr(0), System=cs)
### here it stucks

There could be 'error unknown' or better "Error creating group: name contains invalid char."

The main: it shouldn't stuck with bugfix.

Comment 4 Roman Rakus 2013-08-30 12:46:17 UTC

Looks like it does not go into provider, it is stuck in the Pegasus.

We can learn lmi shell to not pass null.

Comment 6 Vitezslav Crhonek 2013-09-16 11:13:37 UTC


*** This bug has been marked as a duplicate of bug 1007386 ***