Description of problem: Using the following %pre script example, weird things happen with the kickstart. - start - cat > /tmp/a <<EOF a b c d EOF - end - With the above script included in a kickstart profile as a %pre script, The kickstart file looks something like this: %packages --resolvedeps @ Base %pre cat > /tmp/a < /tmp/ssl-key-1 <<'EOF' Certificate: Data: Version: 3 (0x2) Serial Number: 0 (0x0) Signature Algorithm: sha1WithRSAEncryption ..... EOF # ssl-key1 cat /tmp/ssl-key-* > /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT perl -npe 's/RHNS-CA-CERT/RHN-ORG-TRUSTED-SSL-CERT/g' -i /etc/sysconfig/rhn/* And there is no %post section. Version-Release number of selected component (if applicable): rhns-4.1.0-89.rhel4 How reproducible: ever time Steps to Reproduce: 1. Create kickstart profile 2. Create a %pre using hte script mentioned above 3. Actual results: Weirdness, and no %post section Expected results: See seperate %post & %pre sections Additional info: A work-around is to add a space between << & EOF so the line would be cat > /tmp/a << EOF
User bnackash's account has been closed
I've just tried this on rhns-5.1.0-9 and both the %pre and %post scripts are shown as expected. So I assume that with the numerous changes to the kickstart generation code, this problem got resolved. As such, moving to ON_QA. Taking from Mike's plate and reassigning to myself for possible kickbacks.
On the latest ISO build, 510-15, including the test script as a %pre script does not cause the funky behavior originally reported. Thus, it looks like this bug is now VERIFIED.
Looks good on Stage Satellite, moving to RELEASE_PENDING.
UI Enhancements for 5.1 Sat GA so Closed for Current Release.