Hello all, I'm quite new to Cobbler, but have made substantial progress and am grateful for this project!
I run my Cobbler server on a non-standard port, and notice that the cobbler-config.repo that lands in /etc/yum.repos.d/ of a new client install looks like this: [core-0] name=core-0 baseurl=http://x.x.x.x:NNNN/cobbler/ks_mirror/CentOS-6.2-x86_64 enabled=1 gpgcheck=0 priority=1 [CentOS-6.2-x86_64] name=CentOS-6.2-x86_64 baseurl=http://x.x.x.x/cobbler/repo_mirror/CentOS-6.2-x86_64 enabled=1 priority=99 gpgcheck=0 That is, the "core-0" repo gets the alternate port, but the "CentOS..." repo I set up does not. Consequently, the "yum check-update" command fails until I add the port to the baseurl assignment. My digging suggested this is generated by the code in "kickgen.py" but it uses the "$http_server" variable in both the "generate_repo_stanza" and "generate_config_stanza" methods, so I'd expect the port number in any case. I'm not sure where to dig in the code beyond that... FYI, my kickstart does contain the "$yum_config_stanza" variable, and I do have yum_post_install_mirror set to "1". Any thoughts/suggestions as to why no port number?? Many thanks! Alaric _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
