Bug 1485865
| Summary: | /etc/virt-who.conf gets overwritten by an update of the virt-who package | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Kenny Tordeurs <ktordeur> | |
| Component: | virt-who | Assignee: | candlepin-bugs | |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> | |
| Severity: | high | Docs Contact: | Jiri Herrmann <jherrman> | |
| Priority: | high | |||
| Version: | 7.4 | CC: | csnyder, jherrman, omankame, rjerrido, yuefliu | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Release Note | ||
| Doc Text: |
*virt-who* configuration no longer resets on upgrade or reinstall
Previously, upgrading or reinstalling *virt-who* reset the configuration of the `/etc/virt-who.conf` file to default values. This update changes the packaging of *virt-who* to prevent overwriting configuration files, which ensures the described problem no longer occurs.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1530132 (view as bug list) | Environment: | ||
| Last Closed: | 2018-04-10 16:21:32 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1530132 | |||
|
Description
Kenny Tordeurs
2017-08-28 10:12:09 UTC
A fix has been posted but not merged to upstream master yet. Moving this bug to POST. Moving to MODIFIED as the fix has been merged to upstream master and will be included in the first build for 7.5. Verified the bug with virt-who-0.21.0-1.el7.noarch, Steps: 1. Install virt-who-0.19-5.el7_4.noarch.rpm and configure /etc/virt-who.conf value. 2. Update virt-who to virt-who-0.21.0-1.el7.noarch.rpm by "#rpm -Uvh" 3. Check /etc/virt-who.conf, the configuration still exists. 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, 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/RHEA-2018:0895 |