Cobbler repositories --priorities problem
Dan White
ygor at comcast.net
Mon Dec 19 16:04:18 UTC 2011
Do you have yum-priorities plugin installed ?
What does the command:
yum list yum-priorities
return ?
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
----- Will McDonald <wmcdonald at gmail.com> wrote:
> Hi List.
>
> I wonder if anyone's seen this problem or can explain what's going on. I've
> updated a couple of repository's priorities using:
>
> [root at buildhost ~]# cobbler repo edit --name=$repo --priorities=N
>
> When I check the repo that I've altered it LOOKS like the edit has
> succeeded, but when I look at the .repo Cobbler's dynamically building,
> it's still pegged at '99'
>
> [root at buildhost ~]# cobbler profile report
> --name=centos56-x86_64-oradb11202-wls1034 | grep Repo
> Repos : ['centos56-repo-x86_64']
>
> [root at buildhost ~]# cobbler repo report --name=centos56-repo-x86_64 | grep
> Prio
> Priority : 1
>
> [root at buildhost ~]# wget -q "
> http://192.168.0.102/cblr/svc/op/yum/profile/centos56-x86_64-oradb11202-wls1034"
> -O /tmp/test.repo
> [root at buildhost ~]# cat /tmp/test.repo
> [centos56-repo-x86_64]
> name=centos56-repo-x86_64
> baseurl=http://192.168.0.102/cobbler/repo_mirror/centos56-repo-x86_64
> enabled=1
> priority=99
> gpgcheck=0
>
> This problem seems to manifest across all repos and associated profiles.
> The value in the JSON for each repo is being updated, it's just the
> dynamically built repo that isn't.
>
> I've tried 'cobbler sync|reposync' and 'service cobblerd restart' the
> problem remains the same. If it's of any bearing, the repos are hardlinked
> mirrors of the corresponding kickstart trees.
>
> I've attached a full 'cobbler report' too in case that's of any use. Am I
> just doing something fundamentally wrong? This is cobbler-2.0.11-2.el5 from
> EPEL on CentOS 5.7.
More information about the cobbler
mailing list