Re: [cobbler] best practices for updating major distro release on systems?

I'm using cobbler-2.6.5-9.1 on RHEL 6.6 (yes I know this is not the latest release; I hope it's not relevant in this context). What's the best way to create distros and repositories so that deployed systems are always pointed to the "lastest" base and updates? The problem I'm trying to solve is how to upgrade already-deployed systems to the latest release. The problem I have is this, e.g.: 1. Imported distro centos65-x86_64 a. defined "updates" repository to <some server>/centos/6/updates/x86_64/ 2. System is deployed using CentOS 6.5. cobbler.config automatically configures yum: a) core-0 to ks_mirror/centos65-x86_64 b) updates to repo_mirror/centos6-updates The above works fine until CentOS 6.6 comes out. At some point (I haven't figured out when -- does anyone know?), the "updates" repository for CentOS will only work correctly for CentOS 6.6 systems. CentOS 6.5 system updates are majorly broken at this point -- It will see new updates for packages that are installed, but often the dependencies are for new packages in the CentOS 6.6 base. The CentOS 6.5 machine can't see the packages and therefore can't resolve dependencies. What I've been doing is: 1. Import distro centos66-x86_64 to cobbler 2. On each client system, update yum config to point core-0 to ks_mirror/centos66-x86_64. "yum update" at this point will upgrade from CentOS 6.5 to 6.6. If what I'm doing is the "right/best" way, fine -- I'm just wondering if there is a better way to organize this so updates don't break on existing systems and I don't have to touch every client system when its time to upgrade. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Robert Jacobson Robert.C.Jacobson(a)nasa.gov Lead System Admin Solar Dynamics Observatory (SDO) Bldg 14, E222 (301) 286-1591 _______________________________________________ cobbler mailing list cobbler(a)lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cobbler