Hide Forgot
Summary of problem: boot with rhn_CA_CERT=<certificate_file> and that parameter gets persisted across reboots. This is not a bug. the parameter you want is rhn_ca_cert=, not rhn_CA_CERT. In your case, it happened to work because the certificate is in the default place we look for it. FYI: This is documented correctly here: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-RHEV_Hypervisor_Kernel_Parameters_and_Automated_Installation-RHN_parameters.html
(In reply to comment #2) > Summary of problem: > > boot with rhn_CA_CERT=<certificate_file> and that parameter gets persisted > across reboots. > > This is not a bug. the parameter you want is rhn_ca_cert=, not rhn_CA_CERT. > In your case, it happened to work because the certificate is in the default > place we look for it. > > FYI: > > This is documented correctly here: > > http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-RHEV_Hypervisor_Kernel_Parameters_and_Automated_Installation-RHN_parameters.html Yes, there is no such issue with rhn_ca_cert=, not rhn_CA_CERT, thanks for your advice.