Bug 1031220

Summary:	pulp.server.db.model.base.Models return None when accessing attributes that do not exist
Product:	[Retired] Pulp	Reporter:	Randy Barlow <rbarlow>
Component:	z_other	Assignee:	Michael Hrivnak <mhrivnak>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Preethi Thomas <pthomas>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Master	CC:	mhrivnak, pthomas
Target Milestone:	---	Keywords:	Triaged
Target Release:	2.4.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-09 06:54:51 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:
Embargoed:

Description Randy Barlow 2013-11-15 22:47:53 UTC

Our base Model class has a very surprising property in that it will return None if attributes are accessed that do not exist. This is unexpected behavior. It would be more appropriate for an AttributeError to be raised.

Comment 1 Michael Hrivnak 2013-12-09 15:23:00 UTC

https://github.com/pulp/pulp/pull/732

Comment 2 Michael Hrivnak 2013-12-09 15:29:23 UTC

QE: I'm not sure how you'll want to verify this. There was not an incorrect behavior from a user standpoint. This was just a code change to make our lives much much easier, and the user experience deliberately did not change at all. Feel free to ping me for details.

Comment 3 Jeff Ortel 2014-04-03 13:36:00 UTC

build: 2.4.0-0.7.beta

Comment 4 Preethi Thomas 2014-07-07 13:13:09 UTC

Moving to verified as per https://bugzilla.redhat.com/show_bug.cgi?id=1031220#c2

Comment 5 Randy Barlow 2014-08-09 06:54:51 UTC

This has been fixed in Pulp 2.4.0-1.