RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 676118 - iscsi --target kickstart option not actually used
Summary: iscsi --target kickstart option not actually used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.0
Assignee: Ales Kozumplik
QA Contact: Release Test Team
URL:
Whiteboard: patch
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-08 20:58 UTC by cruejones
Modified: 2014-09-30 23:39 UTC (History)
4 users (show)

Fixed In Version: anaconda-13.21.118-1
Doc Type: Bug Fix
Doc Text:
Clone Of: 676114
Environment:
Last Closed: 2011-12-06 10:29:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1565 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-12-06 00:39:12 UTC

Description cruejones 2011-02-08 20:58:35 UTC
Description of problem:

kickstart iscsi root install does not use --target option even if specified. 
will use any target that may be available at --ipaddr.

iscsi --ipaddr <ip> --target <iqn>

also, when doing a manual install and selecting a specific target it will work
but will not correctly report in /root/anaconda-ks.cfg.  only reports:

isci --ipaddr <ip>

no --target, even though the manual installer works.


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

RHEL6
Fedora14

How reproducible:
always

1. setup an iscsi target server with more than one target exported
2. use "iscsi --ipaddr <ip> --target <target>" in kickstart file
3. install will work but not use actual target specified (unless your lucky) 

Actual results:
specified target not used

Expected results:
specified target used

Additional info:
--target= shouldn't be ignored in ks.cfg and that writeKS should include it.

Comment 2 Ales Kozumplik 2011-02-24 06:35:20 UTC
Related fedora bug: bug 676114.

Comment 3 RHEL Program Management 2011-05-13 23:09:25 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 4 Ales Kozumplik 2011-06-10 08:18:41 UTC
Fixed by e025eea49bc10b7c710048498846f3db2b846063.

Comment 6 Alexander Todorov 2011-08-18 15:50:44 UTC
Tested with anaconda-13.21.130 and 2 targets. ks.cfg specified only the second target. The first one was not used and data on it was intact. Moving to VERIFIED.

Comment 7 errata-xmlrpc 2011-12-06 10:29:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1565.html


Note You need to log in before you can comment on or make changes to this bug.