We have updated patch on our server SP2 with patch date 2017-10-04. It is updated to the kernel version 4.4.90-92.45.1 which is released on 2017-10-25. How it is updated to the latest one even if we have provided the patch date as 2017-10-04. It should be the patch level released before 2017-10-04?
What command did you apply to your server to do the update?
Also, I presume this is SLES 12 SP2, as nothing else makes sense. You may
have specified that in the forum web UI, but I cannot tell from here.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
zypper patch --date 2017-10-04
yes, it is SLES12 SP2
On 12/12/17 06:24, bpquerries wrote:
zypper patch --date 2017-10-04[/color]
My understanding of the above is the same as yours, in that it should
not install patches on or after the date given.
yes, it is SLES12 SP2[/color]
I’ve just set up a test server with SLES12 SP2 and can duplicate this.
Interestingly, on a freshly installed (and so unpatched) server at the
very beginning of “zypper patch --date 2017-04” it reports various
patches, including SUSE-SLE-SERVER-12-SP2-2017-1786, as being issued
after the specified date … yet it still installed them.
Let me ask my SUSE contacts.
SUSE Knowledge Partner
Hi, thanks for the response… will wait for your further updates
Do you have any update?
On 14/12/17 03:44, bpquerries wrote:
Do you have any update?[/color]
Not this soon and given the holidays are, or will soon be, upon us I
don’t expect one so soon. Once I hear something back I will post an
SUSE Knowledge Partner
And for completeness:
‘patch --date’ selects which patches get selected, not how they are applied.
A ‘patch’ is a meta-object conflicting with the affected/vulnerable versions of a set of packages. As long as any of these affected/vulnerable versions is installed, the conflict triggers and the patch is classified as
needed. Selecting the patch, the conflict is resolved by updating all installed and affected/vulnerable packages mentioned in the patch.
When updating packages, zypper will always head for the latest version.
It behaves as expected.