Production environment: RHEL5.8 server; Cobbler 2.0.11-2 (via RPM) Test environment: RHEL6.4 server; Cobbler 2.5.0-172.1 (via RPM)
The two environments should be more or less the same overall, but obviously "test" is there for trying to move forwards, then eventually pull "production" into line with it. In both environments we are (successfully) installing RHEL6.4 clients; the total is about 100 machines. "Production" is long established and works well. But I'm hitting a problem in "test". Installed systems in both environments include a cobbler-generated file "/etc/yum.repos.d/cobbler-config.repo". In the "production" environment, the file is good and contains several clauses: [core-0] name=core-0 baseurl=http://iii.jjj.kkk.lll/cobbler/ks_mirror/rhel64-x86_64 enabled=1 gpgcheck=0 priority=1 repeated up to "[core-5]". This is followed by a two "# error: could not read repo source: ..." lines about two local repos, but I'm not worried about them; they are unimportant for our environment. But in the "test" environment those "core-<n>" clauses are absent. All we have are those (unimportant) "# error: ..." lines. Are these missing "[core-<n>]" clauses a known issue? I realise that these days even our test server "2.5.0" is out of date. So an answer of "a known fault between 2.0 and 2.5, subsequently fixed in 2.6" would be fine! I'm just trying to get a toehold on this issue so that I can move forwards. Thanks. -- David Lee _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
