Description of problem: While testing kickstarting of a s390x system, I was using kernel options of: "DASD=100 HOSTNAME=s390box.test.example.com IPADDR=XX.XX.XX.XX NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 NETWORK=XX.XX.XX.XX NETMASK=255.255.255.0 SEARCHDNS=example1.example.com:example2.example.com.com BROADCAST=10.10.16.255 GATEWAY=XX.XX.XX.XX DNS=XX.XX.XX.XX PORTNAME=UNASSIGNED MTU=1500 LAYER2=0" I couldn't put the kernel options in the kickstart profile, instead I was entering them through: Advanced Kickstart Configuration from (/rhn/systems/details/kickstart/ScheduleWizard.do) Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL5-re20090625.0-x86_64-embedded-oracle.iso How reproducible: always Steps to Reproduce: 1.Enter the text string described above Actual results: notice that it is truncated Expected results: string is not truncated Additional info:
master git commit: 1147de6f3feabc790c0dfe541dabdb7a4a6576bb vader git commit: 357d8f2728ccddab6f7e8dae8b57f3ffd17b5939 The edit ks profile details was restricting the length of kernel and post kernel options to be 64 characters. Rather than remove the limit, increased it to 1024 in order to keep it bounded to avoid a user entering something that is entirely invalid (e.g. 100,000 characters). Systems->Kickstart->Profiles->profile->Kickstart Details
Verified. 1) create ks profile 2) Systems->Kickstart->Profiles->profile->Kickstart Details 3) Kernel Options = "DASD=100 HOSTNAME=s390box.test.example.com IPADDR=XX.XX.XX.XX NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 NETWORK=XX.XX.XX.XX NETMASK=255.255.255.0 SEARCHDNS=example1.example.com:example2.example.com.com BROADCAST=10.10.16.255 GATEWAY=XX.XX.XX.XX DNS=XX.XX.XX.XX PORTNAME=UNASSIGNED MTU=1500 LAYER2=0" 4) Submit & observed that value is *not* truncated.
verified on sun-x4200-01.rhts.bos.redhat.com
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/RHEA-2009-1434.html