Hi Michael,
On 12.01.2017 21:36, Shaw, Michael wrote:
> Hello,
>
> I walked into an environment that had no frozen channels and monthly patching
> happened by whatever was available in the channel at the time, i.e. if there
> was a kernel upgrade then the kernel upgraded. This has ended up
I retired a bit more than a year ago, so I don't have scripting details
to share, but here's a conceptual outline of how we did it.
Had the same situation when we first deployed spacewalk/Satellite. We
(okay, I) created RHSA-test and RHSA-prod patch channels for each base
OS. Scripted forced
Try and utilize the command lines.
spacewalk-clone-by-date
!!!RESTART TASKOMATIC before running this:
/usr/bin/spacewalk-manage-channel-lifecycle -c $fromchnl --no-children
--promote
Base -> Always updating from the public repo's
date{x}Base -> Frozen at Date {x}
*Note, some 3rd
Hello,
I walked into an environment that had no frozen channels and monthly patching
happened by whatever was available in the channel at the time, i.e. if there
was a kernel upgrade then the kernel upgraded. This has ended up causing
issues.
I have since then locked all of the hosts and
>
>> Due to some reason, many of the servers have issues related to OSAD going
>> offline time and again so sometimes we just go for a way of running
>> rhn_check manually.
>>
>> So I was wondering, can we have rhn_check in all the servers in CRON ? Can
>> it work in this situation ? I had
On 12/01/17 10:58, Zeal Vora wrote:
Hi
We use SpaceWalk 2.4 for our Patch Management.
Due to some reason, many of the servers have issues related to OSAD
going offline time and again so sometimes we just go for a way of
running rhn_check manually.
So I was wondering, can we have rhn_check
Hi
We use SpaceWalk 2.4 for our Patch Management.
Due to some reason, many of the servers have issues related to OSAD going
offline time and again so sometimes we just go for a way of running
rhn_check manually.
So I was wondering, can we have rhn_check in all the servers in CRON ? Can
it work
