[Spacewalk-list] Kickstart falling in spacewalk 1.5

Fri Sep 2 17:40:26 UTC 2011

No, I'm still in 1.4, and I have this problem all the time. Of course, 
the source of my problem is a little different - I'm trying to save 
space by not loading all the packages from the DVD into spacewalk...

If you reposync from 
http://download.fedoraproject.org/pub/fedora/linux/releases/15/Fedora/x86_64/os/ 
instead of from 
http://download.fedoraproject.org/pub/fedora/linux/releases/15/Everything/x86_64/os/, 
then you get the same 3K packages in your base channel as on the media. 
I haven't tried to make that change after the fact, but I doubt that 
spacewalk will clear out the extra packages.

Yes, you have to duplicate packages on disk to recreate the repodata. 
After the repodata has been recreated, you can delete the extra copy of 
the packages that you used to create the repodata.

There is no point in running repo-sync for a base channel after you have 
fully populated it. No packages are ever added to the base after the 
initial release (this applies to Fedora only and is not necessarily true 
of Centos or RedHat), only packages in updates are modified. And 
anaconda correctly pulls repodata for updates from spacewalk instead of 
the distro tree.

You could also take John Hodrien's approach and move everything to a 
child channel. Since anaconda's problem is that it can't see packages in 
base that are not referenced by the repodata from the media, it should 
be able to pull those packages from a child channel.

Jonathan

On 09/02/2011 11:17 AM, André Freitas wrote:
> On 09/02/2011 03:38 PM, Jonathan DeHaan wrote:
>> I see that you have 24K packages in your base channel, but there are 
>> only 3K packages on the DVD media. If you used the repodata from the 
>> media in your distro tree, anaconda only knows about those 3K packages.
>>
>> You need to make sure that the packages in your base channel are 
>> exactly the same as referenced by the repodata in your distro tree - 
>> and spacewalk does not do this for you automatically.
> But this was anything that changed from spacewalk 1.4 to 1.5? the 
> strange part is that i always put the distribution tree path mounted 
> from ISO and base channel using the base repo from distribution (in 
> this case fedora.repo has 24K files) and i never had this problem.
>>
>> You can either download all 24K packages into the Packages folder of 
>> your distro tree and run createrepo, 
> ok but wouldn't this option duplicate the space in disk (as i would 
> have to download again all the 24K of rpms)? the rpms collected by 
> spacewalk-repo-sync are put on /var/satellite using a strange 
> hierarchy of directory (i never understand the logic behind this) and 
> i don't see any way to put the packages from this directories in 
> distro tree package directory (is there any way that i can use local 
> repositories [using rsync and create repo] without the need to upload 
> the files for spacewalk - which consequently would create a second 
> copy of the files in /var/satteliite?)
>> or you can create a child channel called 'extras' and move all the 
>> packages in your base channel that aren't on the DVD to that channel. 
>> If you go the createrepo route, then after it recreates the repodata, 
>> you can delete the packages in the distro tree - anaconda does 
>> correctly pull the packages themselves from the spacewalk channel.
> I think this options is very time consuming and wouldn't probably 
> resolve my problem because when i run the spacewalk-repo-syunc for 
> base channel (or the extras repo) all the missing files would be 
> downloaded again making the channels with more packages than the 
> distro tree
>>
>> A third option would be to take the repodata files from 
>> /var/cache/rhn/repodata and merge them with the comps file from your 
>> current distro tree. You'll have to piece together the repomd.xml 
>> file using the entries from the cache and the original entries for 
>> type 'group' and 'group_gz'.
> Again i think this option is also very time consuming as i would have 
> to repeat this step all the time that the meta changes
>>
>> Jonathan
>>
>> On 09/02/2011 06:08 AM, André Freitas wrote:
>>> No i didn't add anything of spacewalk to the base channel (i use a 
>>> child repo that gets the information form spacewalk directly using 
>>> spacewalk-repo-sync).
>>>
>>> How can see/change the metadata of the distribution tree? The 
>>> strange is that when i used spacewalk 1.4 i din't have this problem.
>>>
>>> On 09/01/2011 03:43 PM, Jonathan DeHaan wrote:
>>>> Anaconda ignores the repository metadata that is provided by spacewalk
>>>> for the base channel and only uses the metadata in the distribution
>>>> tree. If you add any packages to the base channel, you have to recreate
>>>> the metadata and put it in the distribution tree, or anaconda won't see it.
>>>>
>>>> After the install, yum correctly pulls metadata for the base channel
>>>> from spacewalk directly.
>>>>
>>>> Jonathan
>>>>
>>>> On 09/01/2011 08:38 AM, André Freitas wrote:
>>>>> Hi,
>>>>>
>>>>> i have spacewalk 1.5 installed in a machine that has fedora 15 as it
>>>>> OS. I have created the fedora 15 distribution in spacewalk and created
>>>>> the following repos (base and child ones):  Fedora 15 64-bits, Fedora
>>>>> 15 Updates 64-bits, RPMFusion Free 64-bits, RPMFusion Free Updates
>>>>> 64-bits, RPMFusion NonFree 64-bits, RPMFusion NonFree Updates 64-bits
>>>>> and Spacewalk-Client 1.5 64-bits.
>>>>> I have created a minimum kickstart to install fedora. If i put the
>>>>> following packages to install in the kickstart
>>>>>
>>>>> rhn-client-tools
>>>>> rhn-check
>>>>> rhn-setup
>>>>> rhnsd
>>>>> m2crypto
>>>>> yum-rhn-plugin
>>>>> rhncfg-actions
>>>>> wget
>>>>> osad
>>>>>
>>>>> and try to use this kickstart in PXE, i get the information that some
>>>>> of the dependencies doesn't exit. The problem is that i confirm that
>>>>> all the packages are in the repos associated to the kickstart and
>>>>> activation key. If i remove the packages from the kickstart and use it
>>>>> to install in a target machine, i don't have problems when i try to
>>>>> "yum install" those packages after the installation (i edit yum.conf
>>>>> so that i have all the same repos that spacewalk uses to collect
>>>>> information when using spacewalk-repo-sync).
>>>>> Is there any log where i can try to see (in spacewalk-server) what is
>>>>> falling in the installation of the kickstart with the above packages?
>>>>>
>>>>> Best regards,
>>>>> André Freitas
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Spacewalk-list mailing list
>>>>> Spacewalk-list at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>>
>>>
>>>
>>> _______________________________________________
>>> Spacewalk-list mailing list
>>> Spacewalk-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>>
>> -- 
>> Jonathan DeHaan
>> Linux Systems Engineer
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list

-- 
Jonathan DeHaan
Linux Systems Engineer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110902/b898f2e8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 52808 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110902/b898f2e8/attachment.png>