[Spacewalk-list] Package is not available for installation, again

[Paul Robert Marino]

check the taskomatic logs
there may be one of two things happening.
1 there is a delay after you add a package before it becomes visible
to the target servers because taskomatic needs to generate new XML
files for yum.
2 if you have a very large channel then occasionally you may see the
repodata jobs fail due to exceeding the memory limit. if that is
happening you will need to increase the max ram i the taskomatic
config ten restart it.

On Wed, Nov 16, 2016 at 11:24 AM, Robert Paschedag
<robert.paschedag at web.de> wrote:
> All systems are subscribing the same channel that packages have been pushed to?
>
> Am 16.11.2016 11:01 schrieb Artem Pastukhov <pastukhov at lecta.ru>:
>>
>> Hi all!
>> I'm truing to make CI/CD system with spacewalk 2.5
>>
>> There is three seps
>> make rpm
>> push it to spacewalk with rhnpush
>> Schedule to install it to group of hosts with schedulePackageInstall API call
>> And i have troubles with last step. Sometime approximately 10% of cases i'm getting  Package %packageName is not available for installation. I get %packagename by calling listLatestAvailablePackage method.
>>
>> If I reschedule same job in a few minutes, I will get a successful result in 90% of cases.
>>
>> Is there any way to get 100% ?
>>
>> --
>>
>> С уважением,
>>
>> АРТЕМ ПАСТУХОВ,
>>
>> Системный администратор
>>
>> +7 (916) 597-56-74 | +7 (800) 555-46-68 | #переходиналекта
>>
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list