Bug 1927703 - oVirt Node, protecting key packages from being removed.
Summary: oVirt Node, protecting key packages from being removed.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-release
Classification: oVirt
Component: General
Version: 4.4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.5
: 4.4.5
Assignee: Sandro Bonazzola
QA Contact: shiyi lei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-11 11:18 UTC by Sandro Bonazzola
Modified: 2021-03-18 15:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-18 15:22:06 UTC
oVirt Team: Node
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 113892 0 master MERGED spec: protect from removing key packages 2021-03-15 15:09:02 UTC
oVirt gerrit 113893 0 ovirt-4.4 MERGED spec: protect from removing key packages 2021-03-15 15:09:05 UTC

Description Sandro Bonazzola 2021-02-11 11:18:36 UTC 
This bug was initially created as a copy of Bug #1927395


Description of problem:
Currently it is possible to remove critical oVirt Node pacakges leading to an unrecoverable state


Steps to Reproduce:
1. yum remove libvirt (or any other critical rpm)
2. confirm

Actual results:
critical packages get removed.

protecting the packages can be easily achieved by dropping a configuration file in /etc/dnf/protected.d/
Comment 3 RHEL Program Management 2021-03-15 14:25:52 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 4 Sandro Bonazzola 2021-03-18 15:22:06 UTC 
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.