[Spacewalk-list] RHEL 4 client management

[Pierre Casenove]

I managed to get the packages that are not synced.
The packages are gpg-pubkey and 8 packages not provided by redhat,
which are not in any channel of my spacewalk server.

To go further down, I need to understand how arch detection works:
- If I modifiy python code to set to None the arch field if it is
empty, the package sync is working, but all packages are listed with
architecture set as "not specified"
- The up2date client does not provide the arch information to the
spacewalk server (as we can see in the traceback)
- With the actual python code, the sync is done partially (909
packages out of 918) but the arch is set

Where does spacewalk find the arch information when it is not provided
by the client?

Thanks,

Pierre




2012/5/11 Pierre Casenove <pcasenove at gmail.com>:
> Thanks,
> Which definitly leave me confused, as I don't see where the problem is!
> And finding the 9 RPMs that are not synced on a system with 920 RPM is not easy
> How could I log the package that is problematic?
>
> Pierre
>
>
> 2012/5/11 Miroslav Suchy <msuchy at redhat.com>:
>> On 11.5.2012 10:54, Pierre Casenove wrote:
>>>
>>> Hello,
>>> I'm analyzing the traceback in order to understand a bit more what I am
>>> doing.
>>> And I'm suprized to see that there are some exclamation mark in the
>>> traceback:
>>>                package_data =<type 'dict'>  {'a': ['', '', '', '', '', '',
>>> '',
>>> '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '',
>>> '',
>>> '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', '', ''!
>>>  , '', ''
>>> , '', '', ''
>>>
>>> Is it normal or could it be the reason of failure?
>>
>>
>> It is just formatting of TB, it means just: "we are putting here \n but in
>> original data there is neither \n nor whitespace".
>>
>> Mirek
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list