Hide Forgot
Description of problem: When one installs using kickstart and url --noverifyssl and/or repo --noverifyssl the --noverifyssl attributes are not written in anaconda-ks.cfg. Version-Release number of selected component (if applicable): anaconda-13.21.97-1.el6 How reproducible: Always Steps to Reproduce: 1. Perform fully automated installation over https using self-signed certificate. 2. Add to your ks.cfg: url --url https://example.com/rhel --noverifyssl 3. After install do: # grep ssl anaconda-ks.cfg Actual results: --noverifyssl is missing. The result is a kickstart file which can't be used to install again from the same server (because the certificate is self-signed). Expected results: --noverifyssl is present. Additional info:
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.
Fixed by d73b022a34ebbe9ed8a7afb7b2862d707e6f2e29. Fixed on master by 9baca69cff6b1f8c94c2937739730fc4074f194a.
VERIFIED with 0308.n.1 tree.
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-2011-0530.html