Bug 381201

I think i have a suspicion where the problem might come from, will investigate
in the next few days.

Read ya, Phil

This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release.  This request will
be reviewed for a future Red Hat Enterprise Linux release.

----- Additional Comments From suzukikp.com (prefers email at
suzuki.com)  2008-04-01 03:31 EDT -------
--- Additional info from 43310 ---

Looks like the "target=" option is mandatory for all the sections in
the
zipl.conf file.

This worked fine for your original /etc/zipl.conf file, since there was
only one
section and thus it was fine. But when you added another section
("[dump_dasd]")
it requires that you have to add "target=" for each section.

Thanks

Suzuki

----------------------------- 


This event sent from IssueTracker by jkachuck 
 issue 129816

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.

The upstream documentation
(http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26cdd04.pdf,
page 396, available at
http://www-128.ibm.com/developerworks/linux/linux390/october2005_documentation.html)
says:

The default section consists of the section identifier [defaultboot] followed by a
single option line. The option line specifies one of these mutually exclusive
options:
...

So the comment #4 is right, see page 387 for details.

The following config should work
[defaultboot]
default=2.6.18-54.el5.b
[2.6.18-54.el5.b]
        image=/boot/vmlinuz-2.6.18-54.el5.bz325451.rm7
        ramdisk=/boot/initrd-2.6.18-54.el5.bz325451.rm7.img
        parameters="root=/dev/VolGroup00/LogVol00"
        target=/boot
[linux]
        image=/boot/vmlinuz-2.6.18-52.el5
        ramdisk=/boot/initrd-2.6.18-52.el5.img
        parameters="root=/dev/VolGroup00/LogVol00"
        target=/boot

Please, can you check it?

With the config in comment 6, you get the error:

# zipl linux --dry-run
Using config file '/etc/zipl.conf'
Error: Config file '/etc/zipl.conf': Line 1: missing keyword 'target' in section
'defaultboot'

Adding target= back to [defaultboot] (so target= is in 3 places) works.  Not
sure if this is expected behavior.  The documentation is a little unclear on
this.  On p. 396, it makes it appear that the [defaultboot] only requires a
default= or defaultmenu= parameter.

Hmm, it is our "automenu" patch that modifies the default upstream behavior. But
as I see you are using a package that is now out-of-date, RHEL 5.2 has an
updated version (s390utils-1.5.3-17.el5) and with this version an equivalent
config works on my machine. Can you recheck your config with this updated
version of s390utils?

------- Comment From mgrf.com 2008-07-14 10:45 EDT-------
(In reply to comment #51)
> ------- Comment #2171043 from bugzilla at 2008/07/14 07:20:33 EDT
-------
> These changes made by dhorak.
> Bugzilla comment added:
> Hmm, it is our "automenu" patch that modifies the default upstream
behavior. But
> as I see you are using a package that is now out-of-date, RHEL 5.2 has
an
> updated version (s390utils-1.5.3-17.el5) and with this version an
equivalent
> config works on my machine. Can you recheck your config with this
updated
> version of s390utils?

Hello Red Hat:
Can you please post your config used and results for comparison please?

Resolution set to: 'Unknown'

This event sent from IssueTracker by jkachuck 
 issue 129816

I ran the tests in comment 7 on the 5.2 s390utils:

# rpm -q s390utils
s390utils-1.5.3-17.el5

Don't you have an older zipl somewhere?

[root@s390x ~]# rpm -q s390utils
s390utils-1.5.3-17.el5
[root@s390x ~]# which zipl
/sbin/zipl
[root@s390x ~]# 

my config (zipl-test.conf):
-----
[defaultboot]                                                                  
                    
default=2.6.18-92.el5                                                          
                    
target=/boot/                                                                  
                    
[2.6.18-92.el5]                                                                
                    
        image=/boot/vmlinuz-2.6.18-92.el5                                      
                    
        ramdisk=/boot/initrd-2.6.18-92.el5.img                                 
                    
        parameters="root=/dev/VolGroup00/LogVol00"                             
                    
[linux]                                                                        
                    
        image=/boot/vmlinuz-2.6.18-92.el5                                      
                    
        ramdisk=/boot/initrd-2.6.18-92.el5.img                                 
                    
        parameters="root=/dev/VolGroup00/LogVol00"                             
                    
-----

[root@s390x ~]# zipl -c zipl-test.conf --dry-run
Using config file 'zipl-test.conf' (from command line)
Starting dry-run, target device contents will NOT be modified
Building bootmap in '/boot/'
Building menu 'rh-automatic-menu'
Adding #1: IPL section '2.6.18-92.el5' (default)
Adding #2: IPL section 'linux'
Preparing boot device: dasda (0120).
Done.

Oh, sorry, I see it now, I forgot to add the "linux" option to my command line.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-0188.html