Tom Brown wrote:
>> No, I need steps to reproduce, starting with a clean install of a given
>> OS (specify which), and the series of cobbler commands you run to get it
>> into that State.
>>
>>
>>
>
> # cobbler import --path=/var/mirror/5.2/os/x86_64
> --name=CentOS-5.2-x86_64
> --available-as=http://10.10.10.234/mirror/5.2/os/x86_64
> ---------------- (adding distros)
> - found content (breed=redhat) at /var/mirror/5.2/os/x86_64/images/pxeboot
> - creating new distro: CentOS-5.2-x86_64
> - creating new profile: CentOS-5.2-x86_64
> - creating new profile: rescue-CentOS-5.2-x86_64
> - found content (breed=redhat) at /var/mirror/5.2/os/x86_64/images/xen
> - creating new distro: CentOS-5.2-xen-x86_64
> - creating new profile: CentOS-5.2-xen-x86_64
> ---------------- (associating kickstarts)
> - found content (breed=redhat) at /var/mirror/5.2/os/x86_64/images/pxeboot
> - found content (breed=redhat) at /var/mirror/5.2/os/x86_64/images/xen
> - found content (breed=redhat) at /var/mirror/5.2/os/x86_64/images/pxeboot
>
> # cobbler distro list
> CentOS-5.2-x86_64
> CentOS-5.2-xen-x86_64
>
> Now point the created profile at the correct ks
>
> # cobbler profile edit --name=CentOS-5.2-xen-x86_64
> --kickstart=/var/lib/cobbler/kickstarts/CentOS-5.2-xen-x86_64.ks
>
> # cobbler profile report CentOS-5.2-xen-x86_64
> profile : CentOS-5.2-xen-x86_64
> distro : CentOS-5.2-xen-x86_64
> comment :
> created : Tue Apr 7 10:22:33 2009
> dhcp tag : default
> enable menu : True
> kernel options : {}
> kickstart : /var/lib/cobbler/kickstarts/CentOS-5.2-xen-x86_64.ks
> ks metadata : {}
> mgmt classes : []
> modified : Tue Apr 7 10:24:56 2009
> name servers : []
> name servers search : []
> owners : [u'admin']
> post kernel options : {}
> redhat mgmt key : <<inherit>>
> redhat mgmt server : <<inherit>>
> repos : []
> server : <<inherit>>
> template_files : {}
> virt bridge : xenbr0
> virt cpus : 1
> virt file size : 5
> virt path :
> virt ram : 512
> virt type : xenpv
>
> Now lets add some repos
>
> # cobbler repo add --name=CentOS-5.2-x86_64-base
> --mirror=http://10.10.10.234/mirror/5.2/os/x86_64 --mirror-locally=0
>
> And run the sync
>
> # cobbler reposync
> - /usr/bin/wget -q
> http://10.10.10.234/mirror/5.2/os/x86_64/repodata/comps.xml -O
> /var/www/cobbler/repo_mirror/CentOS-5.2-x86_64-base/repodata/comps.xml
> - creating: /var/www/cobbler/repo_mirror/CentOS-5.2-x86_64-base/config.repo
>
> Now lets add that repo to the profile
>
> # cobbler profile edit --name=CentOS-5.2-xen-x86_64
> --repos='CentOS-5.2-x86_64-base'
>
This isn't a cause, but it's interesting workflow. There's actually no
real reason to mirror the base repo, as it's part of the install tree.
Cobbler will add it, only if needed, and make it available for systems
to use. If you look at
cat /var/lib/cobbler/config/distros.d/name
You will see a source_repos line if the import was given a proper DVD
directory, which will contain the information needed
to let installed systems install packages out of base. Users should
never have to do this manually, they should only have to do this to
content NOT in the install tree.
Also if you look at what was posted in the previous email, it's not
saved with the 'ufoo' instead of u'foo' problem, it's saved as standard
ASCII, "foo", which is
also normal.
Read on a bit further and you'll see where I need some info:
> And check the report for that profile to see that it has that repo now
>
> # cobbler profile report --name=CentOS-5.2-xen-x86_64
> profile : CentOS-5.2-xen-x86_64
> distro : CentOS-5.2-xen-x86_64
> comment :
> created : Tue Apr 7 10:22:33 2009
> dhcp tag : default
> enable menu : True
> kernel options : {}
> kickstart : /var/lib/cobbler/kickstarts/CentOS-5.2-xen-x86_64.ks
> ks metadata : {}
> mgmt classes : []
> modified : Tue Apr 7 10:29:40 2009
> name servers : []
> name servers search : []
> owners : [u'admin']
> post kernel options : {}
> redhat mgmt key : <<inherit>>
> redhat mgmt server : <<inherit>>
> repos : ['uCentOS-5.2-x86_64-base']
> server : <<inherit>>
> template_files : {}
> virt bridge : xenbr0
> virt cpus : 1
> virt file size : 5
> virt path :
> virt ram : 512
> virt type : xenpv
>
Ok, so it appears the 'ufoo' instead of u'foo' or 'foo' problem happens
in memory, not on disk, which is strange to say the least.
Why the RPMs don't show up in the kickstart is a moot point here --
Cobbler wouldn't get the mapping right if it thinks the name is 'ufoo'.
This is likely to be your problem, though I am still stumped by it.
It appears that it is not /saved/ in profiles.d as 'ufoo' however, but
only displayed and used in memory as this. I still can't fathom
why this would happen though since only you have reported in thus far.
I still have a hard time believing the json implementation
would have a bug where the deserialization is not the same as the
serialization for simple strings only containing ".", "_", and "-".
Let me know the following output:
tree /var/lib/cobbler/triggers # let's see if any cobbler triggers are
in place, and if so, I need to see their contents
rpm -q --whatprovides redhat-release
rpm -q cobbler
rpm -q PyYAML
rpm -q python-simplejson
cat /etc/cobbler/modules.conf
That should give me enough to go on to try it in a VM and see if I can
get the same. If so, we can go from there.
--Michael
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
