# Automate patching process **URL:** \ **Category:** SLES Updates\ **Created:** [August 11, 2013, 1:22pm UTC](https://forums.suse.com/t/automate-patching-process/24264 "2013-08-11T13:22:23Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [August 14, 2013, 11:16pm UTC](https://forums.suse.com/t/automate-patching-process/24264/21 "2013-08-14T23:16:51Z")
jmozdzen sounds like they ‘said’: [color=blue] > Stevo;15175 Wrote:[color=green] > > > jmozdzen sounds like they ‘said’: > > [color=darkred] > > > > > Hi Stevo, > > > > > > great you got it running & thanks for reporting back! > > > > > > Regards, > > > Jens[/color] > > > > So my response to jmozdzen’s comment is… > > > > Of course another oddity shows up. Picked a server, installed > > latest patches (including July 2013 OES Maint patch), rebooted, no > > updates available. > > > > Looking on the SMT box, this server still shows a critical status > > with updates needed…sigh > > > > – > > Stevo[/color] > > Hi Stevo, > > with “installed latest updates” you mean installing them manually, > right? Invoking “zypper up” (or alike) does nothing to your SMT > status, you’d need to invoke “smtclient” manually after the update, > too. Of course, the cron’ly invocation will “heal” you client’s > status, too. > > Think of SMT as providing a local repository (periodically syncing > that with the Novell master repository) and a client component that > acts as a wrapper to local packet management and reports back the > resulting patch status to the SMT server. > > Regards, > Jens[/color] So my response to jmozdzen’s comment is… You mean invoke smt-agent manually after an update? I did that on the first server I updated a half dozen times, it still always showed up in a critical state. – Stevo ---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [August 14, 2013, 11:17pm UTC](https://forums.suse.com/t/automate-patching-process/24264/22 "2013-08-14T23:17:11Z")
jmozdzen sounds like they ‘said’: [color=blue] > well, I then ow you a solution. Wait, you already got that, I’m off > the hook 😃 > > Regards, > Jens[/color] So my response to jmozdzen’s comment is… I would take a beer. 😉 – Stevo ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [August 15, 2013, 12:32am UTC](https://forums.suse.com/t/automate-patching-process/24264/23 "2013-08-15T00:32:17Z")
Hi Stevo, [QUOTE=Stevo;15182] You mean invoke smt-agent manually after an update? I did that on the first server I updated a half dozen times, it still always showed up in a critical state. – Stevo[/QUOTE] then my memory didn’t serve me right. Nevertheless, give it a few hours to a day (maybe some update interval at the server side blocks updating the status), if it still reports “critical” without new updates being required, I’ll help looking into it more closely. Regards, Jens ---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [August 15, 2013, 9:16pm UTC](https://forums.suse.com/t/automate-patching-process/24264/24 "2013-08-15T21:16:13Z")
jmozdzen sounds like they ‘said’: [color=blue] > then my memory didn’t serve me right. Nevertheless, give it a few > hours to a day (maybe some update interval at the server side blocks > updating the status), if it still reports “critical” without new > updates being required, I’ll help looking into it more closely. > > Regards, > Jens[/color] So my response to jmozdzen’s comment is… So I guess I was just too impatient. Updated a different server this morning, couple hours later it shows as up to date on the SMT box. Thanks again!! – Stevo ---
**Author:** ![shevary](https://avatars.discourse-cdn.com/v4/letter/s/eada6e/32.png) [@shevary](https://forums.suse.com/u/shevary)\ **Post date:** [August 17, 2013, 12:36pm UTC](https://forums.suse.com/t/automate-patching-process/24264/25 "2013-08-17T12:36:32Z")
Hi Jens, I am glad Stevo fixed his issue. Going back to my questions can you used SMT for patching SLES and Opensue? Can you download patches to reportistory and manually add the patches to machine? For instance if I have a machine in DMZ, can I use SMT to download the patches and apply the patches manually? thx ---
**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\ **Post date:** [August 18, 2013, 12:05am UTC](https://forums.suse.com/t/automate-patching-process/24264/26 "2013-08-18T00:05:00Z")
Hi shevary, [QUOTE=shevary;15246]Hi Jens, I am glad Stevo fixed his issue. Going back to my questions can you used SMT for patching SLES and Opensue?[/QUOTE] Hm, at least _we_ are not using SMT for this - although we have our openSUSE repositories shadowed to the same server machine SMT is running on. The repository list on the openSUSE machines is set up to use the local repositories via NFS or FTP (depending on the network connection) and updates are applied using standard openSUSE mechanisms. > [@shevary;15246](#): > > Can you download patches to reportistory and manually add the patches to machine? Can you elaborate on what you’re trying to achieve? Do you want to add _your own_ patches to the repos? Or are you after deciding which (official) patches are distributed to the servers? [QUOTE=shevary;15246]For instance if I have a machine in DMZ, can I use SMT to download the patches and apply the patches manually? thx[/QUOTE] Are you talking about setting up a _SMT server_ in the DMZ to shadow the offical patches to your DMZ, and feeding those to you machines manually? _That_ will work, all you need to do is to disable the cron job for the SMT client and invoke “zypper” on demand on the client machine. In case of a client view behind your question: SMT won’t download the patches to the (SMT client) machine, it rather invokes “zypper” to pull the patches and updates the resulting status at the SMT server. So if you’re looking at the client side of things, then no: SMT won’t download, you’d rather have to invoke “zypper” manually, which _then_ will download from your SMT server. I may have misunderstood you in some parts, then please let me know so I can try to give more matching answers… Regards, Jens ---
**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\ **Post date:** [August 20, 2013, 12:25am UTC](https://forums.suse.com/t/automate-patching-process/24264/27 "2013-08-20T00:25:53Z")
shevary sounds like they ‘said’: [color=blue] > I am glad Stevo fixed his issue.[/color] So my response to shevary’s comment is… Sorry for hijacking this thread, was not my intent. 🙂 – Stevo [Previous page](https://forums.suse.com/t/automate-patching-process/24264.md?page=1)