Bug 521043

Summary:	[RFE] Database specific code should be split from spacewalk-setup
Product:	[Community] Spacewalk	Reporter:	Michael Mráka <mmraka>
Component:	Installation	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	0.7	CC:	cperry, herrold, jpazdziora, msuchy
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-10 09:27:03 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:
Bug Blocks:	737830

Description Michael Mráka 2009-09-03 09:53:52 UTC

Description of problem:
Support of different database backends requires split of database specific code to independent setup scripts. Otherwise we will install unnecessary drivers/scripts via rpm dependencies.


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

How reproducible:


Steps to Reproduce:
1. choose one of database backends (oracle o postgresql as of now)
2. install spacewalk
3. check that no other database backend packages/scripts/files have been installed (e.g. via rpm -q)
  
Actual results:
both oracle and postgresql packages are installed:
oracle-instanclient-basic
oracle-instanclient-sqlplus
cx_Oracle
postgresql-jdbc
postgresql-libs
python-pgsql

Expected results:
successful installation
only drivers for selected db installed

Additional info:

Comment 1 Jan Pazdziora (Red Hat) 2010-11-19 16:05:38 UTC

Mass-moving to space13.

Comment 2 Miroslav Suchý 2011-01-19 21:44:14 UTC

Michael, this is already solved, isn't it?
Can we close this one?

Comment 3 Michael Mráka 2011-01-20 09:18:43 UTC

Nope, it's not finished yet.

Comment 4 Miroslav Suchý 2011-04-11 07:34:14 UTC

We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 5 Miroslav Suchý 2011-04-11 07:37:27 UTC

We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 6 Jan Pazdziora (Red Hat) 2011-07-20 11:52:51 UTC

Aligning under space16.

Comment 7 Jan Pazdziora (Red Hat) 2012-12-07 19:31:02 UTC

I'd consider this resolved. With the spacewalk-sql script and the spacewalk-oracle and spacewalk-postgresql packages, you choose the the supported backend during installation. Yes, in pacewalk-setup and Spacewalk::Setup, we have a mix of functions for both databases and we might get to split that out eventually, but right the installation works just fine so I propose closing it as CURRENTRELEASE. Do you concur?