Bug 731738

Summary: Error in %postun scriptlet
Product: Red Hat Enterprise Linux 6 Reporter: Richard W.M. Jones <rjones>
Component: spice-serverAssignee: Uri Lublin <uril>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: acathrow, cfergeau, dblechte, mkenneth
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-18 14:45:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Richard W.M. Jones 2011-08-18 14:13:39 UTC 
Description of problem:

This is not very serious, but I'm just noting it anyway.  When
upgrading from spice-server 0.8.0-1.el6.x86_64 -> 0.8.2-3.el6.x86_64
RPM gives this non-fatal error:

Running Transaction
  Updating   : spice-server-0.8.2-3.el6.x86_64                             1/16 
  Updating   : 2:qemu-img-0.12.1.2-2.183.el6.x86_64                        2/16 
  Updating   : spice-protocol-0.8.1-1.el6.noarch                           3/16 
  Updating   : seabios-0.6.1.2-4.el6.x86_64                                4/16 
  Installing : sgabios-bin-0-0.3.20110621svn.el6.noarch                    5/16 
  Updating   : kernel-firmware-2.6.32-188.el6.noarch                       6/16 
  Installing : kernel-2.6.32-188.el6.x86_64                                7/16 
  Updating   : 2:qemu-kvm-0.12.1.2-2.183.el6.x86_64                        8/16 
  Updating   : spice-server-devel-0.8.2-3.el6.x86_64                       9/16 
  Cleanup    : spice-server-devel-0.8.0-1.el6.x86_64                      10/16 
  Cleanup    : 2:qemu-kvm-0.12.1.2-2.160.el6.x86_64                       11/16 
  Cleanup    : seabios-0.6.1.2-3.el6.x86_64                               12/16 
  Cleanup    : spice-protocol-0.8.0-1.el6.noarch                          13/16 
  Cleanup    : kernel-firmware-2.6.32-131.0.15.el6.noarch                 14/16 
  Cleanup    : spice-server-0.8.0-1.el6.x86_64                            15/16 
Non-fatal POSTUN scriptlet failure in rpm package spice-server
  Cleanup    : 2:qemu-img-0.12.1.2-2.160.el6.x86_64                       16/16 
/sbin/ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-188.el6.x86_64.conf:6: hwcap index 0 already defined as nosegneg
warning: %postun(spice-server-0.8.0-1.el6.x86_64) scriptlet failed, exit status 1


Version-Release number of selected component (if applicable):

The error appears to be in the %postun scriptlet of
spice-server 0.8.0-1.el6.x86_64

How reproducible:

?

Steps to Reproduce:
1. Upgrade from spice-server 0.8.0-1.el6.x86_64 to a later version.
2.
3.
  
Actual results:

Non-fatal error.

Expected results:

There should be no errors or warnings when upgrading an RPM package.

Additional info:
Comment 1 Richard W.M. Jones 2011-08-18 14:14:45 UTC 
After the upgrade, /etc/ld.so.conf.d/kernel-2.6.32-188.el6.x86_64.conf
contains:

# This directive teaches ldconfig to search in nosegneg subdirectories
# and cache the DSOs there with extra bit 1 set in their hwcap match
# fields.  In Xen guest kernels, the vDSO tells the dynamic linker to
# search in nosegneg subdirectories and to match this extra hwcap bit
# in the ld.so.cache file.
hwcap 1 nosegneg

I don't know what was in this file before.
Comment 3 Andrew Cathrow 2011-08-18 14:37:20 UTC 
Rich,

Is this really a bug on spice-server or is it just 'luck' that spice-server was the next rpm to call ldconfig

Regardless of the root cause, should we be trapping that error and returnign success anyway?
Comment 4 Richard W.M. Jones 2011-08-18 14:45:02 UTC 
Actually yes you are right ...

# /sbin/ldconfig 
/sbin/ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-188.el6.x86_64.conf:6: hwcap index 0 already defined as nosegneg

Odd one though.  This is a completely ordinary RHEL 6.1
install.  Xen has never been near it.
Comment 5 Andrew Cathrow 2011-08-18 14:50:22 UTC 
Before we close it though, would it be better for the post script to catch that (non fatal error) and return success?
Comment 6 Richard W.M. Jones 2011-08-18 14:55:14 UTC 
I don't know.  The way that spice-server is doing it now
is the standard way:

https://fedoraproject.org/wiki/Packaging:Guidelines#Shared_Libraries