Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: After upgrading from virt-viewer-5.0-10.el7.x86_64 to virt-viewer-5.0-11.el7.x86_64, there is a dangling symlink in /etc/alternatives/spice-xpi-client
Version-Release number of selected component (if applicable):
virt-viewer-5.0-11.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. rpm -Uvh ./virt-viewer-5.0-11.el7.x86_64.rpm
2. [ -h /etc/alternatives/spice-xpi-client -a \! -f /etc/alternatives/spice-xpi-client ] && echo symlink missing
3.
Actual results:
symlink missing
Expected results:
The rpm scripts should remove the obsolete alternative by running /usr/sbin/update-alternatives --remove spice-xpi-client /usr/libexec/spice-xpi-client-remote-viewer
Additional info:
I can reproduce this bug with version:
virt-viewer-5.0-11.el7.x86_64
Steps:
1. Prepare a host with "virt-viewer-5.0-10.el7.x86_64" installed.
$ rpm -q virt-viewer
virt-viewer-5.0-10.el7.x86_64
1.1 Check status of file "/etc/alternatives/spice-xpi-client".
$ ll /etc/alternatives/spice-xpi-client
lrwxrwxrwx. 1 root root 43 Apr 29 15:17 /etc/alternatives/spice-xpi-client -> /usr/libexec/spice-xpi-client-remote-viewer
Result: File "/etc/alternatives/spice-xpi-client" is existing.
2. Update virt-viewer version to virt-viewer-5.0-11.el7.x86_64
# yum update virt-viewer-5.0-11.el7.x86_64.rpm -y
...
$ rpm -q virt-viewer
virt-viewer-5.0-11.el7.x86_64
2.1 Check status of file "/etc/alternatives/spice-xpi-client".
$ ll /etc/alternatives/spice-xpi-client
lrwxrwxrwx. 1 root root 43 Apr 29 15:17 /etc/alternatives/spice-xpi-client -> /usr/libexec/spice-xpi-client-remote-viewer
Result: There is a dangling symlink in /etc/alternatives/spice-xpi-client, so I can reproduce this bug now.
Then try to verify this bug with latest version:
virt-viewer-5.0-13.el7.x86_64
3. Update virt-viewer from old version "virt-viewer-5.0-11.el7.x86_64" to latest version "virt-viewer-5.0-13.el7.x86_64"
# yum update virt-viewer-5.0-13.el7.x86_64 -y
3.1 Check status of file "/etc/alternatives/spice-xpi-client" again.
$ ll /etc/alternatives/spice-xpi-client
ls: cannot access /etc/alternatives/spice-xpi-client: No such file or directory
Result: File "/etc/alternatives/spice-xpi-client" isn't existing now.
New version of virt-viewer removes alternatives for spice-xpi-client so I move this bug from ON_QA to VERIFIED.
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/RHSA-2019:2229