Bug 640670

Summary:	Regression: db-sid in answer file ignored, says it's missing
Product:	[Community] Spacewalk	Reporter:	Sandro Mathys <sandro>
Component:	Installation	Assignee:	Jan Pazdziora (Red Hat) <jpazdziora>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.1	CC:	colin.coe
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-20 17:09:39 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:	653453

Description Sandro Mathys 2010-10-06 15:04:53 UTC

Description of problem:
We install our spacewalk instances unattended, therefore we use an answer file for the installation.

Now while this worked fine with spacewalk 0.8 (and I think 1.0 but maybe we never installed that from scratch, i.e. only updated 0.8) in spacewalk 1.1 the installer ignores the db-sid setting and says it's missing the necessary DB SID information.

Version-Release number of selected component (if applicable):
spacewalk-setup-1.1.14-1.el5

How reproducible:
Always

Steps to Reproduce:
1. create an answer file
2. spacewalk-setup --disconnected --non-interactive --answer-file=/path/to/answers.txt --clear-db
  
Actual results:
No answer provided for 'DB SID'

Expected results:
installer reads DB SID from answer file and continues

Additional info:
If I strip the "--non-interactive" I'm being asked for the DB SID. If I give the same answer as is written in the answer file it works.

The according line in case it matters:
db-sid = swdb

Comment 1 Jan Pazdziora (Red Hat) 2010-10-27 08:32:20 UTC

Mass-aligning under space12, so that we don't lose track of this bugzilla. This however does not mean that we plan (will be able to) address this bug in Spacewalk 1.2.

Comment 2 Colin Coe 2010-11-05 06:22:47 UTC

Does it work if you change 'db-sid' to 'db-name' in the answer file?  

I ask because I see no reference to 'db-sid' in git/spacewalk/spacewalk/setup/lib/Spacewalk/Setup.pm but I do see a reference to 'db-name'.

Comment 3 Jan Pazdziora (Red Hat) 2010-11-19 16:02:55 UTC

Mass-moving to space13.

Comment 4 Jan Pazdziora (Red Hat) 2010-11-20 17:09:39 UTC

The db-sid was indeed changed to db-name. Please change the parameter name in your answer file.

Closing as CURRENTRELEASE, please reopen if you disagree.