Bug 661662

Summary:	Several database tables have row movement disabled
Product:	Red Hat Satellite 5	Reporter:	Milan Zázrivec <mzazrivec>
Component:	Server	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	540	CC:	cperry, mmraka
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	649706	Environment:
Last Closed:	2014-07-04 13:26:24 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:
Bug Depends On:	649706
Bug Blocks:	462714

Comment 1 Jan Pazdziora (Red Hat) 2010-12-09 12:23:18 UTC

The fix that was implemented in db-control enables the row movement when needed.

While I agree that we should be consistent and have row movement enabled in all tables, unless we have some sanity check which will test our schema definitions, even if we fix this bugzilla once, the problem may reoccur.

Therefore I feel that the db-control fix is actually enough.

Comment 2 Milan Zázrivec 2010-12-09 12:34:55 UTC

First of all, db-control will work for embedded databases only. Second
of all, closing the bug just because there's no sanity test for this
available is nothing but a shallow argument.

Besides, if you think having a sanity test like that is important, it
can be implemented as a part of the fix for this bug.

I'm reopening this bug and assigning it to myself, since I don't consider
discussions about what the current default owner of 'Server' component
"feels" that constructive (or important).