Bug 1874807 - TPS result complaining about exiting symbolic link
Summary: TPS result complaining about exiting symbolic link
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.4.1
Hardware: All
OS: All
medium
medium
Target Milestone: ovirt-4.4.2
: 4.4.2
Assignee: Nobody
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-02 09:55 UTC by Pavol Brilla
Modified: 2020-09-23 16:16 UTC (History)
5 users (show)

Fixed In Version: vdsm-4.40.26.3
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-23 16:16:39 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3823 0 None None None 2020-09-23 16:16:40 UTC
oVirt gerrit 111089 0 master MERGED spec: Don't recreate config on upgrades 2020-09-21 08:27:17 UTC
oVirt gerrit 111090 0 ovirt-4.4.2 MERGED spec: Don't recreate config on upgrades 2020-09-21 08:27:17 UTC

Description Pavol Brilla 2020-09-02 09:55:26 UTC 
During Upgrade TPS test I am getting error:
doRpmCommand-result (0): ln: failed to create symbolic link '/etc/sysctl.d/50-coredump.conf': File exists

looks related to scripts of vdsm rpm
# rpm -qp --scripts vdsm-4.40.26-1.el8ev.ppc64le.rpm | grep core
# core dumps for us, so we have to disable the systemd's core
ln -s /dev/null /etc/sysctl.d/50-coredump.conf

Steps to reproduce:

Try to upgrade 4.4 vdsm with new version
Comment 5 errata-xmlrpc 2020-09-23 16:16:39 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (RHV RHEL Host (ovirt-host) 4.4.z [ovirt-4.4.2] 0-day), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3823
Note You need to log in before you can comment on or make changes to this bug.