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 1007914 - Do not place /boot on iSCSI if it is not possible to boot from it
Summary: Do not place /boot on iSCSI if it is not possible to boot from it
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.5
Hardware: s390x
OS: All
medium
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
Clayton Spicer
URL:
Whiteboard:
Depends On:
Blocks: 972747
TreeView+ depends on / blocked
 
Reported: 2013-09-13 14:44 UTC by Jan Stodola
Modified: 2017-12-06 11:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
The /boot Partition May Be Created on Network Storage on IBM System z A known issue in Anaconda on IBM System z causes the /boot partition to be placed on an iSCSI disk if you do not explicitly configure this partition to be placed on a local drive (DASD). As a result, the system is unable to boot after the installation. To work around this issue, specify a local drive for your /boot partition. When configuring storage using Kickstart, use the 'part /boot --ondisk=<local drive>' command to create /boot. If you are performing a manual installation, select only local drives in the Allowable Drives section of the Add Partition dialog. Do not use automatic partitioning.
Clone Of:
Environment:
Last Closed: 2017-12-06 11:23:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jan Stodola 2013-09-13 14:44:16 UTC
Description of problem:
Anaconda creates /boot partition on iSCSI disk when running installation with following partitioning:

iscsiname iqn-2012-12.com.nb:for.all
iscsi --ipaddr=10.16.67.175 --target=iqn.2012-01.com.example:for.all 
zerombr
bootloader --location=mbr
zerombr
clearpart --all --initlabel
part /boot --size=500
part swap --fstype=swap --recommended
part / --grow --size=2048 --ondisk=/dev/disk/by-id/scsi-1IET_00010001

Partitioning created by anaconda:
[anaconda root@rtt6 root]# mount | grep sysimage
/dev/sda2 on /mnt/sysimage type ext4 (rw,seclabel,relatime,barrier=1,data=ordered)
/dev/sda1 on /mnt/sysimage/boot type ext4 (rw,seclabel,relatime,barrier=1,data=ordered)
none on /mnt/sysimage/dev type tmpfs (rw,seclabel,relatime)
/dev/devpts on /mnt/sysimage/dev/pts type devpts (rw,seclabel,relatime,gid=5,mode=620,ptmxmode=000)
/dev/tmpfs on /mnt/sysimage/dev/shm type tmpfs (rw,seclabel,relatime)
/dev/proc on /mnt/sysimage/proc type proc (rw,relatime)
/dev/sysfs on /mnt/sysimage/sys type sysfs (rw,seclabel,relatime)
/selinux on /mnt/sysimage/selinux type selinuxfs (rw,relatime)

Besides the iSCSI LUN, there are three DASD disks in the system:
[anaconda root@rtt6 root]# lsdasd 
Bus-ID     Status      Name      Device  Type  BlkSz  Size      Blocks
==============================================================================
0.0.3726   active      dasda     94:0    ECKD  4096   2347MB    601020
0.0.3626   active      dasdb     94:4    ECKD  4096   2347MB    601020
0.0.3026   active      dasdc     94:8    ECKD  4096   2347MB    601020

But only one DASD is used (for swap):
[anaconda root@rtt6 root]# swapon -s            
Filename                                Type            Size    Used    Priority
/dev/dasdc1                             partition       1769464 0       -1

So, there are two problems:
1) since it is not possible to boot from iSCSI disk on s390x, anaconda should not place /boot on iSCSI if there are DASD/FCP drives available
2) although "--grow" was used for rootfs, anaconda didn't use whole available space on the iSCSI for it. There were three DASD drives available for /boot partition

Version-Release number of selected component (if applicable):
anaconda-13.21.204-1.el6

How reproducible:
always

Steps to Reproduce:
1. run installation with attached kickstart on an s390x system with at least one DASD/FCP drive

Actual results:
/boot is placed on iSCSI, system will not boot

Expected results:
/boot is not placed on iSCSI if there are DASD/FCP drives available

Comment 7 RHEL Program Management 2013-10-14 02:11:46 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 9 Stephen Gilson 2015-04-16 17:53:11 UTC
Engineering and Product Management along with CCS have determined that this bug should be described in the RHEL 6.7 Release Notes. 

Please update the Doc Text field with a description following the Cause Consequence Workaround Result model by April 22.

Comment 13 Jan Kurik 2017-12-06 11:23:55 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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