Bug 711064

Summary:	Order of iscsi and iscsiname wrong in generated Kickstart File
Product:	[Community] Spacewalk	Reporter:	BugBuster666 <reg>
Component:	WebUI	Assignee:	Jan Pazdziora <jpazdziora>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.4	CC:	jpazdziora
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-schema-1.5.6-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-21 14:43:46 UTC	Type:	---
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:	695242

Description BugBuster666 2011-06-06 12:41:43 UTC

Description of problem:

If I configure a Kickstart profile with iscsi and iscsiname set, the resulting kickstart profile contains: 

...
iscsi --ipaddr a.b.c.d
iscsiname IQN
...

This results in "Initiator name not set" when booting.

The correct order must be: 

...
iscsiname IQN 
iscsi --ipaddr a.b.c.d
...

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

--
spacewalk-repo-1.4-1.el5
spacewalk-java-lib-1.4.37-1.el5
spacewalk-java-config-1.4.37-1.el5
spacewalk-backend-server-1.4.39-1.el5
spacewalk-backend-app-1.4.39-1.el5
spacewalk-backend-xp-1.4.39-1.el5
spacewalk-base-minimal-1.4.21-1.el5
spacewalk-monitoring-selinux-1.3.1-1.el5
spacewalk-admin-1.4.2-1.el5
spacewalk-taskomatic-1.4.37-1.el5
spacewalk-branding-1.4.3-1.el5
perl-XML-NamespaceSupport-1.09-1.2.1
spacewalk-setup-jabberd-1.3.2-1.el5
spacewalk-slf4j-1.6.1-1.el5
spacewalk-backend-libs-1.4.39-1.el5
spacewalk-certs-tools-1.4.1-1.el5
spacewalk-backend-sql-1.4.39-1.el5
spacewalk-backend-config-files-common-1.4.39-1.el5
spacewalk-backend-xmlrpc-1.4.39-1.el5
spacewalk-backend-iss-export-1.4.39-1.el5
spacewalk-backend-config-files-tool-1.4.39-1.el5
spacewalk-backend-iss-1.4.39-1.el5
spacewalk-backend-applet-1.4.39-1.el5
spacewalk-java-postgresql-1.4.37-1.el5
spacewalk-monitoring-1.4.1-1.el5
spacewalk-pxt-1.4.21-1.el5
spacewalk-backend-tools-1.4.39-1.el5
spacewalk-java-1.4.37-1.el5
spacewalk-sniglets-1.4.21-1.el5
spacewalk-setup-1.4.9-1.el5
spacewalk-schema-1.4.18-1.el5
spacewalk-common-1.3.3-1.el5
spacewalk-client-repo-1.4-1.el5
spacewalk-html-1.4.21-1.el5
spacewalk-config-1.4.4-1.el5
spacewalk-doc-indexes-1.1.1-1.el5
spacewalk-backend-sql-postgresql-1.4.39-1.el5
spacewalk-backend-1.4.39-1.el5
spacewalk-backend-xml-export-libs-1.4.39-1.el5
spacewalk-backend-config-files-1.4.39-1.el5
spacewalk-backend-package-push-server-1.4.39-1.el5
spacewalk-search-1.4.1-1.el5
spacewalk-base-1.4.21-1.el5
spacewalk-grail-1.4.21-1.el5
spacewalk-selinux-1.4.1-1.el5
spacewalk-postgresql-1.3.3-1.el5
--

How reproducible:

Configure iSCSI Options in Kickstart. Check the resulting kickstart profile.

Steps to Reproduce:
1. Create Kickstart Profile
2. Configure iscsi Parameter
3. Configure iscsiname Parameter 
  
Actual results:

...
iscsi --ipaddr a.b.c.d
iscsiname IQN
...


Expected results:

...
iscsiname IQN 
iscsi --ipaddr a.b.c.d
...


Additional info:

Comment 1 BugBuster666 2011-06-07 15:23:09 UTC

A quick test on RHN Sattelite shows that this also happens on RHN.

Comment 2 Jan Pazdziora 2011-06-08 12:33:01 UTC

(In reply to comment #0)
> kickstart profile contains: 
> 
> ...
> iscsi --ipaddr a.b.c.d
> iscsiname IQN
> ...
> 
> This results in "Initiator name not set" when booting.

What operating system is being booted here?

Comment 3 Jan Pazdziora 2011-06-08 12:39:09 UTC

Taking.

Comment 4 Jan Pazdziora 2011-06-08 12:40:27 UTC

Could you please check if running

update rhnKickstartCommandName set sort_order = 40 where name = 'iscsiname';
update rhnKickstartCommandName set sort_order = 41 where name = 'iscsi';
commit;

in sqlplus against your spacewalk database acount fixes the order?

Comment 5 BugBuster666 2011-06-22 22:01:14 UTC

Sorry for the delay ...

Hello I did what you suggested, 

After applying the order patch above and saving the kickstart profile again (advanced options -> modify kickstart), the order was correct. It seems this fixes the issue. 

Thanks and Regards, 
Robert

Comment 6 Jan Pazdziora 2011-07-15 13:38:39 UTC

Thank you for the confirmation.

Fixed in Spacewalk master, 9181edb8c54b4f396613219e97504149e701b2c9.

Comment 7 Jan Pazdziora 2011-07-19 19:36:53 UTC

This bugzilla is currently MODIFIED, so we believe the fix is in the Spacewalk nightly yum repository at http://spacewalk.redhat.com/yum/nightly/

Therefore, moving ON_QA.

Comment 8 Jan Pazdziora 2011-07-21 14:43:46 UTC

Spacewalk 1.5 was released.