dchunt Absent Member.
Absent Member.
804 views

OES2018 kenel source conflict

When I go to patch one of my OES2018 servers, I get a file conflict that looks like the following:


Detected 2 file conflicts:

File /etc/rpm/macros.kernel-source
from install of
kernel-macros-4.4.121-92.98.1.noarch (OES2018-SLES12-SP2-Updates)
conflicts with file from package
kernel-source-3.0.101-108.38.1.x86_64 (@System)

File /usr/lib/rpm/kernel-module-subpackage
from install of
kernel-macros-4.4.121-92.98.1.noarch (OES2018-SLES12-SP2-Updates)
conflicts with file from package
kernel-source-3.0.101-108.38.1.x86_64 (@System)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.



What should I do? Should I continue? I cancelled the patch for now. Unfortunately, this is a physical server and not a VM so I can't take a snapshot.

Thanks,

Dan
Labels (2)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re:OES2018 kenel source conflict

dchunt Wrote in message:

> When I go to patch one of my OES2018 servers, I get a file conflict that
> looks like the following:
>
>
> Code:
> --------------------
>
> Detected 2 file conflicts:
>
> File /etc/rpm/macros.kernel-source
> from install of
> kernel-macros-4.4.121-92.98.1.noarch (OES2018-SLES12-SP2-Updates)
> conflicts with file from package
> kernel-source-3.0.101-108.38.1.x86_64 (@System)
>
> File /usr/lib/rpm/kernel-module-subpackage
> from install of
> kernel-macros-4.4.121-92.98.1.noarch (OES2018-SLES12-SP2-Updates)
> conflicts with file from package
> kernel-source-3.0.101-108.38.1.x86_64 (@System)
>
> File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
>
> --------------------
>
>
>
> What should I do? Should I continue? I cancelled the patch for now.
> Unfortunately, this is a physical server and not a VM so I can't take a
> snapshot.


Since both of the conflicted files were originally installed from
kernel-source-3.0.101-108.38.1.x86_64 which is a @System package
(i.e. it's not known to zypper from a repo) I would make a backup
of both files then run zypper and choose to contiinue. Afterwards
you can then compare the contents of each file.

Basically what's happened is Micro Focus (or SUSE since these are
SLES-related files) have shipped packages which they've not
included in the Pool repo. Yes they shouldn't do that but it
happens.

HTH.
--
Simon Flood
Micro Focus Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/
0 Likes
Highlighted
lauterbach Absent Member.
Absent Member.

Re: OES2018 kenel source conflict

Just remove kernel-source-3.0.101-108.38.1.x86_64 with zypper or rpm.
It's a leftover from the upgrade to OES2018 and belonged to the previous
OES2015/OES11.

Franz

0 Likes
dchunt Absent Member.
Absent Member.

Re: OES2018 kenel source conflict

Franz, thanks a lot. We will be applying updates tonight so I will follow your recommendation.

What does this file do, anyway?

Dan
0 Likes
dchunt Absent Member.
Absent Member.

Re: OES2018 kenel source conflict

Also, I should know this but I am unsure - what is the correct command syntax for zypper or rpm to remove that file? 'Kernel source' sounds like a pretty important file that would prevent the server from booting. Since this is our only print server, and it is a physical server, I want to make sure I have the command correct so I don't foobar the server.

Thanks,

Dan
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES2018 kenel source conflict

Am 2019-02-07 um 20:04 schrieb dchunt:
>
> Also, I should know this but I am unsure - what is the correct command
> syntax for zypper or rpm to remove that file? 'Kernel source' sounds
> like a pretty important file that would prevent the server from booting.
> Since this is our only print server, and it is a physical server, I
> want to make sure I have the command correct so I don't foobar the
> server.


Hello Dan,

the commands would be:

zypper rm kernel-source-3.0.101-108.38.1

or
rpm -e kernel-source-3.0.101-108.38.1

The reason you can be sure that's harmless is the version. 3.0 kernel
versions belonged to OES2015, OES2018 comes with 4.4 kernel versions.

Franz

0 Likes
dchunt Absent Member.
Absent Member.

Re: OES2018 kenel source conflict

Thanks, Franz. That is what I needed to know.

Dan
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.